Differences

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

--- tutorial:adm:notification_-_identity_s_last_contract_is_ending [2020/04/23 08:27]
klementm [Set up the Long running task (LRT)]
+++ tutorial:adm:notification_-_identity_s_last_contract_is_ending [2020/06/19 11:34]
klementm [Set up the Long running task (LRT) with technical identities]
@@ Line 66: / Line 66: @@
 Finally, we can set up the LRT. In the left menu, go to Settings>Task scheduler>Scheduled tasks and click the green button Add. Select the task type LastContractEndNotificationTask and specify the configuration of the LRT.
-{{ :tutorial:adm:task-.png?600 |}}
+{{ :tutorial:adm:lastcpont1.png?600 |}}
-You can specify how many days before the contract's end the notification should be sent. If you set it to 0 the notification will be sent the day the contract ends and the extras:contractEnd topic will be used. If you write a positive integer x (1, 2, ...) the notification will be sent x days before the contract ends and the extras:contractEndInXDays topic will be used.
+You can specify how many days before the contract's end the notification should be sent.
 <note tip>The notification is sent x days before the end of the contract or sooner. This is useful if for some reason the LRT did not run one day, it will simply be sent the next day.</note>
-You can select the role that the recipients of the notification will have assigned. You can only select one so if you need multiple ones, you have defined multiple LRTs.
+* You can select the role that the recipients of the notification will have assigned. You can only select one so if you need multiple ones, you have defined multiple LRTs.
+* You can also check the box and select whether the user's manager is to be notified as well. Only one manager will receive the notification!
-You can also check the box and select whether the user's manager is to be notified as well. Only one manager will receive the notification!
+**There is also support for technical identities. There are two options:**
-There is also support for technical identities. There are two options:
+* If you provide prefix, then the task will look for username with this prefix (for identity whose contract is going to end). If some are found, then it sends the notification.
+* If you select a role in "Code of the role used for technical identities" then it will look if identity with ending contract has some subordinates with this role.
-) If you tick "Identity is owner of admin account with this prefix" and provide prefix, then the task will look for username with this prefix (for identity whose contract is going to end). If some are found, then it sends the notification.
+<note important>Do not use a combination of these two. Create a new task if both needed!</note>
-) If you just set prefix with **not ticking** "Identity is owner of admin account with this prefix" then it will look for subordinates with this prefix of ending users. If some are found, then manager for ending identity is notified (or also some role holders according to other settings).
+The last option (Send invalid contracts) is if you want to send only valid users or all. The reason for putting this option to this setting is this case: Task did not run a couple of days and some users are already not valid. So it admin can decide if those identities will be sent too.
-The last option (Send invalid contracts) is if you want to send only valid users or all. The reason for putting this option to this setting is this case: Task did not run couple of days and some users are already not valid. So it admin can decide if those identities will be sent too.
 ===== Run the long running task (LRT) =====