Input Step
The Input step is used to collect data from users at a specific point in the workflow. It allows for the creation of a custom input form, typically utilised by requesters to enter their request details. These forms are specifically built for each request type and workflow, providing flexibility to address various customer needs. This approach enables each request to have a unique form rather than adhering to a standard template, ensuring better alignment with customer requirements.
The Input form configuration panel consists of the below configuration tabs. Details about configuring commonly used tabs are included in the Common Steps Configuration section. The configuration unique to the Input step is explained below.
And in the Advanced mode, additionally:
Form Fields tab (aka Input Fields)
The Input Fields tab is the core element of the Input step, enabling the definition of the form's content displayed to end users. See and example of an access request input form below.
All the fields shown above are added and configured in the Input Fields tab:
A Form Field / Input Filed Configuration
Filed
Identifies which global field is used to save and store the specific user input data captured by this form field.
Control Type
Each individual field on the input form is called a UI Control and can take the form of e.g. a text entry field, label, drop-down, checkbox, file uploader, etc., similar to typical online forms. The available UI controls include, for example:
Text Box: For entering text or numbers.
Dropdown, List, SearchMultiSelect: For selecting from predefined lists of options.
Date Picker: For choosing dates.
File, ImageUploader: For attaching documents or pictures.
Checkbox: For true/false choices.
Label, Message: For displaying information or instructions.
In the example above, Areas you need access to is a search drop-down list containing the available Command Centre Access Groups for user access requests.
Required Filed
Specifies whether the user must complete the field to proceed with the workflow and submit the form.
Input Value: Autofill
Fields can be automatically filled with data from the system (e.g., user’s name, department) and set as read-only if needed.
Display: Hide and Read Only
Input fields can either be visible for user interaction or hidden and used only for background processing.
Display: Read Only
The fields can be set to read only e.g. e.g. The RequesterName field can be autofilled with the logged-in user’s name and set as read-only, so the user doesn’t have to type it in.
Properties
UI Controls may have various properties that can be leveraged in the input forms. For example, the search drop-down list below allows for selecting multiple options.
Last updated
Was this helpful?