Differences

This shows you the differences between two versions of the page.

--- devel:documentation:identities:dev:contractual-relationship-slice [2019/08/13 13:54]
doischert [How customize the method for the create/update contract by slice?]
+++ devel:documentation:identities:dev:contractual-relationship-slice [2020/05/07 15:59] (current)
apeterova [Protection of the contract validity]
@@ Line 21: / Line 21: @@
 After synchronization correctly ended is started HR processes if is these option enabled. Together with HR processes is also started task **ClearDirtyStateForContractSliceTaskExecutor**. These task process all slices that has dirty state and recalculated their status.
-<note important>When you disable HR process is required created the task **ClearDirtyStateForContractSliceTaskExecutor** as dependent on synchronization. Otherwise slices will not be recalculated!</note>
+<note important>When you disable HR process is required created the task **ClearDirtyStateForContractSliceTaskExecutor** as dependent on synchronization. Otherwise slices will not be recalculated! LRT ClearDirtyStateForContractSliceTaskExecutor is very important part of slice sync, this LRT ensures create/delete of contracts and delete slices (marked during sync to as to delete). This is reason, why after every sync of slice, **must be this LRT executed**.</note>
@@ Line 31: / Line 31: @@
 However, in some situations (projects), it is required to use the **protection period** for which the contract will **not be terminated**, provided that there is a next slice in the contract, which restarts the contract. Furthermore must be ensured that the gap between the termination and the beginning of the contract is less than or equal to the protection interval.
-<note>**The protected interval** can be set using the property `idm.sec.core.contract-slice.protection-interval`, where the value is the **number of days**. If the number of days between the termination of the contract and its renewal in the following time slice is **less than or equal** to the number of days set in the protection interval, then the date of the contract validity **from** the following slice will be used instead of the date of **termination** of the contract from the currently valid slice.</note>
+**The protected interval** can be set using the property `idm.sec.core.contract-slice.protection-interval`, where the value is the **number of days**. If the number of days between the termination of the contract and its renewal in the following time slice is **less than or equal** to the number of days set in the protection interval, then the date of the contract validity **from** the following slice will be used instead of the date of **termination** of the contract from the currently valid slice.
 <note tip>
-**By default** is property `idm.sec.core.contract-slice.protection-interval` sets to value '**0**'. That means protection interval is **disabled**.</note>
+**By default**, the property `idm.sec.core.contract-slice.protection-interval` is set to value '**0**'. That means protection interval is **disabled**.</note>
+<note important>
+If you **change** the property `idm.sec.core.contract-slice.protection-interval`, it doesn't immediately affect already existing contracts and slices. You must ensure that **all** affected contracts will be recalculated, so the new value of the protection interval is used. The easiest way: run the reconcilation of all contract slices.</note>
 ===== How to customize the method for creating/updating contract by slice? =====