Data can be entered on Form Steps, but what about entering data on a standard production step?

In order to cut down on the number of steps and routing options an operator must go through, it is often easier to enter data within an instructions step, rather than a separate Form Step. The following will display how to initiate a data entry field, or Input Widget, onto any app step.

Creating A Widget to Store User Input

Select the Input option on the Toolbar:

Once selected, you will have the following options:

  • Checkbox
  • Text
  • Number
  • Single Select
  • Multiselect
  • Date Picker
  • Camera

Checkbox

The checkbox option provides a boolean output, which can be turned to Yes or No by checking or un-checking the box. For more information on checkboxes, check out this article here.

Text

Selecting the text option will provide similar options in the Context Pane.

Similarly to the checkbox, a variable will need to be assigned to the text Input Widget in order to use the data later in the app. This variable can be selected from a list of text variables, or created inline from the Variable selection dropdown.

This will behave in the same way as a variable created in a form step input.

If you want to make the text input widget larger, select the "Multiple Lines" toggle in the Context Pane. You can then change the dimensions to fill any space.

Number

A number Input Widget is also similar to the previous two, as it will need to be assigned a Number variable to appropriately use the entered data. Select an existing variable, or create one by typing a name and selecting Create.

Once a Variable is added in this case, an additional option is revealed.

In the Format option, both Integer and Decimal can be selected for the display of the information. An Integer type will display only the whole number, while a Decimal will display up to the number of significant figures selected. The Precision option determines this number of figures to be displayed.

Single Select

To best use this widget, make sure you already understand arrays.

The single select Input Widget allows you to select an option from a list, with a number of powerful configurations.

One very simple way to use this is to assign or create a text variable in the Variable field, and display as a Dropdown with statically created values. You can add options by selecting 'New Option' just below the Options field. Once done, it will look like this:

If you change the Display field to a Menu, the widget will take on the following form for display:

You can also have the Options be listed as the parts of an Array variable.

In this method, all of the components of the selected array can be selected. To be clear, the Array is the variable selected beneath Options, and the Variable named 'Test' will store the user's selected value from the list of options.

Using the Array Variable configuration is extremely powerful, as it allows you to take options from the existing array, and also push new values onto the array to be selected. As an example, a button can add an option to this widget by adding a trigger. the trigger might look something like this:

In this example, the button adds the option 'Something New' to the Menu or Dropdown Input Widget.

Multiselect

The Multiselect option follows the same configurations as the Single Select widget, with one small configuration difference. The resultant output of this widget must be a Text Array, rather than simply a Text variable as in the Single Select widget.


This allows you to select multiple options from the Menu or Dropdown, and output them to an array variable. The configuration on view and select options are exactly the same as the Single Select widget options, detailed above. The Multiselect widget will display as below.


Date Picker

Once selected, choose or create a Datetime variable to associate with the widget. The output of the selected Datetime will store to the given variable.

The widget will then allow for the Datetime to be selected by the user within an App on a normal step. The interface will look like this in the Player:

Camera

The Camera widget allows the Player to take an image on a normal step. This widget will need an Image URL data type variable to store the image taken to an appropriate variable. Notably, the Aspect Ratio can also be adjusted within the Context Pane for this widget.

Once configured, users will be able to take images from the Tulip Player without needing to use a Form Step. Within the Player, users can also "Flip" and "Rotate" live view from the camera.

Did this answer your question?