MEGA Administration : Administrator Guide : Command File Syntax : Object Naming Rules
   
Object Naming Rules
Object naming will depend on the uniqueness rule applied to its name. This rule is important, since the name appears in command files.
An object has a unique name
An object must have a unique name throughout the repository.
For example, a report template (MS Word) has a name that appears in command files.
A name is unique in a given context
Several objects can have the same name, but the name must be unique in a particular context: therefore it has a namespace.
For example, an operation of an organizational process: its name must be unambiguous within the process, but several different process operations can carry the same name.
For these objects, two names are presented to the user in the user interface:
Concept
Example
Comment
Name
Hire::Call candidate
Complete object name. Unique in the repository. Calculated from the local name and the namespace name (which can itself have a namespace). Here the operation "Call candidate" belongs to the "Hire" process.
Local name
Call candidate
Name of the object in its namespace. Unique in the namespace.
Two names are used in MEGA command language:
Concept
MetaAttribute
Example of value
Internal name of the object. It contains
HexaIdabs of the object.
Name
14B8162B3F3A0347
Local name of the object and HexaIdabs of its namespace.
Generic Local Name
Call candidate [85ED06B63EC95B6F]
These build rules ensure respect of naming rules imposed by the repository:
• The name must be unique: the IdAbs is built to be so.
• The local name must be unique in its context: specify a uniqueness constraint on the GenericLocalName.
*If the object is detached from its namespace, in the local name the indicated HexaIdAbs is then a string of 16 "0".
Objects without name constraint
There is no name uniqueness constraint on certain objects such as messages: the same operation can send or receive several messages with the same name.
In this case, the object constitutes its own namespace.
Two names are used in MEGA command language:
Concept
MetaAttribute
Example of value
Internal "Name" of the object. It contains
HexaIdabs of the object.
Name
14B8162B3F3A0347
Local name of the object and HexaIdabs of its namespace (itself).
Message Local Name
Convocation [14B8162B3F3A0347]