Whereas field-level rules control the behavior of specific fields within a record, family-level rules reside within the code item that represents an entity family and control actions performed against the entire record.
Family-level rules provide flexibility in determining how records will behave. Some of the most common uses of family-level rules include:
You can create family-level rules by developing custom code.
GE Digital APM supports the following family-level rule types.
Rule Type | Stores logic that is executed... |
---|---|
BeforeInsert | Before a record is created. |
AfterInsert | After a record is created. |
BeforeUpdate | After changes have been made to a record, before those changes are saved to the database. |
AfterUpdate | After changes to a record have been saved. |
BeforeDelete | Before a record is deleted. |
AfterDelete |
After a record has been deleted. |
A change to a record in the GE Digital APM database will trigger the appropriate rule regardless of the current user’s permissions. However, if a user does not have permissions for an action a rule is taking, the rule will not execute and the transaction will be rolled back and no changes will be made. Similarly, the transaction will be rolled back if an error occurs during the rule’s execution.
Copyright © 2018 General Electric Company. All rights reserved.