Managing User Options
For specific requirements, you can modify default values of certain
Options (see
Accessing Options).
Configuring the Metamodel Access
With the Metamodel Access option (Options > Repository field), 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.
• 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).
Prohibiting the Administrator from Modifying User Options
By default the HOPEX (Web Front-End) administrator can modify the options at 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 prohibit the administrator from modifying options at user level.
Authorizing Deletion of a Dispatched 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 option (Options > Repository folder) 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.
Making a Comment Mandatory on Dispatch
With the Comment on dispatch option (Options > Repository folder) users must enter information in the Dispatch comment (report) pane when they dispatch their work.
Managing User Inactivity
You can specify for how long user session time can remain inactive before closing.

This option can be useful for example for security requirements, or to ensure that all sessions are closed before starting a batch program.
By default, user inactivity management is not activated.
Activating/Deactivating user inactivity management
To activate/deactivate user inactivity management:
1. Access Options at the environment level.
2. In the Options tree, select Workspace.
3. In the right pane:
• to activate user inactivity management, select Automatic Session Timeout.
• to deactivate user inactivity management, clear Automatic Session Timeout.
Managing user inactivity
Prerequisite: user inactivity management is taken into account if the Inactivity Management option is selected.

The
Period of inactivity requiring authentication is
HOPEX (Windows Front-End) specific.
To manage user inactivity:
1. Access Options at the environment level.
2. In the Options tree, select Workspace.
3. In the right pane, enter a value for the Duration of inactivity before closing HOPEX option.

If the
Period of inactivity requiring authentication option is lower than the
Duration of inactivity before closing HOPEX value, thus the value taken into account for user disconnection is this latter.
When this duration has been reached, the user is disconnected and HOPEX closes without warning.