...
Details Tab - Basic settings for the form behavior and usage
Dates and Deadlines Tab - Sets various date and deadline options for the form
Default Workflows Tab - Settings for one or more workflow to add to a new submission by default
Workgroup Routing Tab - Settings for which workgroup(s) should be assigned to the new submission
Form Sets Tab - Indicates whether the form is part of a Form Set or is used by a Schedule Type
Tags Tab - Lists the nFORM form sections and controls that make up the form
...
The following elements are displayed on the Details tab:
Field | Description |
---|---|
Short Form Name | This field may be used to specify an abbreviated name that will be used for display in internal list screens (e.g., My Tasks, Submissions Lists). This saves screen space and minimizes text wrapping when very long names have been used in the nFORM form configuration. If this field is left blank, the nFORM name is displayed in the list screens. |
Form Type | Each form must be assigned a Form Type. The default is "Unspecified" when a form is first created. The following types are available:
|
Program Component Type | Only visible when Form Type is set to Program Component. Allows for linking a form to a Component Type. |
Program Area | The program area that applies to the form. |
Form External Security Level | Indicates whether external users can view or use the form. Internal forms are typically used for rapid data entry of only key information off a received paper application. |
Fee Category / SKU Number / HotKey | Used for integration with financial systems. If a form has a fee associated with it, a Fee Category must be assigned before the form can be made available for use. |
Draft Submission Retention Days Before Deleting (Blank to Never Delete) | Submissions that have been abandoned will be deleted after the specified number of calendar days. There are currently no notifications associated with this function. |
Import Settings and Defaults | |
Assignment Type | Indicates whether new submissions should land in the inbox ("Manual," via the Submissions - Inbox page) or bypass the inbox and be automatically assigned to a workgroup/processor ("Auto Import"). |
Processor Must be Selected Before Import Checkbox | Only applies when Import Type is Manual. When this box is checked, a specific processor must be selected before the "Assign" button becomes available in the inbox. This setting controls whether the form is managed using "push" or "pull" processing. Push processing means that the person that monitors the inbox decides which specific processor should be assigned to a submission. Pull processing puts the submission in the "My Tasks" list at the Workgroup Level. Workgroup users would be trained to monitor the My Tasks lists for any submissions that are unassigned within their workgroup and assign them to themselves when they are ready. |
Entity Category to Create | Specifies the category of the entity (Site, Person, or Organization) that will be created when the form is submitted (if SITE tags are specified in the form). |
Default Program Components | Provides the ability to specify one or more program components that are automatically created when the form is submitted. |
Submission Reference Number Prefix | Allows configuration of a specific prefix for system-generated submission numbers. Note that this is separate from the nFORM reference number. |
Submission PDF and Attachments Security Classification | Determines the document security class setting for the submission form pdf and any attached files when the form is submitted. |
Summary Description Formula | A formula used to compose a summary description of data provided on the related form submission. If configured, the summary description text will appear on various screens, including My Tasks, Submissions - All, Submission Details. See this page for details. |
Other Settings | |
'Priority' Field Options | Defines the behavior of 'Priority' assignment fields for submissions associated with the form:
|
'Processing Hours Spent' Field Options | Defines the behavior of the 'Processing Hours Spent' fields for submissions associated with the form:
|
Processor Instructions | This field may be used to add instructions for the processor of the submission. It will display as a read-only field on the Submission Details page. |
Dates and Deadlines Tab
The Dates and Deadlines tab is hidden for Component and Schedule form types.
The following elements are displayed on the Dates and Deadlines tab:
Administrative Completeness Settings | |
'Application Review Complete Date' Field Options | Indicates whether the Application Review Complete Date field should be hidden, displayed/optional, or displayed/required. Required indicates that the field must be entered before the Submission status can be updated to "Closed". |
Allow Application Review Complete Date to be greater than Admin Complete Date | If unchecked, the user will be prevented from entering an Application Review Complete Date greater than the Admin Complete Date. |
'Administratively Complete Date' Field Options | Indicates whether the Administratively Complete Date field should be hidden, displayed/optional, or displayed/required. |
Days from receipt to determine Administrative Completeness | Creates a deadline for determination of administrative completeness. This setting can trigger notifications as the date approaches. The calculation uses calendar days. |
Automatically set Administratively Complete Date when date occurs | Indicates that, when the administratively complete due date comes to pass, the system will automatically set the admin complete date. This is performed as part of a nightly batch process. |
Holds and Extensions | |
Allow holds after Administratively Complete Date | If unchecked, users will be prevented from adding holds that begin or end after the administratively complete date. |
Hold duration affects Processing Deadline Date | Indicates that hold days should push out the processing deadline date. When an open hold is in place, the deadline date will be blank since it is indeterminate until all holds are ended. |
Allow Extensions | Indicates that the "Extensions" tab should be visible. This will extend the processing deadline date up to the maximum allowed processing days. |
Actions and Deadlines
Action Types and Deadline Rules can be configured at a form level. An action type indicates the type of processing the agency will perform on submissions using the form. The primary reason to assign an action type to a form is to configure one or more processing deadlines for that form.
...
For example, for the form in the following screenshot, the Processing Due Date has been configured as 90 days from the Application Administratively Complete Date. Because that field has not yet been populated, the Processing Due Date field is blank. Once the Application Administratively Complete Date field is populated, the system will automatically calculate the Processing Due Date.
...
Additional Deadline Settings | |
Maximum Processing Deadline Days | Indicates the longest possible period allowed for processing an application. Extensions will never be allowed to exceed this number. Value is either Business or Calendar days, as specified in the Day Interval Type used by the applicable Action Type/Deadline. |
Deadline Type | Indicates whether the deadline is a legal deadline (defined in a law or rule) or just an internal target. This setting has no bearing on system behavior. |
Default Workflows Tab
The Default Workflows tab lists the Workflow Templates that are automatically added to a submission upon receipt.
...
The Form Sets tab lists any Form Sets or Schedule Types that reference the current form. This is a read-only list screen. The Add Schedule Type button can be used to create a new schedule type that is based on this form.
...