GIMAC - Cloning ISIM Objects
Cloning is the act of making an exact copy of the selected object. The GIMAC configuration file allows us to specify which attributes should not be copied. The following ISIM entities can be cloned: -
GIMAC - Cloning Persons
When cloning Person objects the user can change the Business Unit to which the entry belongs. Any field can then be amended before the new Person is saved.
GIMAC - Cloning Accounts
When cloning Account objects the user can change the Owner and or the Service (providing it is of the same type). So we can: -
- make a second account for the same owner on the same service (useful for testing or problem solving)
- make a new account for the same owner on a different service (useful for copying accounts between different environments e.g Production and Test)
- make a new account for a different Owner
- make a new account for a different Owner on a different service
GIMAC - Cloning Roles
Role memberships are not copied to the new Role. The Administrator can choose: -
- the Business Unit the new role should be created in
- whether to copy the Role hierarchy positions from the "master" Role
- whether to make the new Role a member of the same Provisioning Policies
- whether to amend the filter if this is a Dynamic Role
GIMAC - Cloning Provisioning Policies
When cloning Provisioning Policies the user can change the Business Unit to which the new policy should belong. Any field can then be amended before the new Provisioning Policy is saved.
GIMAC - Cloning Workflow
When cloning Account and Access Request Workflow the new workflow will not be attached to any requests. The workflow can be assigned to Accounts and Accesses after creation.