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.
Fields
All form inputs implement the following fields:
| Name | Description |
|---|---|
| Input Label | The text will be presented as the label for the input |
| Font Size | The font size of the input label |
| Font Color | The color of the input label |
| Font Style | Optional toggle for each: bold, italic and underline. Applies to input label only |
| Variable | An optional variable that will also link to the recorded form output |
| Required Field | Whether 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.
| Name | Description |
|---|---|
| Default Value | None, Yes or No |
Dropdown
An input that lets a user pick one text value from a list of options.
| Name | Description |
|---|---|
| Show as Buttons | Whether to present the selected value + a dropdown menu, or all the options in a list |
| Dropdown Options | Users specify the possible options. These can be grouped. |
| Default Value | None 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.
| Name | Description |
|---|---|
| Show as Buttons | Whether to present the selected value with a dropdown menu, or all the options in a list |
| Dropdown Options | Users specify the possible options. These can be grouped. |
| Default Value | None or any number of the listed options |
| Columns | Present the options in 1, 2 or 3 columns |
Text
An input that lets a user input a custom text response
| Name | Description |
|---|---|
| Multiline | Yes or no - whether the response is a single line or can have multiple lines. |
| Default value | Empty 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.
| Name | Description |
|---|---|
| Required Range | An 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.
| Name | Description |
|---|---|
| Input Options | Camera option only, upload only or enable both |
Tests
| ID | Name |
|---|---|
| QA-T107 | Signature Step : 02 - Signature widgets cannot be deleted from a signature form step and additional ones cannot be created |
| QA-T110 | Signature Step : 05 - Signature forms should only be submittable a single time per process run |
| QA-T153 | Form Widgets : 06 - Photo Widget |
| QA-T346 | Form Step - Create Form Step |
| QA-T347 | Form Step - Running the Form Step |
| QA-T483 | Form Widgets : 01 - Boolean widget |
| QA-T485 | Form Widgets : 02 - Dropdown widget |
| QA-T486 | Form Widgets : 03 - Multiselect widget |
| QA-T487 | Form Widgets : 04 - Text widget |
| QA-T488 | Form Widgets : 05 - Number widget |
Requirements
| ID | Requirement |
|---|---|
| PLAT-8743 (296) | Prompt for, verify and capture an e-signature as part of a step execution if an e-signature is required in the step's configuration |
| PLAT-8747 (302) | Ability 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. |
| PLAT-8748 (301) | Ability to re-execute process step respecting any constraints of the process step configuration in the process flow. |
| PLAT-8750 (300) | Provide a managed and authorized way to capture (log) and document any comments or exceptions during process execution. |
| PLAT-8752 (298) | Require 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 |
| PLAT-8764 (297) | Provide 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. |
| PLAT-8819 (27) | Provide 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 |
| PLAT-8847 (119) | Ability to configure procedural elements for work on orders, materials or equipment in a workflow |
| PLAT-8891 (816) | The manifestation of an electronic signature should contain the user's full name, date & time, meaning of signature human readable format; the record itself should contain these elements. |
| PLAT-8902 (817) | Ability to require multiple electronic signatures for a record. Ie co-signer, verifier, etc. |
| PLAT-8904 (820) | Electronic signatures have to be secured and not allowed to be falsified. They can only be used by their genuine owners. |
| PLAT-8905 (819) | All 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. |
| PLAT-8906 (818) | If more than one signature is required the electronic signature shall capture the role of each signatoree. Eg. trainer, verifier, co-signer, etc. |
| PLAT-8914 (99) | Ability 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. |
| PLAT-8921 (330) | Ability 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 |
| PLAT-8931 (19) | Provide the ability to configure an e-signature requirement for any master data definition or model's status transition in the approval workflow |
| PLAT-8980 (88) | Ability to designate certain content fields to be required for data entry |