A rule is triggered when a user attempts to “send” a business process record to the next step whose status activates the rule. For example, the rule may be designed to activate when a record gets to the Pending or Approved status. A rule can prevent the record from proceeding to the next step if doing so will violate the rule.
| • | Rules affect how users can work with: |
| • | Funding sheets (at project or shell or company level) |
| • | Project/Shell Cost sheets |
| • | Schedule of Values |
When you create a rule, you can designate specific groups or users who can override the rule exception.
When a rule violation occurs, Primavera Unifier displays a “Rule Exceptions” window.
If the user has override control, they can click Override to ignore the rule exception, or Cancel to accept the rule and remain on the step. If the user clicks Override, Primavera Unifier will ignore the rule exception and send information to the audit log about the override transaction.
Rule exceptions can be triggered by:
| • | Adding or copying a line item on the Cost Sheet |
| • | Copying data from one column to another on the Cost Sheet |
| • | Entering data directly into a cell on the Cost Sheet |
| • | A SmartForm that sends cost data to the sheet |
| • | An email action that sends cost data to the sheet |
| • | An integration transaction that sends cost data to the sheet |
| • | I Step and S Step business process auto-creation |
| • | A business process record that rolls up cost data to the sheet |
Note: Primavera Unifier does not display a Rule Exception window if the rule validation is triggered from a SmartForm, an email action, or integration. If the user has override control, Primavera Unifier will assume the user wants to override the rule exception and sends the override information to the audit log.
Oracle Corporation
Primavera Unifier 9.10 • Copyright © 1998, 2012, Oracle and/or its affiliates. All rights reserved.