Manage data imports
Manage data imports
In this use case are described one time data imports, which are used for importing
1. IGA Entitlements from different applications
Customer can export group information from the application and import that to IGA Entitlements. After import, information can be used as same as IGA Entitlements which provisioning type is automatic. Usually this is done when new application is starting to use IGA solutions centralized services, processes and workflows for requesting and managing applications access rights.
2. IGA Business Roles
If Customer has list of pre-defined roles (or can export one from some other application), which are needed in IGA solution. Usually this import is done once, when IGA solution is technically taken into use.
3. Application list
If Customer has list of all applications used in the Customers organization, it can be imported to IGA solution for further usage. Usually this is done once and after that applications are managed in Efecte solution.
4. IGA Access Right Records
This means that group membership information is exported from the source application and imported as a base information to IGA solution. This use case will provide audit information about who has currently active access rights to the application.
5. Proof Of Concept
IGA Import Task can be also used in IGA Proof of Concept (PoC) projects. This is used for simulating HR-integration and user imports. Most commonly PoC's does not included actual HR-integration, but still it is important to test how future HR-integration would work.
Use Case Description
This use case contains all functionalities for all Efecte IGA Packages, different package content has been marked
* Add-on to IGA Starter package
** IGA Growth package
*** Only available for IGA Enterprise package
|
Description |
Overview |
This use case also describes situation when HR-integration needs to be simulated during the PoC project. |
Operators |
IGA solution |
Prerequisites |
|
Result |
IGA Entitlement, IGA Business Role, Applications, IGA Access Right Records are imported to datacards. In PoC projects, use cases related to user lifecycle management are simulated according to the future HR-integration. |
Operating chain for IGA Entitlement |
|
| Data content for Entitlement |
Mandatory: Technical name, friendly name Highly recommended: Description, provisioning type, application Recommended: Owner, approval level (approvers) |
| Data content for Business Roles |
Mandatory: Name Highly recommended: Description, IGA Entitlement ID's (role content) Recommended: Owner, approval level, sub-role ID's (role content) |
| Data content for Applications |
Mandatory: Name Highly recommended: Description, friendly name, IGA Entitlement ID's Recommended: Owner, sub-role ID's |
| Data content for Group Memberships |
Mandatory: Name, cost center number, active / inactive Highly recommended: Description, start date, end date Recommended: Timestamp for last update in source system |
| Data content for PoC |
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 entitlements, business roles or application imports 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). While importing users (available only during PoC project) or group memberships, IGA Access Right Records are created (source type import by Admin) |
Related datacards |
IGA Import Task |
Configuration changes
In this use case Customer can make following changes, without them having affect to the project schedule or work estimations.
1. Data content, attributes
Customer can define importable data content, except the mandatory information. Data content can be any attribute from the template, but new attributes might have affect to the project schedule and work estimation.
2. Data content, values
Customer can define different attribute or attribute value names.
Expansion possibilities
1. Add new data content
If ready-made attributes are not enough it is possible to have Customer specific configuration to the data content, but this will always need Efecte consultants review before affects to the project schedule and work estimations.
2. Add new import types
Customer can use same IGA import Task for importing other needed information to IGA solution, but this will always need Efecte Consultants review before affects to the project schedule and work estimations.
DeleteRelations & configuration instructions
Relations to other use cases,
Relations to other data cards,
IGA Import Task
IGA Entitlement
IGA Business Role
Application
IGA Access Right Record
Configuration instructions,
IGA importask configuration instruction here
Delete