How Can We Help?
Unified Supervisor Synchronisation - ViewsUnified Supervisor Synchronisation - Views
VIEW CREATE STATEMENTS
Download Postgres supervisor view create statements
Download Oracle supervisor view create statements
SUPERVISOR_DATA (Optional)
This view is used to list supervisor relations. This means that one row should exist in this view per supervisor relation you want to have in Pure. For each relation you have to specify an ID which will be the primary key for this relation. This means that this ID has to be unique for each supervisor relation and cannot change over time.
All columns in the below view must be supplied, even if they are not mandatory, in order for the synchronisation to work.
Either an internal or an external supervisor must be specified and it is not valid to specify both in one row. |
Column name |
Data type |
Size |
Mandatory |
Note |
Sync type. For each field pick on of: 'Yes', 'No', 'Once' |
|
---|---|---|---|---|---|---|
ID | String | 1024 | Yes |
This is unique ID of the supervisor relation. Keep above description in mind when defining ids. |
||
APPRENTICE_ID | String | 1024 | Yes | Lookup for apprentice will be done by NonExplicit Ids matching. | ||
SUPERVISOR_ID | String | 1024 | No(*) | If defined, lookup for supervisor will be done by NonExplicit Ids matching. | ||
SUPERVISOR_PURE_ID | Long | No(*) |
If defined, lookup for supervisor will be done by person pure id. Will be DEPRECATED: please use SUPERVISOR_ID instead |
|||
SUPERVISOR_SOURCE_ID | String | 1024 | No(*) |
If defined, lookup for supervisor will be done by person source id. Will be DEPRECATED: please use SUPERVISOR_ID instead |
||
SUPERVISOR_IDS_ID | String | 1024 |
No(*) If used, must be supplied together with a valid id source |
If defined lookup for supervisor (person) will be done by a classification defined id. | ||
SUPERVISOR_IDS_TYPE |
|
No Is used when matching on PERSON CLASSIFIED ID, otherwise not. |
The source where the SUPERVISOR_IDS_ID is related to. Provide the last part of the uri (key) of the classification. | |||
EXT_SUPERVISOR_FIRST_NAME | String | 1024 | No(**) | First name of external supervisor | ||
EXT_SUPERVISOR_LAST_NAME | String | 1024 | No(**) | Last name of external supervisor | ||
EXT_SUPERVISOR_ID | String | 1024 | No(**) | If defined lookup for external supervisor will be done by NonExplicit Ids matching | ||
EXT_SUPERVISOR_SOURCE_ID | String | 1024 | No(**) |
If defined lookup for external supervisor will be done by EXTERNAL_PERSON_ID from external person synchronisation Will be DEPRECATED: please use EXT_SUPERVISOR_ID instead |
||
EXT_SUPERVISOR_PURE_ID | Long | No(**) |
If defined the external person will be found using the Pure ID Will be DEPRECATED: please use EXT_SUPERVISOR_ID instead |
|||
EXT_SUPERVISOR_COUNTRY | Classification | 1024 | No |
Value from classification scheme /dk/atira/pure/core/countries Used when matching external person on name and when creating external person by name |
||
APPRENTICE_ORG_RELATION_ID | String | 1024 | Yes | The source ID of the organisation relation to be linked to on the supervised | ||
SUPERVISION_PERCENTAGE | Integer | No | The amount of responsibility this supervisor has in relation to the supervised. Provided values should be between 0 and 100. | |||
SUPERVISOR_ROLE | Classification | No | The role of the supervisor. Must be a key from classification scheme: /dk/atira/pure/person/roles/supervisor
|
|||
START_DATE | Date | Yes | ||||
END_DATE | Date | No |
(*) If the person is an internal person it is required that only one of the 3 ids is used
(**) If the person is an external person it is required that only one of the 3 ids or name is used. If name is specified we try to find an external person by that name, if not found an external person with specified name is created.
SQL for validating view
Updated at July 27, 2024