Field Editor – Top Section
Layout View — To return to the layout view where you can add/move groups and fields, click on the “Layout View” with the back arrow.
Field Name is used in some of the other field configuration options, such as picking fields for calculations (see below)
Control Type is used to select how the field input works (numeric, text, date, etc.) When you change this value, some other options might appear such as when you select Text Area or Drop Down.
Control Types include:
- Text Box (Single line of text)
- Text Area (Multiple lines of text and optionally rich text editor)
- Drop down (Driven by lists)
- Check Box
- Radio Buttons
- Password (hides input)
- Assigned To ( to show whom the form is assigned to)
Required, when checked, will not allow the form to be saved until the form’s users enter a value.
Initial Focus will cause the field to have the cursor and be ready for input when the form opens.
Field Editor – Labels
The Labels section will allow you to specify a label that appears next to the field.
Show Label — If you prefer not to show a label for your form (which will make your eForm field display narrower), uncheck the checkbox. A common use is if you have a text area with a separate field of type Label above the text area and want to increase the amount of width used by the text area.
Language-specific Labels — Depending on the language(s) you have selected for your eForm, you can enter the text to match that language. In the example above, English, German, Spanish and French are all valid languages for this eForm.
Field Editor – Layout
The Layout section enables you to specify where and how the field displays within the group.
Width (%) — This is the relative width within the column. It may be useful, for instance, in a shorter column such as a date field, to make the input match the width of the data that is being captured. It is very useful when the group layout is Row Layout., This layout is commonly used to show lines items on sales orders or an invoices. It is necessary to decide the width of fields so they can be represented horizontally without wrapping.
Column — This shows the column for the field, which is used for 2-column groups. You can change it here, and you can also change it by dragging and dropping the field on the Field Layout view.
Field Editor – Default Value
The default section causes the eForm to automatically enter a value, which can by static (fixed value) or dynamic
Dynamic — Depending on the field type, the select list will allow you to select either “None” or calculated values like user name of the logged-in user, current date, current week, etc. For example, with a text box, if you select User Name, the name of the user who is logged in will automatically populate the field. This could be useful if the field is a vacation request, and you want the employee’s name to automatically populate as the logged-in user.
Static — To enter a fixed value for a field’s initial value, just type it here.
Field Editor – Metrics Settings
The Metrics Settings section defines how the field displays in the metrics (requires a subscription)
Use For Metrics — By checking this checkbox, the value of this field will be stored in ProcessMetric’s data warehouse for reporting.
Metric Field Name — This is the description of the metric that will show up when rendering the data. Typically this will match the field label.
Type — This is the type of the data you want to store. There may be instances where you wish to capture numeric data but report on it as a text value. For instance, if you are capturing the number of the month December as 12, but want to report on it in a histogram, you may want it treated as categorical vs. numeric data.
inbox Field Number — On the inbox page, there exists a view setting of “Field Data.” This view displays up to four pieces of data about each eForm. For instance, if you have an RMA eForm, you may want to show the customer, invoice number, and return amount on the inbox page to help customer service representatives more easily find the correct RMA eForm they are looking for.
Field Editor – Form Statuses
The Form Status Settings section controls the field-level security for internal and external users. External users are users who do not belong to your company, typically a business partner such as a customer, vendor.
Fields can have three states for each status: Edit, Read Only, or Hidden. It is common to have more restrictive values for external users, only allowing them to edit the fields that you want them to. For instance, with an Return to Manufacturer Authorization, you may want them to be able to edit the reason for the return, but restrict them from editing the field that actually authorizes the return.
IMPORTANT: Groups have these same status controls. If a group specifies a more stringent state (such as Read Only), the group will override the field-level security.
New — Sets the state when the eForm has been loaded, but has not yet been saved. Typically this will be an Edit status unless you specify a default value that you don’t want overridden, such as the dynamic user name value.
Submitted — The first time an eForm is saved (not including when it is New), it enters a Submitted state.
In Process — Each subsequent save, up to the point it is Archived, the form will be in an In Process state.
Archived — Finally, when the form is complete, it goes into an Archived state. Typical use here is to make the fields read-only to lock their values.
Field Editor – Calculation
When you select a field type (in the top section) of Numeric, the option to include a calculation appears in the form editor.
Use in a Calculation — When you check the box, the options above appear
Arithmetic — What kind of operation to you want to perform. Choices are Add, Subtract, Multiply, and Divide.
Target Field — This is the field into which the calculation result will be stored. For instance, this field contains a numeric value representing a dollar amount of a line item, the target field may be a “grand total” field on the document. If all line items have this same calculation configuration, the grand total will add up all of the line items’ values.
Scope — Scope can be Document or Group. Sometimes you want to perform operations at a group level rather than a document value. For instance, consider a group that represents a line item on an invoice. It has numeric fields Quantity, Price and Total. To calculate the line-item total, “Quantity” and “Price” fields would have a “Multiply” arithmetic operation with a Target Field of “Total” and a Scope of “Group.” If the eForm also had a “Grand Total” field on it, then the line item “Total” fields would have an “Add” arithmetic operation with a Target Field of “Grand Total” and a Scope of “Document.”