Create a rule template

You are here: Primavera Unifier Administration Mode > Cost Management Setup > Setting up the Rules Engine > Create a rule template

Create a rule template

You can create a rule template, or a rule within a project or shell template. By default, rule templates remain inactive; the Validate, Activate and Deactivate buttons on the toolbar are disabled. Rules within project and shell templates can be validated and activated.

You can create a new rule manually or by copying an existing rule. If you create a rule within a project or shell template, the rule can be “pushed” to existing projects or shells.

To create a rule template

Go to the Company Workspace tab and switch to Admin mode.

In the left Navigator, click one of the following:

•

Company Workspace > Rules

•

Templates > Rules

•

Templates > Projects (Standard) > [project] > [template] > Rules

•

Templates > Shells > [shell] > [template] > Rules

Note: At the Template > Shells level, you can create rules only for WBS shells, not generic shells.

Click New. The Create a New Rule window opens.

Select the Control Source and Rule Level.

Note: For details on choosing the source and level, see "About control sources and levels".

Click OK. The Edit Rule window opens.

Use the information in the following table to complete the fields on the General tab.

In this field:

Do this:

Name

Enter a name for the rule.

Description

Enter a description of the rule.

Control Source

Primavera Unifier displays the control source you chose in this field.

Rule Level

Primavera Unifier displays the rule level you chose in this field.

Status

Primavera Unifier displays the current status of the rule.

Users/Groups who can override

(Optional; appears only at the project and shell templates level)

This option is available only for the following rule levels:

•

Per selected summary WBS codes

•

Per selected WBS codes

Click the Select button and from the picker that appears, select the users or groups that will be allowed to override this rule at runtime.

If you select this option, the specified users/groups should be able to override a rule failure condition during a workflow. Primavera Unifier will display the name(s) of the overriding user(s) and any comments in the Audit Log.

Note: If you use this option, users/groups can override this rule, even if the data is not valid. Also, the users/groups specified in this option will be added to the project/shell if they do not already exist there

Notify Users/Groups when overridden

(Optional; appears only at the project and shell templates level) Click the Select button and from the picker that appears, select the users or groups that should be notified if this rule is overridden.

Click the Rule tab and complete the fields using the information in the following table.

In this field:	Do this:
Limit Expression	This defines the Upper Limit that the rule validates against and is static. For example, for cost rules, this might be the Assigned Budget, or can include the sum of several budget-related data sources on the cost sheet. Click the Formula button. The Formula Creation window opens. The data source list includes all available cost sheet data sources for cost-related rules, or funding sheets data sources for fund-related rules. This is the value on the left of the Condition. Pending positive values are not considered.
Condition	The option “greater than or equal to” is the only selection available. Rules always check that the “Upper Limit” (Limit Expression) is greater than or equal to the amount calculated by the Data Expression.
Data Expression	This is what is being validated. For example: Purchase Order (Pending) + Purchase Order (Approved) + Change Commit (Pending) + Change Commit (Approved) Click the Formula button. The Formula Creation window opens. The data source list includes all available cost sheet data sources for cost-related rules, or funding sheets data sources for fund-related rules. This is the value on the right of the Condition. Pending negative values are not considered.
Show this message when condition is not met	This field is required. Enter a message to display to users if the rule condition is not met.

In project or shell templates, if you chose “Per selected WBS Summary Codes” or “Per selected WBS Codes” as the rule Level, then the WBS Codes tab appears in the Edit Rule window. See the following procedure for selecting WBS codes.

Click OK to save and close the Edit Rule window.

To select WBS codes or summary codes

In the Edit Rule window, click the WBS Codes tab. (This tab is available if you chose “Per selected WBS Summary Codes” or “Per selected WBS Codes” as the rule Level.)

Click Add. The WBS Picker opens.

•

If you chose “Per selected WBS Summary Codes,” the picker displays the summary WBS codes on the sheet. This is only applicable if the project/shell cost sheet uses a tree structure. Cost sheets with flat structures do not have summary WBS codes.

•

If you chose “Per selected WBS Codes,” the picker displays the “leaf” WBS codes (individual, non-summary codes). This is applicable for both tree and flat cost sheets.

Select one or more codes from the picker and click Select.

To locate the WBS codes you need, you can click the Find button in the WBS Picker. For tree structure cost sheets, you can also click Expand or Collapse to help you navigate the code structure.

After you select the WBS codes, they are listed in the WBS Codes tab. You can add as many WBS codes as needed. At runtime, the rule will be applied only to the WBS codes selected.

Note: Summary WBS codes must all be at the same summary level (i.e., the same indent level).

For Validation, choose one of the following:

•

Validate total of selected rows: the system will calculate the sum of the selected WBS codes and then apply the rule to the total

•

Validate selected rows independently: the system will apply the rule to each selected WBS code individually

To remove a WBS code from the list, select it and click Remove.

Click OK to save and close the Edit Rule window.

Note: If you add a WBS code or summary code to this list and it is later removed from the cost sheet, the rule will not be affected. The code will still appear on the WBS Codes tab. At runtime, the rule engine will ignore the code that was removed from the cost sheet. Similarly, in a tree structure, if a summary code is changed to a leaf code (or vice versa) after adding it to the WBS Codes tab, at runtime, the rule engine will ignore the code that was changed and not create an error.

Oracle Corporation