Description of the Menu Versions

From Metis Documentation

Revision as of 12:13, 11 December 2012 (view source) Patrick (Talk | contribs) (→Version without Administrator) ← Older edit		Revision as of 12:16, 11 December 2012 (view source) Patrick (Talk | contribs) (→Access) Newer edit →
Line 193:		Line 193:
	== Access ==		== Access ==
-	Description of the behaviour	+	From this sub-menu, the administrator can define and manage the access between the various children versions, as shown in the following example:
		+
		+
		+	[Screenshot of the access / Versions screen]
		+
		+
		+	The left hand part of the Versions window allows the administrator to search for a version by its designation; the full designation is not necessary. The administrator can enter some characters and the search function returns all the entries that contain the typed-in characters. The search results are listed under the '''Search''' button.
		+
		+	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 version is automatically selected in the Versions table.
		+
		+
		+	== Editing a Version's Rights ==
		+
		+
		+	Clicking on the '''Edit''' button opens the Version Rights window as shown in the following example:
		+
		+
		+	[Screenshot of the access / Version screen + Edit Headquarters]
		+
		+
		+	The title on the window displays the name of selected version (e.g. Version Rights Headquarters where Headquarters is the name of the selected version).
		+
		+	The Versions (Smart Quotes) table displays all the available versions. The displayed versions consist of all of the children versions of the administrator's version.
		+	The authorized column allows the administrator to select / deselect the versions that the Smart Quotes users is authorized to access to.
		+
		+	The following example describes the cases where a version can have access to the projects and offers made in other versions:
		+
		+
		+	[[File:MetisSmartModelingVersionsProfileDiagram.PNG]]
		+
		+
		+	An admnistrator of Version A can define that the Version A users can have access to the direct children versions' projects and offers (i.e. Version B, Version C and Version D). However, Version A users cannot access Version E's projects and offers because Version E is not a direct child of Version A.
		+
		+	The admnistrator of Version A can also define that Version B users can have access to Version C's projects and offers but not to Version D's projects and offer. The same administrator could also define that Version C users can only have access to Version B's projects and offers.
		+
		+	The authorization is not bi-directional: if Version B users have access to Version C's projects and offers, Version C users do not automatically receive access to Version B's projects and offers. The admninstrator must set the authorizations for each version.
		+
		+
		+	== Previewing a Version's Rights ==
		+
		+
		+	Clicking on the '''Preview''' button opens the Version Rights window as shown in the following example:
		+
		+	In this window, only the authorized versions are displayed. This means that if a version is not authorized to see the projects or the offers or at least one other version, the table is empty as shown in the following example:
		+
		+
		+	[Screenshot of the Profiles / Version screen + Preview Headquarters with no version selected]
		+
		+
		+	The properties are not editable.
	== Languages ==		== Languages ==

---

Revision as of 12:16, 11 December 2012