Short Form Name

An abbreviated form name to display on internal list pages.

A short form name saves screen space and minimizes text wrapping when the full form name is very long.

If this field is left blank, the full form name from nFORM is used on the list pages.

Program Area

The program area to which the form applies.

Form Type

The form type. Options include:

• Application: The most common type. Allows users to complete and submit the form online.

• Service Request: Similar to an application, but used for non-permitting activities.

• Package Form: Available only within a submission package form set. For more information, see the Form Sets page.

• Permit Change: Available only in the context of an existing permit. Can be configured to prepopulate permit details, such as the permit number, dates, category, and type. 

• Schedule: Available only in the context of an existing permit, compliance action, or environmental project activity, or if triggered by another submission. For more information, see the Managing Form Sets page.

• Complaint: Similar to an application or service request, but used for complaints.

• Program Component: A customizable data entry screen. Must be configured under Admin > Lookups > Component Types.

New forms are set to “Unspecified” by default.

Program Component Type

The linked program component, if applicable.

This field is only visible when Program Component is selected in the Form Type field.

Form External Security Level

External visibility and access settings for submissions. Options include:

• View: External users can view submissions.

• Edit: External users can create and edit submissions.

• Internal: Neither forms nor submissions are visible to external users.

• Restricted: External users that have been explicitly granted access to the form can create and edit submissions.

New forms are set to “Edit” by default.

Internal forms are typically used for quick data entry of key information from a paper application.

For more information on external security levels, see the Restricting Forms and Submissions to Specific Users page.

Draft Submission Retention Days Before Deleting (Blank to Never Delete)

The abandoned submission retention period.

Submissions that have been abandoned will be deleted after the specified number of calendar days.

To never delete submissions, leave this field blank.

Notifications to inform users of pending deletions may be configured via system actions.

Import Settings and Defaults

Assignment Type

The submission routing preference. Options include:

• Manual Assign (Use Inbox): New submissions appear on the Submissions - Inbox page.

• Automatically Assign (Bypass Inbox): New submissions bypass the inbox and are automatically assigned to a workgroup or processor.

Processor Must be Selected Before Import

The option to require that a processor be selected before the Assign button becomes available in the inbox.

This field is only visible when “Manual Assign (Use Inbox)” is selected in the Assignment Type field.

This setting determines whether the form uses “push” or “pull” processing. In push processing, the person that monitors the inbox assigns submissions to specific processors. In pull processing, submissions appear in the workgroup’s My Tasks list, where users can claim unassigned submissions.

Entity Category

The category of the entity created when the form is submitted (site, person, or organization).

This field applies if site tags are used in the form.

Default Program Components

Program components that are automatically created when the form is submitted.

Submission Reference Number Prefix

A specific prefix for system-generated submission numbers.

This is separate from the nFORM reference number.

Submission PDF and Attachments Security Classification

The security class setting for submission PDFs and attached files. 

For more information, see the Submission PDF File Naming page.

Submission PDF File Naming Scheme

The file naming convention for submission PDFs.

Summary Description Formula

The formula used to generate a summary description of new submissions.

If configured, the summary description will appear on various pages, including My Tasks, Submissions - All, and Submission Details. For more information, see the Configuring a Summary Description Formula page.

Financial Settings

Fee Category / SKU Number / HotKey

The fee category or other financial system identifier.

Data entered in this field is 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.

Allow Additional Fees to be Added After Import (e.g. Expedited Review Fees)

The option to allow users with the “Submissions - Manager - AddFee” role to add fees to submissions of this form.

Other Settings

'Priority' Field Options

Submission Priority field behavior. Options include:

• Hidden: Priority fields are hidden and do not display on the form.

• Optional: Priority fields are displayed but not required. 

• Required: Priority fields are displayed and required to change the submission status to Completed.

'Processing Hours Spent' Field Options

Submission Processing Hours Spent field behavior. Options include:

• Hidden: Processing Hours Spent fields are hidden and do not display on the form.

• Optional: Processing Hours Spent fields are displayed but not required. 

• Required: Processing Hours Spent fields are displayed and required to change the submission status to Completed.

Processor Instructions

Instructions for the submission processor.

Text entered in this field displays as a read-only field on the Submission Details page.

Data from submissions using this form can be copied to new submissions.

The option to enable a Copy Submission button for submissions of this form on the Submissions Search page.

This option is only available to external users on submissions that were submitted by external users.

Clicking the Copy Submission button copies the submission as a new draft. The user is prompted to select an existing site or create a new one as the destination site for the copied submission. Once copied, the draft submission opens for editing.

To use this feature, the form must be configured in nFORM to inherit from itself, with mapped controls specifying which data should be copied. This allows new submissions of this form to automatically inherit data from the previous submission, if one exists.