Configuring Metamodel Access
With the Metamodel Access option (Options > Repository menu) , you can restrict the view of HOPEX objects or functions according to user skill level.
This option can be defined at environment, profile or user level according to the requirement.
Metamodel access levels are:
Beginner
For introduction to HOPEX. Only basic objects are visible. This level allows very simple modeling.
Intermediate (default value)
For standard use of HOPEX. Almost all object types, links and non-technical attributes are visible.
Advanced
For advanced use of HOPEX. All objects, links and non-technical attributes are visible, including those that require advanced skills for their use. Only object types and attributes which are present only for compatibility with previous versions are filtered. Certain technical object types are visible. The user can carry out simple customizations of the HOPEX platform.
For example, this level enables access to:
certain navigation windows, with a restricted view of objects (MetaStudio, Utilities)
the Administration navigation window, which gives access to reading and writing access areas.
the Repository Activity (Navigation window in HOPEX, see "Viewing the Repository Update Log", page 99).
Expert
This level displays all object types, links, and attributes, as well as the abstract metamodel. All HOPEX platform customizations are available.
*Specify this access level only for a highly expert user or a particular profile (e.g.: HOPEX Customizer).
This is the level for example that offers:
all functions of HOPEX Power Studio (MetaStudio navigation window)
report template creation (Utilities navigation window)
certain advanced commands (e.g.: update logfile export at particular intervals).
Preventing the administrator from modifying user options
By default the HOPEX administrator can modify the options at site, environment, profile, and user level. The option levels are governed by an inheritance mechanism (Site > Environment > Profile > user).
The Enables modification of user option by the administrator option (Options > Installation > User Management folder) enables to prevent the administrator to modify options at user level.
*Authorizing Deletion of a Published Object
Users working in a public workspace can delete objects.
By default, users working in a private workspace are not authorized to delete dispatched objects, even if these have been created by the user wishing to delete.
The Authorize dispatched object deletion from private workspace allows the user to delete dispatched objects from a private workspace, irrespective of the creator.
This authorization complements object deletion rights defined elsewhere for the profile or user.
Authorizing HOPEX Data Modification
*This option should only be selected in certain highly specific cases, at debugging operations or at MEGA request, and for a temporary period.
This option authorizes modification of the HOPEX metamodel or any other HOPEX technical object. Modifying a HOPEX object can generate errors at HOPEX upgrades, import of correctives, etc.
*Specify this access level only for a highly expert user or highly advanced profile.