Data Setup

Data Setup is used to associate your resources with apps thus adapting the behavior of the app to your specific needs or context of use.

Note: This guide is about Data Setup on the cloud.

Apps rely on standard resources that modify their behaviors and that must be identified and localized when the app is running and exploiting them. Apps describe the list of resources that can be customized. An administrator can associate resources with apps using the Data Setup app. These resources will then be associated with collaborative spaces. Resources can therefore be different depending on your projects.

Business Rules Capabilities

Amongst the resources that can be provisioned to apps (that include spreadsheets tables, catalogs, XML files, templates…), there is one particular kind of resource called 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 business rules are triggered in particular apps (for example, in the context of the Electrical Physical System Design app to validate the connection of a device) whereas some are triggered at lower level in the architecture, enabling deep customization of the data management behaviors.

  • Some are invoked on the server side during life cycle operations (maturity change, revisioning, transfer ownership, cloning, workspace delivery).
  • Some are invoked on the client side to implement object naming strategies, or rules for aggregating and inserting objects in structures. To know more, see Business Logic Implementations.
  • Some are invoked in standard User Interface components like PLM New or Edit properties to control the valuation of attributes. To know more, see Business Logic Implementations.
  • Some enables to enrich the data model of applications at runtime depending on the project. To know more, see Business Logic for Object Typing.
  • A particular business rules enables to choose a different policy for objects than the out of the box ones, thus enabling a customer to implement its own security schema. To know more, see Business Logic for Object Typing.