About Changing Schema

Many aspects of the application are controlled through the administrative objects installed with the ENOVIA Live Collaboration. For example, the policy that governs a business object type controls who can work with that kind of business object, what they can do, and during which states. All these changes can be made using Business Modeler or MQL

When changing schema, remember these important points:


  • When changing names of administrative objects, change only the admin object name, not the symbolic name.
  • Whenever you remove the Originator attribute from a type, make sure you turn off the trigger that populates the attribute by removing the Create and Revision triggers from the type.
  • Because the application uses a string resource properties file to internationalize all onscreen text, including schema names, changing schema names does not change the names displayed onscreen. For instructions on how to change the onscreen names for internationalized schema, including policy states and attributes ranges, see the Business Process Services Administrator's Guide.