Assignment context transformations
- Silvan Grüter
- RoFa
Introduction
As described in https://itsense.atlassian.net/l/c/FY1EUCfV, a resource assignment can have a context. By default, this context is stored as internal references within the CoreOne Suite Meta Directory. For example an assignment of a resource submit taxes in the context of another user is stored as the combination of the other users Core Identity Id and Identity Type Id. The tax application itself will not understand this data an might need an official tax number id of the user which is stored on an attribute on the Core Identity. This is where you can configure a assignment context transformation to transform the CoreOne Meta Directory data to application specific data.
Properties
Whenever you are creating or updating an assignment context transformation, you have to specify the following properties depending on the context type.
Core Identity and Identity Type
Property | Data Type | Mandatory | Example | Description |
|---|---|---|---|---|
| Drop Down |
| Core Identity and Identity Type | A context type defined in the Assignment Context |
| Drop Down |
| SSO User | Select the identity type for which the transformation should be applied. |
| Drop Down |
| Username | Any unique attribute of the selected identity type. The attribute has to be unique to uniquely identify the user. |
Organization Unit
Property | Data Type | Mandatory | Example | Description |
|---|---|---|---|---|
| Drop Down |
| Organization Unit | A context type defined in the Assignment Context |
| Drop Down |
| Default | Select an organization unit type from where you would like to load the resolved attribute. |
| Drop Down |
| Tax Number | Any unique attribute of the selected organization unit type. The attribute has to be unique to uniquely identify the user. |
Related articles and How-tos
Â
Filter by label
There are no items with the selected labels at this time.
Â
Â
© ITSENSE AG. Alle Rechte vorbehalten. ITSENSE und CoreOne sind eingetragene Marken der ITSENSE AG.