Data Model Customization allow to:
- Prevent administrators from modifying the assets installed by our platform. By doing so, you are ensured that the installation of a new software version will run correctly (no need to merge your modifications with Dassault Systèmes ones).
- Perform administration, configuration or customization tasks in a cloud environment without stopping the services.
- Ensure that administration work is complete and applies to a wider context (for example, introduction of persons in all services of the 3DEXPERIENCE platform.)
The following actions can still be performed in MQL:
- Creation of vaults and stores
- Definition of customer specific security scheme.
- Introduction of new maturity graphs with new states
- Definition of triggers for web apps. For work in progress native client apps, this is done through business rules
- Customization of web forms
- Migration of customized data
The following actions shall not be performed using MQL:
| Intent | Tool to Use |
|---|
| Data model customization | Data Model Customization tools. |
| Definition of password for a person, or connection to LDAP | 3DPassport administration tools. |
| Creation of person, organization, roles, collaborative spaces | PLM Pos Import tool or interactive administration capabilities. |
| Definition of triggers for work in progress native client applications | Data Setup. |
| Definition of naming rules or revisioning naming rules | 3DSpace Control Center widget. |
| Creation of dimensions and units | The list of dimensions and units is fixed now. If you introduce a new dimension, it will be taken into account only in web apps. |
Note:
You cannot delete users using MQL if that user was created for the
3DEXPERIENCE platform using the Members & Roles app.