Conditional Routing of Requests for Approval
The Maximum Rule Severity to Auto Approve property allows the system to automatically approve requests when the rule severity produced by the request is equal to or less than the severity defined in Maximum Rule Severity to Auto Approve.
Alternatively, the system can determine that manual approval is required when the request's rule severity violation exceeds the severity defined in Maximum Rule Severity to Auto Approve or prevent the request from being submitted. The Maximum Rule Severity to Auto Approve property is available in these request subtypes:
- Cover
- Open Shift
- Swap
Schedule rules severity levels
Schedule rules are used to maintain compliance with scheduling policies and practices. Each rule is assigned a severity level that determines its importance. You specify the severity of each rule violation in a schedule rule; you define how you want the system to respond when a request violates that severity rule using the Maximum Rule Severity to Auto Approve and Minimum Rule Severity to Block Submission request subtype properties.
Severity levels have a hierarchy, from least to most severe:
- Not Considered — The system ignores schedule rules with a setting of Not Considered. There is no impact on whether the request can be submitted for violations to Not Considered severity rules.
- Informational — Requests that violate rules of Informational, Warning, and No Save severity are not submitted.
- Warning — Requests that violate rules of Warning or No Save severity are not submitted.
- No Save — The employee cannot submit requests that violate rules with No Save severity.
When does validation occur?
The system validates the request when the employee submits it. What happens next depends on these factors:
- The severity of the rule that was violated, if any (as defined in the schedule rule)
- How the Minimum Rule Severity to Block Submission and Maximum Rule Severity to Auto Approve fields were configured
The request is either:
- Automatically approved,
- Submitted to the approving manager for review, or
- Blocked from submission
Consider this simple example:
- Minimum Rule Severity to Block Submission is set to No Save
- Maximum Rule Severity to Auto Approve is set to Informational
| Severity Rule Evaluation | Result | Comment |
|---|---|---|
| No severity rules were violated | The request is automatically approved | When there are no severity rule violations, submitted requests are automatically approved. |
| An Information severity rule was violated | The request is automatically approved | The request is automatically approved because the severity rule violation is not greater than Information. |
| A Warning severity rule was violated | The request is submitted to the manager for review | The request cannot be automatically approved because the severity rule violation is greater than Information. |
| A No Save severity rule was violated | The request is not submitted | The No Save severity rule violation prevents the request from being submitted. |