Contributor - Starting a Late Exception Workflow

As an optional feature a Late Exception workflow can be forced on a contributor when they try to initiate an approval for an item where the Meeting Submission Date has already passed as shown below. There are 3 options to determine how reports are handled when a meeting deadline has passed, these settings are configured in the Report Settings (see "Administrator- Report Settings" for further reference). These setting options are: to allow late reports, only allow late reports with late exception workflow, and to not allow late reports at all.

Note: If Run Late Exception Workflow for Late Items in Settings has been selected by the administrator, then the contributor will be able to start the Exception Workflow instead of the standard workflow for that item. If it has been set to Not Allowed, then they will be unable to start the workflow and will have to select a future date where the submission deadline has not passed.

Note: to change how your system handles reports that have passed their submission deadline, please contact your administrator to make changes to the Report Settings.

To run the late exception workflow, go to Workflows in the report drop down menu, in the Start Approval Process screen select the required Late Exception Group and required Approval group (or add new approvers as users or meeting type) and click Start Workflow. A processing screen appears showing the workflow has started.

The Status of the report in the Item History changes to Approval Started (in the case of User as Approver) or Pending Meeting Assignment (in case of Meeting Type as Approver).

Note: Once the Submission Deadline has passed and the late exception workflow has started, approvals for the late exception workflow complete as normal. Once the late exception workflow has completed, then the regular approval workflow continues. The workflow is completed only when the last approver approves the report.

Related Articles: