specs/models/M_APP_VER_STEP_REG
Regular Step
A Regular Step defines the layout and logic for a portion of an app.
Regular Steps allow for widgets to be placed and sized as needed by the user. This creates myriad possibilities for interactions and visualization when creating and running an app.
The User can add the following widgets to Regular Steps:
- Assets
- Default assets (e.g. person icon, rectangle)
- Assets uploaded by the user (e.g. image, logo)
- Buttons
- Generic
- Previous
- Menu
- Next
- Complete
- Inputs
- Checkbox
- Text
- Number
- Single Select
- Multiselect
- Date Picker
- Camera
- Text
- Text
- Variable
- Step Name
- Table Record
- Embed
- Analysis
- Image
- Video
- Document
- Webpage
- Gauge
- Grid
- Machine Attribute
- Machine Status
- Machine Uptime
- Tulip Table
- Camera
- Barcode Scanner
- Timers
- Step Timer
- Process Timer
Fields
| Step | Name of step as defined by the user |
| Step Options (gear icon) | A series of options related to the step and all widgets that it contains |
| Step Cycle Time | Target duration that a step is expected to take when it is run as defined by the user. |
| 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. |
Requirements
| ID | Requirement |
|---|---|
| 67 | Ability to build apps consisting of a number of pre-configured app components. ie for modularity and consistency |
| 72 | App has to display the time elapsed since starting a process step |
| 73 | Ability for apps to display rich media. ie. audio video |
| 87 | Content screens can be populated to the extent possible based on context of entered data. Ie. text fields, drop downs for users to selection, etc. |
| 91 | Ability for content to have text, drop down and check box fields for user input |
| 95 | Ability to view material information for a batch/lot in an App. Information includes all material as part of a material hierarchy, ie. cohort, plate, well, etc.) |
| 102 | Ability to display sampling plan requirements to user |
| 103 | Ability to guide operator in execution of sampling plan. Ie extract materials from batches/lots and disposition of sample material |
| 149 | Ability to provide access to relevant documents such as SOPs at process step |
| 180 | Ability to propagate material attributes to associated materials in the material tracking hierarchies. e.g. assigning material attributes to final product from intermediates. |