What's New

This section describes recent changes in MQL.

This page discusses:

R2022x FD01 (FP.2205)

Shortbinary attributes with multiple values
You can now add multiple values to attributes of type shortbinary. For more information, see Type Clause for the Add Attribute Command.
Attributes with no default values
You can now define an attribute to have no default value by using the !hasdefault clause. Attributes can be defined as !hasdefault for businessobject, connection, and paths. You can also use the selectable isset to identify is an attribute is defined as !hasdefault. For more information, see Type Clause for the Add Attribute Command and Using .isset.
Transition a Relationship Type
You can now select a set of business objects, identify a specific relationship type and transition them to a new relationship type. For more information, see Transition Relationship Type.
Composee Inheriting Access from Composer
You can now change the environment variable MX_COMPOSEE_STRICT_ACCESS to allow or block composee to inherit access from composer. For more information, see Compositional Clause.

R2022x GA

Service Name in path Command
You can now store a reference to a service in the path command by adding the service name. The service name can be added in the add path or import path command if the name, and tenant are not created by a previous path command. You can also allow the addition of a service in the path command by specifiying it in the add pathtype command. For more information, see path Command and pathtype Command.
Precreate Trigger
You can now customize an event before instance object creation or any other configured triggers using the precreate trigger for business objects and relationships. For more information, see type Command and Trigger Clause.
End-of-life of FCS File Synchronization
In system settings, the FCS file synchronization mode fcssettings syncconcurrency is deprecated.
Extending the Data Model
Information has been added to the type command, attribute command, and policy command indicating that you should not use MQL for defining or modifying schema such as subtypes, extensions, policies, and attributes.
Studio Modeling Customization Guide
The Studio Modeling Customization Guide has been renamed the Legacy ENOVIA Web Apps Customization Guide and moved to the Developer Documentation portal. The MQL Command Reference now includes the Selectables, Macros, and MQL Parser Keywords appendices.