Warning: preg_match(): Compilation failed: group name must start with a non-digit at offset 8 in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 722

Warning: preg_match(): Compilation failed: group name must start with a non-digit at offset 8 in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 722

Warning: preg_match_all(): Compilation failed: group name must start with a non-digit at offset 4 in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 700

Warning: Invalid argument supplied for foreach() in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 701

Warning: preg_replace(): Compilation failed: group name must start with a non-digit at offset 4 in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 705

Warning: preg_match_all(): Compilation failed: group name must start with a non-digit at offset 4 in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 700

Warning: Invalid argument supplied for foreach() in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 701

Warning: preg_replace(): Compilation failed: group name must start with a non-digit at offset 4 in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 705

Warning: preg_match_all(): Compilation failed: group name must start with a non-digit at offset 4 in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 700

Warning: Invalid argument supplied for foreach() in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 701

Warning: preg_replace(): Compilation failed: group name must start with a non-digit at offset 4 in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 705

Warning: preg_match_all(): Compilation failed: group name must start with a non-digit at offset 4 in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 700

Warning: Invalid argument supplied for foreach() in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 701

Warning: preg_replace(): Compilation failed: group name must start with a non-digit at offset 4 in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 705

Warning: preg_match(): Compilation failed: group name must start with a non-digit at offset 8 in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 722

Warning: preg_match(): Compilation failed: group name must start with a non-digit at offset 8 in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 722

Warning: preg_match(): Compilation failed: group name must start with a non-digit at offset 8 in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 722

Warning: preg_match(): Compilation failed: group name must start with a non-digit at offset 8 in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 722

Warning: preg_match(): Compilation failed: group name must start with a non-digit at offset 8 in /home/clients/fc00b35069112567fd28baa9a60aff76/web/mediawikidev/includes/MagicWord.php on line 722
Description of the Sub-Menu Functionalities - Metis Documentation

Description of the Sub-Menu Functionalities

From Metis Documentation

Jump to: navigation, search
(Creation of the page)
(Contents added)
Line 1: Line 1:
-
Description of the different functionalities and their impact on the other windows/menus of Metis.
+
In this menu, the administrator can define and manage the Metis user default settings and the functionalities that the Metis user has the right to use, as shown in the following example:
 +
 
 +
[Screenshot of the Profiles / Functionalities screen]
 +
 
 +
Functionality profiles can be defined for each product of the Metis Smart suite:
 +
* Smart Modeling
 +
* Smart Monitoring
 +
* Smart Quotes
 +
 
 +
These products are listed in the '''Application''' drop-down menu. The administrator must first select an application from the drop-down menu to see the functionality profiles that exist for the selected application.
 +
 
 +
The left hand part of the screen allows the administrator to search for a functionality profile by its designation. The full designation is not necessary. The administrator can enter some characters and the search function returns all the entries that contains the typed-in characters. The search results are listed under the '''Search''' button, as shown in the following example:
 +
 
 +
[Screenshot of the Profiles / Functionalities screen + screenshot with some search results (ex. letter q) & button greyed]
 +
 
 +
After a search, the '''Search''' button is greyed out until the search criterion is modified.
 +
 
 +
If the administrator selects an entry in the search result, the profile is automatically selected in the '''Profiles''' table.
 +
 
 +
The '''Profiles''' table consist of two columns:
 +
* the first column may contain a padlock icon. If a padlock icon appears, this means that the profile cannot be deleted and its properties cannot be edited. Only an administrator of the parent version can edit the properties of this profile or delete that profile.
 +
 
 +
* the second column contains the designation of the profile.
 +
 
 +
The contents of the '''Profiles''' table can be sorted by alphabetic order. The administrator can search for a profile directly in the profile name column. To do so, the administrator must click on the magnifying glass icon then type in the name of the profile.
 +
 
 +
The functionality profiles defined in this menu are then made available in the following parts of Metis:
 +
 
 +
[Screenshot of Users / Add + focus on Functionality Profiles field which will be added by MAR] + Remember that an example must be provided for the 3 types of applications
 +
 
 +
'''Note:''' It is not possible to create a profile from scratch. Profiles can only be duplicated from existing ones and then edited accordingly.
 +
 
 +
=== Deleting a Functionality Profile ===
 +
 
 +
The administrator can delete a profile by selecting it first, then clicking on the ''Delete'' button. A confirmation window appears as shown in the following example:
 +
 
 +
[Screenshot of the confirmation pop-up window]
 +
 
 +
If the profile has been attributed to one or more users, the confirmation window indicates the number of users to which the profile has been attributed to, as shown in the following example:
 +
 
 +
[Screenshot of the confirmation pop-up window]
 +
 
 +
To delete the profile, click on the ''Yes'' button.
 +
 
 +
Remember that profiles with a padlock icon cannot be deleted. If the administrator tries to do so, the following message appears:
 +
 
 +
[Screenshot of the warning pop-up window]
 +
 
 +
'''Note:''' The administrator cannot select several profiles at the same time.
 +
 
 +
=== Creating a Duplicate Functionality Profile ===
 +
 
 +
To create a new profile, the administrator must create a duplicate of an existing profile then edit it accordingly.
 +
 
 +
To do so, the administrator must select a profile then click on the '''Duplicate''' button. The profile features window appears as shown in the following example:
 +
 
 +
[Screenshot of the Feature Profile window]
 +
 
 +
By default, the profile name field displays the name of the profile which has been selected. The administrator must provide another name for the profile.
 +
 
 +
It is not possible to enter a profile name that already exists. If the administrator tries to do so, the following message appears when saving the new profile:
 +
 
 +
[Screenshot of the info pop-up window]
 +
 
 +
The administrator can then edit the properties of the new profile (see [[#Editing a Functionality Profile|below]]).
 +
 
 +
=== Editing a Functionality Profile ===
 +
 
 +
Selecting a profile and clicking on the ''Edit'' button displays the properties of the profile, as shown in the following example:
 +
 
 +
[Screenshot of the feature profile]
 +
 
 +
If the administrator does not have the right to edit the properties of a profile, he/she receives the following message when trying to do so:
 +
 
 +
[Screenshot of the no permission pop up window]
 +
 
 +
The properties of a profile are grouped within the following tabs:
 +
* Rights: the Metis user default settings and the functionalities that the Metis user has the right to use
 +
* Languages: the language(s) that the Metis user is authorized to use
 +
* SQL connection: the databases to which the Metis user can connect to and toward which databases data can be transferred
 +
 
 +
Each tab is described below.
 +
 
 +
==== Rights tab ====
 +
 
 +
IN PGROGRESS
 +
 
 +
==== Languages tab ====
 +
 
 +
The '''Languages''' tab shows the languages that were made available for the version in the [[Description of the Menu Languages|Language menu]], as shown in the following example:
 +
 
 +
[Screenshot of the Languages tab]
 +
 
 +
By default, a language made available for the version is automatically selected in the '''Languages''' tab (i.e. the Authorized checkbox is ticked). If the administrator wants to customize the language that the Metis user is authorized to use, he/she can untick the checkbox in the '''Authorized''' column for the languages that the end user cannot use.
 +
 
 +
If no language is selected, the end user's default language is English.
 +
 
 +
The languages defined as authorized in this menu are then made available in the end user's Setup menu, as shown in the following example:
 +
 
 +
[Screenshot of the Setup + focus on the Language field]
 +
 
 +
*** to check when the Setup menu will be available ***
 +
 
 +
==== SQL connection tab ====
 +
 
 +
The SQL connection tab contains two tables ('''SQL Connections''' and '''Transfer to'''), as shown in the following example:
 +
 
 +
[Screenshot of the SQL Connection tab]
 +
 
 +
Both tables are populated with the SQL connections that were previously defined in the [[Description of the Sub-Menu SQL Connections|SQL Connections submenu]] in [[Description of the Menu Data Management|Data Management]].
 +
 
 +
*** to check later on and see if the link to the SQL connections page is necessary / relevant ***
 +
 
 +
The default SQL connection corresponds to the server name and database name that were defined the very first time that Metis was launched (see [[Metis Smart Modeling User Manual Home Page#Log In|Log In]]) or in the setup.ini file.
 +
 
 +
The SQL connections table allows the administrator to give the right to the Metis user to connect to other databases. To give access to a database, the administrator must tick the box in the '''Authorized''' column for the SQL connections of his/her choice. All the checkboxes can be ticked / unticked except the '''DEFAULT''' SQL Connection checkbox.
 +
 
 +
The authorized connections are then proposed to the Metis user once he/she logs in, as shown in the following example:
 +
 
 +
[Screenshot of the Database selection after login in Metis PM + Metis BW]
 +
 
 +
The '''Transfer to''' table allows the administrator to set the data transfer authorizations between the various SQL connections. This means that the administrator can define, for each SQL connection, towards which database(s) the data can be transferred.
 +
 
 +
The administrator must first select a connection (i.e. a database) in the '''SQL Connections''' table. The selected database is greyed in the '''Transfer to''' table.
 +
 
 +
Then, in the '''Transfer to''' table, the administrator can tick the box in the '''Authorized''' column for the SQL connections towards which it is possible to transfer data.
 +
 
 +
This mapping is then used for the data transfer process. Upon selection of a source database, the proposed destination databases are those defined in the '''SQL connection''' tab, as shown in the following example:
 +
 
 +
[Screenshot of a mapping + screenshot of the Data Transfer menu with the source and destination database accordingly]
 +
 
 +
*** check that data transfer is a functionality for Metis PM users only (if so, the Transfer to table must be shown when selecting Metis Modeling as application). check where the data transfer menu will be in Metis ***
 +
 
 +
=== Previewing a Functionality Profile ===
 +
 
 +
Selecting a profile and clicking on the ''Preview'' button displays the properties of the profile, as shown in the following example:
 +
 
 +
[Screenshot of the Feature Profile window]
 +
 
 +
The properties of a profile consist of:
 +
* the rights: the Metis user default settings and the functionalities that the Metis user has the right to use
 +
* the languages: the language(s) that the Metis user is authorized to use
 +
* the SQL connection: the databases to which the Metis user can connect to and toward which databases data can be transferred
 +
 
 +
The properties are not editable.
 +
 
 +
*** General note for myself! The descriptions are based on the Smart Quotes application. Check what adaptations are necessary for the Smart Modeling and Smart Monitoring applications (esp. the Rights, SQL connection) ***

Revision as of 13:50, 29 March 2011

Personal tools