OU Management - Cronologia

Renato.daverio: /* Admin Kit - Support functions to manage OU */

2018-06-15T15:09:32Z

‎Admin Kit - Support functions to manage OU

Renato.daverio il 14:23, 15 giu 2018

2018-06-15T14:23:27Z

Renato.daverio: /* Upload OU on Client */

2018-06-15T14:20:08Z

‎Upload OU on Client

Renato.daverio il 14:19, 15 giu 2018

2018-06-15T14:19:07Z

Renato.daverio il 14:17, 15 giu 2018

2018-06-15T14:17:47Z

Renato.daverio: /* Ticket Management - Add Request by Resource */

2018-06-15T13:43:28Z

‎Ticket Management - Add Request by Resource

Renato.daverio: /* Ticket Management - Add Request by Resource */

2018-06-15T13:37:19Z

‎Ticket Management - Add Request by Resource

Renato.daverio: /* Ticket Management - Add Request by Requester */

2018-06-15T13:27:56Z

‎Ticket Management - Add Request by Requester

Renato.daverio: /* How to activate the Service Request visibility based on OU tree */

2018-06-15T13:27:18Z

‎How to activate the Service Request visibility based on OU tree

Renato.daverio: /* How to activate the Service Request visibility based on OU tree */

2018-06-15T13:24:41Z

‎How to activate the Service Request visibility based on OU tree

@@ Riga 17: / Riga 17: @@
 The relation between ''OU'' and ''Resource'' will be added (if found and if the relationship is not already present).
-To remove relations among Resources and Clients, follow these steps:
+To remove relations among ''Resources'' and ''Clients'', follow these steps:
 . Optionally select Clients on which to perform operation in Clients filter.
 . Click on the Delete Resources on Clients button to delete the relations on the selected Clients.
 . Click the Delete all Relationships button to delete the relations among all Clients and all Resources.
-To insert/update relations among  Resources and Clients, follow these steps:
+To insert/update relations among ''Resources'' and ''Clients'', follow these steps:
 . Optionally check the Add not found resource option if is required to add the not found Resources
 . Optionally check Add not found Organization Unit if is required to add Organization Units
@@ Riga 29: / Riga 29: @@
   for child OUs.
-OU import management rules:
+''OU'' import management rules:
-  A resource may belong to only one OU as Member: if it is related to another OU during xls import, it
+  A Resource may belong to only one OU as Member: if it is related to another OU during xls import, it
   relation with previous OU will be removed and a new relation will be created with the specified OU.
   When a resource is added to an OU, the Member flag is automatically activated.
-  A resource can be OU Manager of multiple OUs.
+  A Resource can be OU Manager of multiple OUs.
-  A resource can be both a Member and an OU Manager of an OU.
+  A Resource can be both a Member and an OU Manager of an OU.
 Expected xls format:
@@ Riga 56: / Riga 56: @@
-The button Report allows to view the current situation of relations among Resources and Clients.
+The button '''Report''' allows to view the current situation of relations among ''Resources'' and ''Clients''.
-The button Update User Info in all the Tickets allows to update all the data in the User Info Tab of the Tickets as filtered in Customers \ OUs and addresses.
+The button '''Update User Info in all the Tickets''' allows to update all the data in the User Info Tab of the Tickets as filtered in Customers \ OUs and addresses.
 This operation is high impacting on performance and on data structure: is strongly suggested to create a backup of the DB before proceeding and to run it at low system load time.
@@ Riga 64: / Riga 64: @@
 This feature is based on the upload of an xls file formatted as shown below.
-The page allows to import one or more Organization Unit per Client with a specific Parent - Child structure.
+The page allows to import one or more ''Organization Unit'' per ''Client'' with a specific Parent - Child structure.
-To insert/update OUs on Clients, follow these steps:
+To insert/update ''OUs'' on ''Clients'', follow these steps:
 . Select the xls file
 . Click on button Submit
-The Clients and the Organization Units are identified by Name, not by ID (the columns Id and Parent id are used only for identification of the Father - Child structure).
+The ''Clients'' and the ''Organization Units'' are identified by Name, not by ID (the columns Id and Parent id are used only for identification of the Father - Child structure).
 Expected xls format:
@@ Riga 117: / Riga 117: @@
   Organizational Unit updated
-The button "Update all the Tickets - User Info" allows you to update all the data in the User Info Tab of the Tickets as per current settings relative to Customers \ OUs and addresses.
+The button '''Update all the Tickets - User Info''' allows you to update all the data in the User Info Tab of the ''Tickets'' as per current settings relative to ''Customers'' \ ''OUs'' and ''Addresses''.
 This operation is high impacting on performance and on data structure: is strongly suggested to create a backup of the DB before proceeding and to run it at low system load time.

@@ Riga 13: / Riga 13: @@
 This feature is based on the upload of an xls file formatted as shown below.
-The Client with name corresponding to <u>CLIENT DIVISION</u> + " " + <u>CLIENT REGION</u> will be added the Organizational Units present in columns OU_1, OU_2 ... OU_9, respecting the hierarchy present in the xls file (if the Customer or the Organizational Unit are not present an error message will be visualized).
+The ''Client'' with '''Name''' corresponding to <u>CLIENT DIVISION</u> + " " + <u>CLIENT REGION</u> will be added the ''Organizational Units'' present in columns '''OU_1, OU_2 ... OU_9''', respecting the hierarchy present in the xls file (if the ''Client'' or the ''Organizational Unit'' are not present an error message will be visualized).
-The relation between OU and resource will be added to the Organizational Unit (if this is found and if the relationship is not already present).
+The relation between ''OU'' and ''Resource'' will be added (if found and if the relationship is not already present).
 To remove relations among Resources and Clients, follow these steps:

@@ Riga 13: / Riga 13: @@
 This feature is based on the upload of an xls file formatted as shown below.
-The Client with name corresponding to CLIENT DIVISION + " " + CLIENT REGION will be added the Organizational Units present in columns OU_1, OU_2 ... OU_9, respecting the hierarchy present in the xls file (if the Customer or the Organizational Unit are not present an error message will be visualized).
+The Client with name corresponding to <u>CLIENT DIVISION</u> + " " + <u>CLIENT REGION</u> will be added the Organizational Units present in columns OU_1, OU_2 ... OU_9, respecting the hierarchy present in the xls file (if the Customer or the Organizational Unit are not present an error message will be visualized).
 The relation between OU and resource will be added to the Organizational Unit (if this is found and if the relationship is not already present).

@@ Riga 5: / Riga 5: @@
 = Admin Kit - Support functions to manage OU =
-In General\System\Admin Kit are available some support functions.
+In '''''General\System\Admin Kit''''' are available some support functions.
-Two of them are related to Organization Unit:
+Two of them are related to ''Organization Unit'':
-  Upload Relations Resources-Clients
+  '''Upload Relations Resources-Clients'''
-  Upload Organization Unit on Client
+  '''Upload Organization Unit on Client'''
 == Upload OU on Client ==

@@ Riga 1: / Riga 1: @@
 = Client - Organization Unit =
-The Tab Organization Unit under Clients Management\Clients\Clients allows to manage the Organization Unit (OU) tree related to each Clients.
+The Tab <u>''Organization Unit''</u> under '''''Clients Management\Clients\Clients''''' allows to manage the ''Organization Unit'' (OU) tree related to each ''Clients''.
 For a detailed description check here: [[Client Management]]

@@ Riga 182: / Riga 182: @@
 The purpose of this functionality is to create Ticket following a 3 steps mini-wizard oriented to Requested.
-  Step 1:
+  Step 1: This step allows to select the Ticket Requester.
-  Step 2:
+  Step 2: This step allows the selection of Service Request from Service Catalog, the Ticket will be
-  Step 3:
+  Step 3: This step allows to complete the Ticket before its creation.
 More details about the configuration of this functionality can be found here: [[TBC]]

@@ Riga 180: / Riga 180: @@
 = Ticket Management - Add Request by Resource =
-TBD
+The purpose of this functionality is to create Ticket following a 3 steps mini-wizard oriented to Requested.
-== How to activate ==
+ Step 1:
-== How to configure Resource to add Ticket in this way ==
+ Step 2:
-TBD

@@ Riga 179: / Riga 179: @@
 The SRCS - Service Request visibility by Organization Unit can be configured by xls import, more details can be found here: [[Service Catalog Management (SRCS)]]
-= Ticket Management - Add Request by Requester =
+= Ticket Management - Add Request by Resource =
 TBD

← Versione meno recente		Versione delle 13:27, 15 giu 2018
Riga 176:		Riga 176:

	System will help with the proposal of Organization Units childs auto-selection.		System will help with the proposal of Organization Units childs auto-selection.
		+
		+	The SRCS - Service Request visibility by Organization Unit can be configured by xls import, more details can be found here: [[Service Catalog Management (SRCS)]]

	= Ticket Management - Add Request by Requester =		= Ticket Management - Add Request by Requester =

← Versione meno recente		Versione delle 13:24, 15 giu 2018
Riga 170:		Riga 170:

	== How to activate the Service Request visibility based on OU tree ==		== How to activate the Service Request visibility based on OU tree ==
		+
		+	In General\Ticket\SRCS shall be possible to define the visibility for each Service Request depending by Organization Unit of Resource.
		+
		+	In Service Request - Tab Organization Unit is possible to click on button lookup and select in popup the Organization Unit enabled to see current Service Request.
		+
		+	System will help with the proposal of Organization Units childs auto-selection.

	= Ticket Management - Add Request by Requester =		= Ticket Management - Add Request by Requester =