specs/models/M_APP_VER_STEP_FORM_INPUT

Form Input

Form inputs, which can only be used on Form Steps and Signature Steps are used to make forms that have a clear 'submit' action for clear record keeping in completion data. All form inputs implement the following fields:

NameDescription
Input LabelThe text will be presented as the label for the input
Font SizeThe font size of the input label
Font ColorThe color of the input label
Font Styleoptional toggle for each: bold, italic and underline. Applies to input label only
Variablean optional variable that will also link to the recorded form output
Required FieldWhether the input must have a response for the form to be submitted

Each form type also has unique fields according to its data type and interactions:

Boolean

A 3 state input that presents Yes and No buttons. One or neither can be selected.

NameDescription
Default ValueNone, Yes or No

An input that lets a user pick one text value from a list of options.

NameDescription
Show as ButtonsWhether to present the selected value + a dropdown menu, or all the options in a list
Dropdown OptionsUsers specify the possible options. These can be grouped.
Default ValueNone or one of the possible options

Multiselect

An input that lets a user pick multiple text values from a list of options. The options are displayed in columns.

NameDescription
Show as ButtonsWhether to present the selected value + a dropdown menu, or all the options in a list
Dropdown OptionsUsers specify the possible options. These can be grouped.
Default ValueNone or any number of the listed options
ColumnsPresent the options in 1, 2 or 3 columns

Text

An input that lets a user input a custom text response

NameDescription
Multilineyes or no - whether the response is a single line or can have multiple lines.
Default valueempty or a custom text value

Number

An input that lets a user input a custom number response. By default a "+" and a "-" button are presented for manual incrementing the value.

NameDescription
Required RangeAn optional min and max value the user can enter
Hide +/-yes or no - whether to show the value incrementing controls

Photo

An input that lets a user add an image either through the camera on the device or file upload.

NameDescription
Input OptionsCamera option only, upload only or enable both

Time

An input that lets a user select a time of day value, and does not include date information. Note, variables of type 'time' exist only in the context of this input and the data it saves. You may no longer add new Time widgets to apps. Please use the Datetime Input on normal steps instead.

Date

An input that lets a user select a date value, and does not include time information. Note, variables of type 'date' exist only in the context of this input and the data it saves. You may no longer add new Date widgets to apps. Please use the Datetime Input on normal steps instead.

Tests

IDName
QA-T107Signature Step : 02 - Signature widgets cannot be deleted from a signature form step and additional ones cannot be created
QA-T110Signature Step : 05 - Signature forms should only be submittable a single time per process run
QA-T153Form Widgets : 06 - Photo Widget
QA-T346Form Step - Create Form Step
QA-T347Form Step - Running the Form Step
QA-T483Form Widgets : 01 - Boolean widget
QA-T485Form Widgets : 02 - Dropdown widget
QA-T486Form Widgets : 03 - Multiselect widget
QA-T487Form Widgets : 04 - Text widget
QA-T488Form Widgets : 05 - Number widget
QA-T489Form Widgets : 07 - Time widget
QA-T490Form Widgets : 08 - Date widget

Requirements

IDRequirement
19Provide the ability to configure an e-signature requirement for any master data definition or model's status transition in the approval workflow
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
88Ability to designate certain content fields to be required for data entry
99Ability to display the acceptable quality limits to the operator during the execution with an indication of whether the current value is inside/outside the limits.
119Ability to configure procedural elements for work on orders, materials or equipment in a workflow
296Prompt for, verify and capture an e-signature as part of a step execution if an e-signature is required in the step's configuration
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.
298Require e-signature for exception of specific configured risk categories. Ie for high severity or high risk exception require the capture of an e-signature in the history record
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.
330Ability to automatically or manually log an exception when data is not within configured limits and tolerances. Disallow process completion until exceptions have been logged with configured e-signatures and any authorized overrides have been processed e.g. supervisor signature, scrap, etc.
816When capturing/acquiring an electronic signature the user must be able to see in human readable format the user's full name, date & time, meaning of signature; the record itself should contain these elements.
817Ability to require multiple electronic signatures for a record. Ie co-signer, verifier, etc.
818If more than one signature is required the electronic signature shall capture the role of each signatoree. Eg. trainer, verifier, co-signer, etc.
819All electronic signatures have authenticate the signatoree by two distinct elements (e.g. username and password; at least one being a private element), or a secure unambiguous biometrics system that cannot be used by anyone other than their genuine owner.
820Electronic signatures have to be secured and not allowed to be falsified. They can only be used by their genuine owners.