Versions Compared
| Version | Old Version 16 | New Version 17 |
|---|---|---|
| Changes made by | ||
| Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
About Forms
Forms are documents available to the public and internal users for submission. The form type distinguishes the purpose of the form. Form types include applications, service requests, permit change forms (modifications, renewals, transfers and, terminations), complaints, and schedules. Form submissions are the primary means of initiating a work activity in nVIRO. Forms are designed and managed by internal users with certain administrative rights.
Searching Forms
To manage forms, navigate to Admin > Forms. The Forms List screen will display.
Adding a New Form
At the top of the Forms list screen, two buttons are displayed to create a new Form:
- Add New Form - Creates a new regular form such as an application that can be made available to internal and external users for submission
- Add New Component Form - creates a new program component form. Component forms are customizable data entry screens that can be added to an item within nVIRO.
NOTE: Creating and Editing Forms are out of scope for this topic.
Editing Form Details
From the Form List page click the Open button to view the form details.
Depending on the form type, up to five tabs are displayed:
- 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
Details Tab
The following elements are displayed on the Details tab:
| Field | Description |
|---|---|
| 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 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 | |
| Import Type | Indicates whether new submissions should land in the InBox (manual) 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 is the difference between "push" versus "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 |
Dates and Deadlines Tab
The Dates and Deadlines tab hidden when for Component forms.
The following elements are displayed on the Dates and Deadlines tab:
| Administrative Completeness Settings | |
| 'Application Review Complete Date' Field Options'Application Review Complete Date' Field Options | |
| 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'Administratively Complete Date' Field Options | |
| Days from receipt to determine Administrative CompletenessDays from receipt to determine Administrative Completeness | |
| Automatically set Administratively Complete Date when date occurs Checkbox | |
| Holds and Extensions | |
| Allow holds after Administratively Complete Date Checkbox | |
| Hold duration affects Processing Deadline Date Checkbox | |
| Allow Extensions Checkbox | |
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. A single form can be configured to have one or more action types. For example, an application may have two action types, one for regular processing and one for expedited processing.
Deadline rules (clocks) are then assigned to each action type. This allows for multiple clock scenarios per form. Within these settings is the ability to allow for holds, the resetting of clocks after a hold has ended, and the differentiation between administrative completeness and technical review deadlines.
| Additional Deadline Settings | |
| Maximum Processing Deadline Days | Indicates the longest possible period allowed for processing an application. Extensions will never be allowed to exceed the 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 deadline (defined in a law or rule) or just an internal target. This setting has no bearing on system behavior. |
On this page
| Table of Contents |
|---|
Sub-Topics
| Page Tree | ||
|---|---|---|
|
Related Content