Definition Objects

Many of the selectable fields are definition objects (type, policy, vault, etc.). You access the definition information through the select mechanism.

This information is less likely to be used by ENOVIA product users, but is useful for system integrators who may have to build programs and need to understand the internal details of the schema being used. Since all definitions have some relationship to business objects, they can be accessed from them (and, therefore, from the application rather than the Business Modeler) when needed. For example, expanding:

policy.type[].*

yields (among other things):

policy.type.policy[].*

A business object is governed by a policy. That policy can govern other object types. These types can have other governing policies.

The first policy is not followed by square brackets. This is because a business object instance can have only one governing policy. By contrast, the second policy is followed by square brackets because a type definition can have many optional policies. The connections can be illustrated as: