Differences

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

Link to this comparison view

Both sides previous revision Previous revision
tutorial:adm:status_task_how_to_set_up [2020/01/27 17:10]
stloukalp [Create and run task]
tutorial:adm:status_task_how_to_set_up [2020/02/19 14:31] (current)
stloukalp [Notification content]
Line 52: Line 52:
 <note important>​If there are multiple errors during CzechIdMStatusNotificationTask,​ just the last one is send to notification template. The rest can be found in application log</​note>​ <note important>​If there are multiple errors during CzechIdMStatusNotificationTask,​ just the last one is send to notification template. The rest can be found in application log</​note>​
  
-===== Notification content ===== 
-In status notification there are information about state of processes in CzechIdM. In CzechIdM there are asynchronous processes on many places. Advantage is that users do not have to wait for events, which are executed on the background. But on the other side users does not know the result of processes. This notification contains state of some vital agendas. 
-  - First of all there is **provisioning status**. This status is importatnt because of end systems. If some entity will be provisioned to end system and this process ends with failure, every other continuous provisioning to this system will be added to an queue. So it is important know, that some identity has not have failed provisioning and it's attributes are updated in end system. 
-  - Some **scheduled tasks** are not that important, but all of them has its purpose, so it is better if all of them did their job. Scheduled tasks are used as synchroinzation of data from HR or recalculation of states of identities (throught the night) or for sending email like this notification. 
-  - **Events** basically means asynchronous save process. In IdM almost every entity has asynchronnous save. So if during save process there is some failure, it means some data has been lost. So if someone or synchronization edited an entity and it failed, notification will tell you, you should check this agenda. 
-  - In **synchronization status** part there is list of failed synchronizations by system. It only write if there is some failures and not how many. It could be for example mistake or incomplete HR data or some mistake in workflow. 
-  -  In the last part there is list of **users**, whoose **state has been changed**. So it is kinda report. It will show you who of the employees has left, who is new employee and changes of exclusion. 
  
-Example of notification:​ 
-{{ :​tutorial:​adm:​statusnotification.png |}}