Submission Packages
Overview
Submission packages allow related forms to be grouped and submitted together.
Configuring Submission Packages
A submission package is defined using a form set with the “Submission Package” form set type.
A submission package can include multiple forms, with each form designated as required or optional. The first form, called the primary form, is always required.
A text field can be configured for the package to provide a package description or instructions to external users. This field supports HTML formatting.
A workflow that creates a new permit may only be added to the package’s primary form, to prevent confusion and the inadvertent creation of multiple permits from different forms within the package.
In nVIRO implementations that feature SLEIS integration, the submission package form set may also include a SLEIS application form.
Submitting a Submission Package
To submit a submission package, external users (or internal users on behalf of external users) complete and submit the individual forms, then submit the package as a whole.
For information on completing and submitting individual forms, see the Completing and Submitting Forms page.
Starting a Submission Package
External users can access submission packages through the Start New Form page. Submission packages display a View Package button instead of a Begin button.
Clicking the View Package button opens the submission package description, instructions, and a list of the required and optional forms in the package. Clicking the Show/Hide Instructions toggle shows or hides submission package instructions.
To start a form in the submission package, click the Begin button next to it.
Continuing a Draft Submission Package
Draft submission packages may be continued by navigating to the Submissions page using the site navigation menu, then clicking the Manage Package button next to the draft submission. This opens a list of all forms in the package and their statuses.
The overall package status is displayed at the top of the page, underneath the package number.
Clicking the Continue Draft button next to a draft form opens it for editing and submission. To delete a draft, click the Delete Draft button.
Forms with a Staged status have been signed and submitted but are awaiting submission of the full package. These forms can still be updated before the package is submitted by clicking the View or Revise button, then the Revise Submission button. To download a PDF of the completed form, click the Download button.
Deleting a Draft Submission Package
To delete a draft submission package, click the Delete Package button at the top of the page, then confirm when prompted.
Continuing a Submission Package from the External Dashboard
On the external dashboard, any submission package in In Progress or Draft status appears as a single card. Each card shows:
The total number of forms in the package
The statuses of forms in the package, including whether any corrections have been requested
The number of required forms in the package that have not been started
Submitting a Submission Package
When all required forms have been staged, click the Submit Package button.
If no validation errors are found, click the Submit button to submit the package and all staged forms to the relevant agency for processing. If validation errors are found (such as incomplete forms), the submitter can either acknowledge them and proceed by clicking the Agree and Submit button, or click the Cancel button to return and edit the package.
Revising a Submission
Once a submission package has been submitted, individual forms may be revised as needed (for example, to respond to a correction request). To revise a submission, click the Manage Package button, then click the View or Revise button next to a form to review or edit it. Forms designated as optional may also be started and submitted from the Manage Package page after the package is submitted.
Internal Processing
Submissions that are part of a submission package are processed the same way as individual submissions. However, submission packages have additional functionality to simplify navigation between forms and streamline status updates.
Viewing Package Submissions
When viewing a submission that is part of a submission package, a dropdown menu at the top of the page allows for toggling between other submissions in the package.
Submission packages offer an “As Needed - Allow Multiple Drafts” due date type, which allows multiple instances of the same form to be added to a single submission package.
Updating Submission Package Statuses
Submission packages have their own statuses, distinct from the statuses of the forms within it. The package status is shown in the right sidebar of the Submission Details page for all submissions in the package.
When internal processing for all submissions in the package is complete, click the Update Status button to update the package status.
When a submission package status is changed to Completed, the system validates all the submissions in the package, and the combined validation results are displayed in a validation results list. If no errors are found, the package status and the status of each submission are updated to Completed.
Impact of Submission Holds
If a Submission Package has one or more forms in On Hold status, then the following validations are applied:
If the user attempts to change the package to Complete, a Warning is displayed.
If the user attempts to set the permit to In Effect, a Warning is displayed.
The system defaults this to a warning, but if a client wants this to be an error, this can be configured in the environment.
Configuring Submission Package Certification Signatures
As of nVIRO 2025.1.00, administrators can configure a submission package to require a single certification signature, instead of requiring individual signatures on each child form.
Enabling Package-Level Certification
To enable this feature during Form Set configuration:
Edit a form set with the Submission Package context.
After enabling, a Certification Statement field will appear. This is a Paragraph Control where administrators can enter the language the external user will see at the point of submission.
HTML formatting is supported in this field.
The statement becomes required once the checkbox is selected.
Validation occurs on save:
If any child nFORM forms still have the “Signature(s) required” option enabled, an error will be displayed listing the conflicting forms.
All child forms must have individual certification disabled to proceed.
Behavior for SLEIS Forms
When the package includes a SLEIS form, that form bypasses certification when package-level signing is enabled. This ensures compatibility with SLEIS workflows while maintaining signature requirements at the package level.
Notes
The Save button may become disabled if the Certification Statement is empty after toggling the setting.
This feature supports use cases where one consolidated attestation is preferred over multiple individual certifications.
Related Features
This configuration is only available when the form set type is set to Submission Package.
Certification behavior is visible to the user during the final submission of the package, where the full package is signed once.
On this page
Related Content