Manage organizational data
Manage organizational data
In this use case is described how organizational data and other needed data, like titles and cost centers are managed in IGA solution.
Organizational data is needed for example in IGA Automated Rule use case and it means that organization units, cost centers and titles are read from the source system to their own datacards. This information can be used for categorizations, lists, rules etc. and it is automatically updated when there are for example organizational changes.
Notice, that user related organization, title and cost center information are received via IGA Identity Storage and User Lifecycle Management use cases.
Use Case Description
|
Description |
Overview |
|
Operators |
IGA solution |
Prerequisites |
If Customer is managing organizational, title and cost center related data manually, it is good to knowledge that for example IGA Automated Rules are not recommended to be used. |
Result |
|
Operating chain for Automation |
|
| Operating chain for Manual Management |
If organizational units, cost centers or titles are managed manually, it is not recommended to relate IGA Automated Rules to this information.
1. IGA Admin can manage organizational units, titles and cost centers manually by choosing the datacard view
|
| Data content for Organizational Units |
Mandatory: Name, organization ID (unique), active / inactive Highly recommended: Description, start date, end date Recommended: Parent organization ID, timestamp for last update in source system Possibilities: Head of organization, street address, postal code, country |
| Data content for titles |
Mandatory: Name, title ID (unique), active / inactive Highly recommended: Description, start date, end date Recommended: Timestamp for last update in source system |
| Data content for cost centers |
Mandatory: Name, cost center number, active / inactive Highly recommended: Description, start date, end date Recommended: Timestamp for last update in source system |
| Auditing Details |
Auditing details are saved, but since these changes don't have affect to users access rights, IGA Access Right Records are not needed, but history can be reported by IGA Admins (choosing also hidden datacards). If changes are made manually, also modifier and date stamps are available either on the active or inactive datacards. |
Related datacards |
Organization Unit |
Delete
Configuration changes
In this use case Customer can make following changes, without them having affects to the project schedule or work estimations:
1. Organisation, title and cost center datacards can be used for importing other needed information, as long as same pre-defined data content is used and there is none changes to the workflows or templates.
2. Customer can choose names for organization, cost center and title templates (as long as the template code is not changed)
Expansion possibilities
1. Add new data content
Customer can add new data content (attributes), but it will need Efecte Consultants review, before affects to the project schedule or to work estimations can be done.
2. Import other needed information
Which is needed to be automatically managed as organizational, title and cost center data. This will need Efecte Consultants review, before affects to the project schedule and work estimations can be done.
3. Create directory groups based on received information
Based on organization, cost center or titles IGA Entitlements can be created and provisioned to the Customers directory. This will need IGA Enterprise package.
DeleteRelations & configuration instructions
Relations to other use cases,
Relations to other data cards,
Organization Unit
Cost Center
Title
Configuration instructions,
With IGA baseline there is no need to edit workflows or EPEtasks to achieve this use case. Imports are done usually with integration.
Delete