About Changing Schema

Many aspects of the app are controlled through the administrative objects installed with the 3DEXPERIENCE platform. 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 MQL.

When changing schema, remember these important points:

  • When changing names of administrative objects, change only the admin object name, not the symbolic name.
  • If 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 app uses a string resource properties file to internationalize all on-screen text, including schema names, changing schema names does not change the names displayed in the user interface. For instructions on how to change schema names in the user interface, including policy states and attribute ranges, see the Collaboration and Approvals Administration Guide.