Commands
Commands on objects
• .Create (creation of an object)
• .Update (modification of an object MetaAttribute)
• .Delete (deletion of an object)
Commands on links
• .Connect (creation of a link between two objects)
• .Disconnect (deletion of a link between two objects)
• .Change (modification of a link MetaAttribute)
Other Commands
• .Validate (triggers intermediate save on import)
• .Description (produces display in import dialog box)
Rules to be respected
Command files must comply with the following rules:
• A command line cannot contain more than 5000 characters.
• Object names are limited to:
• 63 characters for object types without namespace.
• 255 characters for object types with namespace (name or local name).
• Commands begin with a verb infinitive prefixed by ".".
• The "." of the command must be in the first column.
• Use a hyphen (-) at the end of a line to indicate that it continues on the next line.
• Comment lines are indicated by a hyphen (-) at the beginning of the line.
• Use double-quotes (") around values that contain spaces or characters other than letters or digits.
Remarks
• Certain objects are functionally invalid if one of their MetaAttributes is not entered or a link is not defined. For example, a diagram type object must be connected to another object by a descriptor type link. We say that the diagram describes this object.
• To exchange data between two HOPEX environments, they must have identical metamodels and coherent user diagrams.
Commands as function of file type
Each command must consist of:
• a verb indicating the action to be carried out
• a list of parameters required to carry out this action (object types and names)
• a keyword ".CHK" followed by a list of the IdAbs of objects impacted by this command.
The fact of repeating the object name and IdAbs in the command enables its correct execution, even if the object has been renamed.The difference between the command of an ".MGR" file and the same command of an ".MGL" file is in the ".CHK":
• they have the same verb
• they have the same list of parameters
• the ".CHK" of MGL contains in addition in last position, the IdAbs of the user that issued the order.
A third file format (obsolete in this version) is ".MGE". In these files commands do not have a .CHK. The IdAbs are assigned as required. It is therefore not possible to process "namespaced" objects for which the namespace IdAbs cannot be assigned, since it forms part of their name. References to the metamodel
Each metamodel instance (MetaClass, MetaAttribute, …) can be prefixed by its IdAbs. This assures permanence of files despite renamings which may be carried out in the metamodel.
Example:
"~OsUiS9B5iiQ0[Operation]" is equivalent to "Operation".