Do you know that there are more than 900 business logic included with your 3DEXPERIENCE Installation?

During a DELMIA Process Engineering implementation you may need to adapt some of them in order to automatize some behaviors and improve the User Experience.

With the help of our DSGS colleagues we have decided to list the most used one and explain how they works.

If you want to have more or you have some particular use cases to investigate, do not hesitate to comment this page.

Execution Context

For each business rules there is an execution context that is Server side execution and Client side execution as described below. This category is based on the business rules execution, some business rules that are executed on the Client side are called Client side Business rules and rules that are executed on Server side are called as Server side business rules.

This page will contain links to collection of most commonly used Client BLs and Web BLs.

• Client BLs​​​​​​​
• Server BLs​​​​​​​

About Business Rule

• A business rule is a piece of logic that will be triggered during the execution of an app to make decisions or prevent an operation. The logic is described using the Enterprise Knowledge Language that enables to manipulate almost all the objects of the different apps.
• Some are invoked on the server side during life cycle operations (maturity change, revision change, transfer ownership, cloning and workspace delivery). 
• Some are invoked on the client side to implement object naming strategies, or rules for aggregating and inserting objects in structures. 
• Some are invoked in standard User Interface components like PLM New or Edit properties to control the valuation of attributes.  

There are three kinds of customization intent:

• Validation: the objective is to validate or invalidate a treatment (ex: aggregation check)
• Computation: the objective is to compute something (ex: Color & Icon masks)
• Execution: the objective is to operate modifications on objects (ex: attribute initialization)

​​​​​​​

Who is interested?

1. Administrators (at customer site) will create some business rules to change the behavior of the 3DEXPERIENCE system & applications, in order to adapt them to their business processes
2. DS Developers will also deliver business rules default implementation for their modelers

Where it is used by administrators & DS developers?

At infrastructure level

1. Identification Business Logic: enables to pre-valuate the attributes of PLM objects in creation phase (new, duplicate, save as, implicit creations)
2. Attribute Propagation Business Logic: enables to propagate some modifications of attributes after the edition of some attributes of PLM objects (edit, new, sheet editor)
3. Attribute check Business Logic: enables to validate the modification of attributes of PLM objects after edition & propagation (edit, new, sheet editor)
4. Import / Export Business Logic: enables the valuation of PLM attributes during an import process, and the valuation of file names during an export
5. Aggregation check Business Logic: enables to validate aggregation rules before aggregation of a PLM Reference or a PLM Representation in a PLM reference

At application level

1. Behavior validation: enables to validate the creation of a new behavior or its instantiation under a given reference.
2. Template instantiation naming Business Logic: enables to valuate PLM attributes on elements of a template before instantiation
3. Component family maturity change Business Logic: enables to define the transitions to operate on a family item to make it non editable
4. Component family items naming Business Logic: enables to define a strategy for naming generated family items, based on keywords values of generic

At navigation level

1. Color & icon masks computation Business Logic: enable to customize background color & icon masks for visualized products in navigation tree
2. Compass customization Business Logic: enable to classify the visualized products in different customer categories accessible through compass