About Precommit Triggers

1. In a development environment, open Data Setup and do the following:
   1. Create a precommit-trigger business rule. For more information, see Creating a Business Rule.
      Note: You can only create business rules and resource sets for precommit triggers when Data Setup is in the development environment.
   2. Deploy this business rule. For more information, see Deploying and Undeploying a Business Rule on the Server.
      Note: Precommit-trigger business rules do not require you to bind them to a collaborative space in Data Setup beforehand.
   3. Export the server business rules. For more information, see Exporting the Server Business Rules.
2. To import these server business rules into another platform, open a Enterprise IP Schema Specialization widget and import them. For more information, see Installation and Setup: 3DEXPERIENCE Platform: 3DEXPERIENCE Configuration and Customization: 3DSpace Data Model: Enterprise IP Schema Specialization: Importing Business Rules.

When you create a business rule with a precommit trigger opening, the system follows a specific order of operations that differs from the order of operations that it follows for any other kind of openings.

When a user executes a transaction that depends on a precommit trigger business rules, the following occurs:

1. The kernel registers the transaction.
2. The kernel executes the command (for example, promote).
3. The kernel fires the precommit trigger.
4. If no error occurs, the kernel commits the transaction. Otherwise the transaction is aborted.

In non-private cloud environments, resources (database, memory, and CPU) are shared across several customers. As a result, precommit trigger business rules must use these resources reasonably. This is enforced by the execution control mechanism, whose role is to authorize or forbid the execution of EKL functions based on the following:

• The EKL function profile card: Each EKL function declares a Performance Capacity and Scalability (PCS) profile based on its consumption of resources (metadata, database).
• The execution context: The opening type, the objects in the transaction, and the perimeter of the function.

For more information, see 3D Modeling: Multi Discipline Automated Engineering: Enterprise Knowledge Language: Server Types and Functions: EKL Profile Cards.

The table below lists all existing precommit trigger openings.

Opening ID	Description	For more Information, see...
batchclone	Clones a bunch of objects.	Batch Clone (batchclone)
batchrevise	Revises a bunch of objects.	Batch Revise (batchrevise)
changename	Changes the name (TNR) of the object.	Change Name (changename)
changeowner	Changes the owner of the object.	Change Owner (changeowner)
connect	Creates a relationship.	Connect (connect)
copy	Creates a copy of an object.	Copy (copy)
create	Creates a BusinessObject.	Create (create)
delete	Deletes a BusinessObject.	Delete (delete)
demote	Changes the object maturity, moving it backward in the maturity graph.	Demote (demote)
disconnect	Deletes a relationship.	Disconnect (disconnect)
majorrevision	Creates a new major revision of an object.	Major Revision (majorrevision)
modifyattribute	Modifies an attribute of an object. Warning: This trigger is also fired at create.	Modify Attribute (modifyattribute)
modifydescription	Modifies the description of an object. Warning: This trigger is also fired at create.	Modify Description (modifydescription)
promote	Changes the object maturity, moving forward in the maturity graph.	Promote (promote)