Differenze tra le versioni di "OU Management"

Da itm wiki.
Riga 3: Riga 3:
  
 
= Admin Kit - Support functions to manage OU =
 
= Admin Kit - Support functions to manage OU =
 +
In General\System\Admin Kit are available some support functions.
 +
Two of them are related to Organization Unit:
 +
* Upload Relations Resources-Clients
 +
* Upload Organization Unit on Client
  
 
== Upload OU on Client ==
 
== Upload OU on Client ==
 +
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 relation between OU and resource will be added to the Organizational Unit (if this is found and if the relationship is not already present).
 +
 +
To remove relations among Resources and Clients, follow these steps:
 +
* Select the Company on which to perform the bulk operation from the Company Id pop-up menu.
 +
* Optionally select Customers.
 +
* Click on the Delete Customer Resources button to delete the relations only on the selected Customers.
 +
* Click the Delete all Relationships button to delete the relations among all Customers and all Resources.
 +
 +
To update relations among  Resources and Clients, follow these steps:
 +
* Select the Company on which to perform the bulk operation from the Company Id pop-up menu.
 +
* Optionally check the Add Resources option not found if is required to add the not found Resources
 +
* Optionally check Add Organizational Unit not found if is required to add Organizational Units (if this option is not checked the OU will not be added, but only updated if found)
 +
* Optionally check the OU Manager role assignment option to the Child Organizational Units if is required to set to OU Managers also for child OUs.
 +
 +
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 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 both a Member and an OU Manager of an OU.
 +
 +
Expected xls format:
 +
TBD
 +
 +
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.
 +
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.
  
 
== Upload Resource on OU ==
 
== Upload Resource on OU ==

Versione delle 09:32, 9 mag 2018

Client - Organization Unit

The Tab Organization Unit under Clients Management\Clients\Clients allows to manage the Organization Unit (OU) tree related to each Clients.

Admin Kit - Support functions to manage OU

In General\System\Admin Kit are available some support functions. Two of them are related to Organization Unit:

  • Upload Relations Resources-Clients
  • Upload Organization Unit on Client

Upload OU on Client

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 relation between OU and resource will be added to the Organizational Unit (if this is found and if the relationship is not already present).

To remove relations among Resources and Clients, follow these steps:

  • Select the Company on which to perform the bulk operation from the Company Id pop-up menu.
  • Optionally select Customers.
  • Click on the Delete Customer Resources button to delete the relations only on the selected Customers.
  • Click the Delete all Relationships button to delete the relations among all Customers and all Resources.

To update relations among Resources and Clients, follow these steps:

  • Select the Company on which to perform the bulk operation from the Company Id pop-up menu.
  • Optionally check the Add Resources option not found if is required to add the not found Resources
  • Optionally check Add Organizational Unit not found if is required to add Organizational Units (if this option is not checked the OU will not be added, but only updated if found)
  • Optionally check the OU Manager role assignment option to the Child Organizational Units if is required to set to OU Managers also for child OUs.

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 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 both a Member and an OU Manager of an OU.

Expected xls format: TBD

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. 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.

Upload Resource on OU

Company Info

Custom fields in OU

Other Options

Ticket Management - Fields related to Client and OU

Custom field with type "Resource"

How to activate the Service Requester visibility based on OU tree

Ticket Management - Add Request by Requester

TBD

How to activate

TBD

How to configure Resource to add Ticket in this way

TBD