Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
devel:documentation:synchronization:dev:contract-slice-sync [2018/05/15 09:02] svandav [HR processes] |
devel:documentation:synchronization:dev:contract-slice-sync [2019/08/13 13:26] doischert [Fields for sync contractual relationship mapping] |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Synchronization - time slices of contractual relationship ====== | ||
+ | {{tag> sync contract slice}} | ||
+ | |||
+ | <note tip> | ||
+ | |||
+ | < | ||
+ | ===== What is time slice of contractual relationship ===== | ||
+ | <note tip> | ||
+ | |||
+ | ===== Actions after end of sync ===== | ||
+ | |||
+ | <note important> | ||
+ | |||
+ | ==== Select current contract slice ==== | ||
+ | |||
+ | Before HR process is executed long running task select current contract slice. This options is controlled by checkbox *After end, start HR process*. LRT is started synchronously and complete log will contain information about it. | ||
+ | |||
+ | ==== HR processes ==== | ||
+ | [[devel: | ||
+ | |||
+ | HR processes can be (**should be**) correctly started after the end of the sync. This can be ensured by the property `After end, start the HR processes` on the detail of sync configuration. If is this property ticked, then HR processes ' | ||
+ | |||
+ | ==== Automatic roles ==== | ||
+ | |||
+ | Recalculation of automatic roles is skipped during sync. Recalculation of automatic roles can be (**should be**) correctly started after the end of the sync. This can be ensured by the property ' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== Fields for sync contractual relationship mapping ===== | ||
+ | Bellow is an example of contractual relationship mapping using slices. This is only an example; in general, slices must be mapped in the same way that contracts are but must have two extra attributes: "Valid from of slice" and some sort of "Slice ID". | ||
+ | |||
+ | * **Contract code** - Code of the parent contract. This `String` value represents relation between all slices for the same contract. | ||
+ | * **Valid from of slice** - Defines time from that is slice valid. Valid till of slice is computes automatically (by validity of next slice) after save. Output value from attribute transformation must be ' | ||
+ | * **Owner** - Relation owner. Must be identity in IdM. This field is required for every relation. Output from attribute transformation can be: | ||
+ | * ID of IdM identity in String or UUID format. | ||
+ | * Username of IdM identity in String. | ||
+ | * **Main** - Define if is the contract main (between all contracts for the identity). Output from attribute transformation must be Boolean. | ||
+ | * **State** - State of contract. Output from attribute transformation must be enumeration ContractState or String representation for this enumeration (DISABLED, EXCLUDED) (more details see below). | ||
+ | * **Position** - String representation of contract. Typically name of contract. | ||
+ | * **Guarantees** - List of leaders, directly linked on the contractual relationship (more details see below). | ||
+ | * **Work position** - Define link to some tree node. Generaly define place in organization structure (more details se below). | ||
+ | * **Valid from of contract** - Validity for the contractual relationship. Output value from attribute transformation must be ' | ||
+ | * **Valid till of contract** - Validity for the contractual relationship. Output value from attribute transformation must be ' | ||
+ | * **Externe** - If is the contractual relationship for externe identity, then is output value (boolean true) . | ||
+ | * **Description** - String for description the relation. | ||
+ | * **Slice ID** - ID of the time slice, it is often transformed by combining " | ||
+ | |||
+ | |||
+ | ==== Guarantees field ==== | ||
+ | List of leaders, directly linked on the contractual relation. Linked leader must exists in IdM. | ||
+ | Output from attribute transformation can be: | ||
+ | * Username of leader (String). | ||
+ | * Id of leader (UUID or String). | ||
+ | * List of usernames (List< | ||
+ | * List of Ids (List< | ||
+ | * Null value. If is value not defined and in sync configuration has set ' | ||
+ | |||
+ | If some leader will not found. Then will be synchronization item marked as ' | ||
+ | |||
+ | < | ||
+ | ......................... | ||
+ | Finding guarantee [temslie7]. | ||
+ | ......................... | ||
+ | Warning! - Identity [temslie7] was not found for [temslie7]! | ||
+ | ......................... | ||
+ | </ | ||
+ | |||
+ | ==== Work position field ==== | ||
+ | Define link to some tree node. Generaly define place in organization structure. | ||
+ | Output from attribute transformation can be: | ||
+ | * Id of tree node (UUID or String). | ||
+ | * Code of tree node. Node by code will be searching in default tree (define in sync configuration ' | ||
+ | * Null value. If is value not defined and in sync configuration has set ' | ||
+ | |||
+ | If node will not found. Then will be synchronization item marked as ' | ||
+ | |||
+ | < | ||
+ | ........................ | ||
+ | Work position - try find directly by transformed value [Divanoodle]! | ||
+ | ........................ | ||
+ | Work position - was not not found directly from transformed value [Divanoodle]! | ||
+ | ........................ | ||
+ | Work position - try find in default tree type [DEFAULT_ORG] with code [Divanoodle]! | ||
+ | ........................ | ||
+ | Warning - Work position - none node found for code [Divanoodle]! | ||
+ | </ | ||
+ | <note important> | ||
+ | When isn't work-position attribute defined in the mapping, then **none** default position will be set.</ | ||
+ | |||
+ | ==== State field ==== | ||
+ | State of contract. Output from attribute transformation must be enumeration ContractState or String representation for this enumeration. | ||
+ | |||
+ | ContractState have this values: | ||
+ | * **[[..: | ||
+ | * **[[..: | ||