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

<table> <tr> <td><strong>Step</strong> </td> <td>Name of step as defined by the user </td> </tr> <tr> <td><strong>Step Cycle Time</strong> </td> <td>Target duration that a step is expected to take when it is run as defined by the user. </td> </tr> <tr> <td><strong>Columns</strong> </td> <td>Number of columns that will be used to display the widgets on the form step. </td> </tr> <tr> <td><strong>Background</strong> </td> <td>The color of the step background </td> </tr> <tr> <td><strong>Triggers</strong> </td> <td>Collection of triggers that will run on certain events (e.g. <em>On Step Enter, Timer, Machines & Devices, On Step Exit</em>) </td> </tr> <tr> <td><strong>Step Resolution</strong> </td> <td>The aspect ratio of the step for when it is run in the Tulip Player. </td> </tr> <tr> <td><strong>Step Comments</strong> </td> <td>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. </td> </tr> <tr> <td><strong>Notes</strong> </td> <td>Freeform text comments that can be used to describe the purpose of a step or additional information. </td> </tr> </table>