Good Practices

  • Updated

Good Practice I

Always have the mockup of the complete user interface and the user interaction flow

Detailed annotation (UI specification)

  • Layout: division names and actor names

  • Fields and sections of each actor

  • How to do data query

  • Action flow (communication)

Good Practice II

Use stage prerequisites for

  • between-stage communication

  • Between-actor communication both actors are not available at the same time

Configure conditional rendering at the end.

  • Make everything visible to validate the UI state.

Use save to do incremental configuration.

Stage Prerequisite

In Handler

In Stage

Example 24. Code JSON

"assignments": [{
  "field": "$stage(OfferPage).attr(applicationId);",
  "value": "$result.attr(id);"  
}],
"next": "OfferPage"

Example 25. Code JSON

"property": {
  "structureName": "...",
  "whereClause": {
    "applicationId": "$currentStage.attr(applicationId);"    
  }
  
}

Good Practice III

Use JSON editor as the last resort.

  • Action related

  • Data structure without backend

  • “Special configurations” that are not available through the GUI