Assignment State
Introduction
Each assignment in the CoreOne Suite - Role, Resource, Asset or any other - can have multiple states.
States
The following states are implemented.
Property | Description |
---|---|
| The assignment was just created and has not yet been processed by the system. |
| The assignment was processed and it was determinated that an approval is needed. |
| The assignment is ready to be provisioned in the target system, but it has not yet been done so. This can have multiple reasons, the system has not yet processed it, the appropriate features are not turned and so on. |
| The assignment was successfully assigned. |
| The assignment was deleted and is no longer assigned. |
| An approval was necessary and the outcome of the approval process was a denial. |
| The assignment is assigned but a removal is pending. |
| There was a rule configured that denies the assignment. This means, the core identity will not receive the assignment even if there is another assignment for the same object. |
| An assignment would be technically possible but is not configured in the configuration. |
| A misconfiguration was detected, the configured assignment ist not supported. |
| The assignment itself is not yet valid (valid from), but the enlistment mode was applied and the assignment is assigned. |
| If the validity was moved to the future, this state is set to indicate that the assignment is currently assigned, has to be removed in the target and then set to pending, as the assignment will be valid in the future. |
© ITSENSE AG. Alle Rechte vorbehalten. ITSENSE und CoreOne sind eingetragene Marken der ITSENSE AG.