Collect data from your users with input Widgets. Each Input Widget supports different types of Variables. All inputs must be tied to the location where their value will be stored.
How to Map Input Widgets to a Storage Location
Input widgets data can be stored to either variables or Fields in Table Records. The Datasource setting is where the destination of the input data can be defined.
If an input isn't tied to a datasource, it won't be selectable when running in the Player.
NOTE
When tied to a Table Record Field, there must be a Record loaded into the Table Record Placeholder.
Types of Input Widgets
Checkbox - Collect True/False values from users. Data can be stored in a Boolean variable ex. In an audit app, users need to confirm that they have executed a process.
Text - Collect non-numeric data from users. Data can be stored in a text Variable ex. In a work instruction app, users can add a note in a text field about a defect they found.
Number - Collect decimal or whole number input from users. Data can be stored in a Number variable or Integer variable. ex. At the end of a production run, users need to populate how many parts they finished.
Date Picker - Collect a date and time from users. Data can be stored in a Datetime variable ex. Maintenance staff can select the date for the next maintenance order for preventative maintenance on a machine
Image - Display a camera where operators can use the device camera to capture an image. Data can be stored in a Image variable ex. When a defect is found, users snap a picture of the anomaly
Signature - Collect a digital user Signature to verify the accuracy of data. ex. At the end of a batch mixing process, users need to sign off that the recipe used matches the work order
Single Select - Users can select one value from a list of options. That list can be statically or dynamically set. Data can be stored in any variable type. ex. When starting a process, users need to select the line they are working on, they need to select from a list of valid values.
Multiselect - Users can select multiple values from a list of options. Data can be stored in an Array of any variable type. ex. When a defect is found users must select all of the defect types that apply to that part.
Input Widget Triggers
For all input widgets, when the input is changed, their Triggers will run.
NOTE
In the case of Number and Text input widgets, triggers will fire on users clicking [Enter]
You can also head to community.tulip.co to post your question or see if others have faced a similar question!
Widgets
Widgets are the elements that make up a specific App Step. Widgets can display information to users, collect user input, or trigger app logic.
Common widgets include: Interactive Tables, Number inputs, Machine attribute widgets, and more.
Input Widget
Input widgets are a set of Widgets specifically designed for users to enter information. Input widgets must be associated with a location where the user input is stored.
Variables
Variables are a location to store app information. Variables have a specific type that must match the contents they can store.
Variables are only accessible within a single application and are cleared when the app is restarted or completed.
Table Record Field
Table Record Fields are single columns within a Tulip Table.
Table Record
A Table Record is a reference to a row in a Tulip Table. Table Records can be created either from the Table UI or from with an App Trigger.
To edit a record it must be loaded into a Table Record Placeholder.
Tulip Player
Tulip Player is the Windows/Mac executable program where users can run Tulip apps. Tulip player allows you to create a more seamless user experience by removing the need for a web browser, and allows increased IT controls.
Table Record Field
Table Record Fields are single columns within a Tulip Table.
Table Record
A Table Record is a reference to a row in a Tulip Table. Table Records can be created either from the Table UI or from with an App Trigger.
To edit a record it must be loaded into a Table Record Placeholder.
Table Record Placeholder
A Table Record Placeholder is a reference to a row in a Tulip Table. Table Records can be created either from the Table UI or from an App Trigger.
Boolean
Boolean's are a Tulip Datatype. Booleans can have True/False (Yes/No) values.
Variable
Variables are a location to store app information. Variables have a specific type that must match the contents they can store.
Variables are only accessible within a single application and are cleared when the app is restarted or completed.
Number
Number is a Tulip Datatype. Numbers can be any positive or negative number. Numbers support decimals.
ex. -5, 15, 47, 155, 15.2, -12.73
Integer
Integers are a Tulip Datatype. Integers can have any whole number.
ex. -5, 15, 47, 155. NOT 15.2, -12.73
Datetime
Datetimes are a Tulip Datatype. Datetimes represent a time in the ISO8601 format.
ex. 2022-08-31T19:56:16+00:00
Image
Images are a Tulip Datatype. Images are a reference to a web-hosted location for all Tulip Images.
Signatures
In regulated environments (GxP) getting a user signature to the accuracy of data is critical for process validation. The E-Sig Widget allows users to collect user signatures along with associated metadata.
Array
Arrays are a Tulip Datatype. Arrays are a list of other variables. Every element in an array must be the same type.
Arrays are very useful when managing multiple values that represent the same information.
ex. The measurements of 10 quality checks can be stored in an Array of Numbers, as opposed to 10 Number variables.
Trigger
Triggers are the mechanism to do things in Tulip Apps. Store data, move users between Steps, Interface with hardware, Etc.
Triggers can be added to widgets, machines, devices, apps, and steps.
Was this article helpful?
Thank you for your feedback! Our team will get back to you
.gif)
