Change Order Approval Required Rules

Rules can require approval through a change order when certain changes are made to an item.

Change order approval rules are defined and managed through BPM Worklist.

Approval required rules are triggered when you make these changes to an item and will add the changes to a new or existing change order.

Approval required rules are supported for the following areas:

  • Items

  • Item revisions

  • Item supplier

Changes to item attributes and structures fall in item and item revisions.

Changes to item revision attributes and item supplier associations fall in item supplier.

If an approval required rule is triggered on any item changes that fall into one of the areas, then all changes authored for that item that fall in that area will be added to a change order.

For example, a rule is defined that requires approval if a primary structure is created for any item.

During a single session directly editing an item, a user changes the value of an item level attribute and then creates a primary structure for that item.

On saving the data, the approval required rule will be triggered because of the new primary structure and the user is prompted to either create a new change order or add to an existing one.

When the new change order is created or an existing change order is updated, then the change to the value of the item attribute will also get added to the change order along with the primary structure change for required approval.

Example of Approval Required Rules and Approval Groups

The approvals can be from individual users or from multiple users in a predefined user group. Because individual rules can be made for specific item revisions, attributes, or structures one rule can require approvals from one user group when an attribute is changed, while changes made to a different attribute will require approvals from a different user group.

For example, the new primary structure rule that requires approvals from members of the TestApprovalGroup user group.

Another rule is defined that requires approval if the scheduled date when changes will be implemented for an item is later than the date 01/01/2012, then approvals are required from the COApprovalSAG approval group

This means that if the user creates a primary structure for that item, and specifies a scheduled date for the item that's later than 01/01/2012, approval responses are required from both the COApprovalSAG and TestApprovalGroup approval groups.
Note: When creating the rule, you can click the magnifying glass icon to perform an advanced search using the condition browser.
The figure shows the condition browser