Item Rules to Restrict Operations on Attributes, Structures, and AML for Engineering Items
You can define rules that restrict add, edit, and delete actions on entities such as attributes, structures, and AML respectively.
When a user creates item data or performs any changes for any of these entities, the respective rule is triggered.
Control Operations on Item Attributes
You can create a validation rule to control editing the item attributes.
For example:
Severity: Needs Approval
*Change Order Type: <CO Type>
[Item].[MAIN].[Preliminary] == 'No' AND changedItemAttribute( )
Validation Condition: False
You can specify the association of the rule set as root item class and add it to the master rule set.
This rule will be triggered when a user tries to update item attributes such as item basic, main, operational, and extensible flexfield attributes for an item that isn't a preliminary item.
Control Operations on Item AML
You can create a validation rule to validate create, read, update, and delete operations on item AML.
For example:
Severity: Needs Approval
*Change Order Type: <CO Type>
[Item].[MAIN].[Preliminary] == 'No' AND changedAML( )
Validation Condition: False
You can specify the association of the rule set as Root Item class and add it to the Master rule set.
This rule is triggered when a user tries to create an MPN relationship for an item that's not a preliminary item, edit it, or delete it.
Control Any Action on Item Structures
You can create a validation rule for a specified item structure to control any changes to the structure.
For example:
Severity: Needs Approval
*Change Order Type: <CO Type>
[Item].[MAIN].[Preliminary] == 'No' AND changedItemStructure ( )
Validation Condition: False
You can specify the association of the rule set as Root Item class and add it to the Master rule set.
This rule is triggered when a user tries to perform an action on the structure, such as adding or updating a component, adding a substitute, and adding a reference designator of any item that isn't a preliminary item.