specs/models/M_APP_VER_STEP
Step
A step is a specific page within an app that is displayed to the user when the app is run. Only a single step can be viewed at a time. There are four types of steps:
Regular steps contain a user defined arrangement of widgets that allow for many types of visualizations and interactions.
Base Layout A step that can be used to apply a template to all Regular steps in an App. Anything shown on the Base Layout will also appear on other steps. Individual Widgets can be unlocked on a per step basis and reset to match the Base Layout as required. There is always a single Base Layout per App.
Fields
| Step | Name of step as defined by the user |
| Step Cycle Time | Target duration that a step is expected to take when it is run as defined by the user. |
| Columns | Number of columns that will be used to display the widgets on the form step. |
| Background | The color of the step background |
| Triggers | Collection of triggers that will run on certain events (e.g. On Step Enter, Timer, Machines & Devices, On Step Exit) |
| Step Resolution | The aspect ratio of the step for when it is run in the Tulip Player. |
| Step Comments | Collection of comments that can be added from the app builder or the Tulip Player. Comments cannot be edited and are associated with specific versions of an app. |
| Notes | Freeform text comments that can be used to describe the purpose of a step or additional information. |
Tests
| ID | Name |
|---|---|
| QA-T160 | App Editor Misc - Verify Keyboard Shortcuts Work |
| QA-T505 | Copying Triggers : 04 - Copying and pasting Step Triggers |
| QA-T515 | Base Layout - Widget triggers |
| QA-T516 | Base Layout - Step and App Triggers |
Requirements
| ID | Requirement |
|---|---|
| PLAT-8902 (817) | Ability to require multiple electronic signatures for a record. Ie co-signer, verifier, etc. |