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 three types of steps:

  • Regular steps contain a user defined arrangement of widgets that allow for many types of visualizations and interactions.
  • Form steps only contain input widgets, and in an enforced column/row layout.
  • Approval steps The same as a form step but it also contains an e-signature widget for approving the value captured by the approval step.


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.


QA-T160App Editor Misc - Verify Keyboard Shortcuts Work
QA-T505Copying Triggers : 04 - Copying and pasting Step Triggers
QA-T515Master Layout - Widget triggers
QA-T516Master Layout - Step and App Triggers


27Provide a managed way to define label templates and formats with process and operation specific parameters. Ie. parameters are replaced with specific values when labels are processed for printing during process execution
55Provide a managed way to subscribe or install content in a specific workstation or processing area
67Ability to build apps consisting of a number of pre-configured app components. ie for modularity and consistency
78All contents have to guide operators thru the process steps in an easy intuitive manner. Ie. easy navigation between process steps
79All content has to display the current process step that is being worked on
87Content screens can be populated to the extent possible based on context of entered data. Ie. text fields, drop downs for users to selection, etc.
98Ability to view current process step in the context of the executing production model.
118Ability to configure steps and states for work on orders, materials or equipment in a workflow
133Ability to parameterize a process and production model definitions. Ie. create generic definition using parameterization that are substituted by specific production order information prior to release to production.
147Ability to provide formatted textual work instructions
148Ability to provide multi-media work instructions
150Ability to define steps and procedural elements that are triggered by time-based events such as timers or date-time.
154Ability to use process values from previous process steps in any procedural element or step workflow.
289Ability to exclude a work order from the dispatch list.
297Provide a managed and authorized way to capture (log) and document any deviation from normal process execution as exceptions. An exception log will include a reason, risk category, and comments.
300Provide a managed and authorized way to capture (log) and document any comments or exceptions during process execution.
301Ability to re-execute process step respecting any constraints of the process step configuration in the process flow.
302Ability to re-execute process step with override of constraints of the process step configuration in the Master Recipe or material workflow. In such a case an extra e-signature can be required.
358Provide configurable way to review exceptions
405Ability to manage and track material consumption as part of a process step. Material consumption may include processing, weighing, dispensing, etc.
817Ability to require multiple electronic signatures for a record. Ie co-signer, verifier, etc.