eForm Terms and Icon Descriptions
Form Group. A group of forms that are designed together define a form group, also referred to as a form packet. For example, you may have a two-part form for a “Customer Complaint” request. Part 1 of the form may contain basic information about the problem, and part 2 may contain information on how you address the problem. You may want to break this into two separate forms to define the “Customer Complaint Group” or “Customer Complaint Packet.” Form 1 would be called “Complaint Information,” and form 2 would be called “Complaint Resolution.”
To determine if you should use multiple forms vs. one form, consider the following:
- Access permission. If different individuals need Read/Write permissions to one part of the form and not the other, multiple forms (pages) would be required in the packet. The eForms module establishes permissions on a form-by-form basis within an individual form group or packet. If you are using subforms and there is a workflow attached to the form, you are able to limit Read/Write permissions to the individual attached to the subform. A user table object list must be defined in the subform. The setting called Limit Edit to Subform would need to be set to Yes in the workflow.
- Length of form. If the form is lengthy, you might want to break it into multiple forms for improved usability.
Forms. The individual forms that make up a form packet. You can also think of a form as a page. You can have many forms/pages defined for an individual packet or just one form per packet. For example, a non-conformance packet may have two forms/pages. The first form allows for entering the non-conformances and the second form allows for entering the follow-up recommendation and preventative action information.
Packet. This is a group of individual forms which is sometimes referred as a Form Packet.
Fields. These are the individual data types added to the form, such as customer name, customer number, or product information. (Refer to “”Form Field Definitions” on page 11” in this chapter for more information on field definitions.)
Forms Activity Icon. Designates an activity for a form. Clicking this link for the activity displays the specific form on which the activity originated. If a user has Read/Write permission to the form, they will be able to enter information into the form. If a user has Read-Only permission, they will only be allowed to view information on the form. The description attached to the activity and icon will explain specific tasks that the recipient is requested to perform.
Workflow Icon. Designates that a workflow is attached to the form. This icon can be clicked to see the entire workflow status, or if you hover over the icon, the open current step of the workflow will display. The hover-over feature is active on the My TMS page, Activity Detail page, and Packet List page.
Signature Icon. Designates that an e-signature is required. This icon is the standard signature icon used throughout the TMS application. (Refer to Form Field Definitions).
Choose File Button. Allows for attaching an external (uncontrolled) file to a form. (Refer to Form Field Definitions).
Help Icon. Allows for the viewing of Help text added to the form. (Refer to Form Field Definitions).
Edit Icon. Allows for entering data into a free-use field on a form, editing a multi-level list or value map list.
Delete Icon. Allows for deleting either a multi-level list or a value map.
Ctrl key+mouse click. Allows for selecting or de-selecting multiple items when using drop-down lists or relationship grids.
Shift key+mouse click. Allows for selecting or de-selecting a group of items when using drop-down lists or relationship grids.