Differenze tra le versioni di "OU Management"
(→Admin Kit - Support functions to manage OU) |
(→Upload OU on Client) |
||
Riga 35: | Riga 35: | ||
Expected xls format: | Expected xls format: | ||
− | + | {| class="wikitable" | |
+ | ! Field !! Meaning !! Comments | ||
+ | |- | ||
+ | |<u>CLIENT DIVISION *</u>||First part of the customer's name|| | ||
+ | |- | ||
+ | |<u>CLIENT REGION</u>||Second part of the customer's name|| | ||
+ | |- | ||
+ | |<u>OU_1*</u>||First Level Organizational Unit: at least one Organizational Unit must be present because the Resource can't be associated directly with the Client|| | ||
+ | |- | ||
+ | |<u>OU_[2…10]</u>|||| | ||
+ | |- | ||
+ | |<u>RESOURCE NAME*</u>||MB simulates the defined Publisher|| | ||
+ | |- | ||
+ | |<u>RESOURCE SURNAME*</u>||Message processing priority|| | ||
+ | |- | ||
+ | |<u>Manager (yes|no)*</u>||This is a Filter for field Message Type|| | ||
+ | |} | ||
+ | |||
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. |
Versione delle 10:11, 9 mag 2018
Indice
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:
1. Optionally select Clients on which to perform operation in Clients filter. 2. Click on the Delete Resources on Clients button to delete the relations on the selected Clients. 3. 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:
1. Optionally check the Add not found resource option if is required to add the not found Resources 2. Optionally check Add not found Organization Unit if is required to add Organization Units (if this option is not checked the OU will not be added, but only updated if found) 3. Optionally check Associate OU Manager for child 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:
Field | Meaning | Comments |
---|---|---|
CLIENT DIVISION * | First part of the customer's name | |
CLIENT REGION | Second part of the customer's name | |
OU_1* | First Level Organizational Unit: at least one Organizational Unit must be present because the Resource can't be associated directly with the Client | |
OU_[2…10] | ||
RESOURCE NAME* | MB simulates the defined Publisher | |
RESOURCE SURNAME* | Message processing priority | |
no)* | This is a Filter for field Message Type |
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
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