| Both sides previous revision
Previous revision
|
Next revision
Both sides next revision
|
tutorial:adm:notifications_standard [2019/08/07 19:05]
apeterova |
tutorial:adm:notifications_standard [2020/07/14 16:08]
apeterova wfTaskAssigned |
| |
| <note important> | <note important> |
| The notification about **creating a new approval task is not sent** by default. You must enable it - see core:wfTaskAssigned below. | The notification about **creating a new approval task is not sent** by default. You must enable it - see core:wfTaskCreated below. |
| </note> | </note> |
| |
| | CHECK | core:returnRequestIdentityRole | email | Same as core:changeIdentityRole, only for returned requests | | | CHECK | core:returnRequestIdentityRole | email | Same as core:changeIdentityRole, only for returned requests | |
| | CHECK | core:returnRequestIdentityRoleImplementer | email | Same as core:changeIdentityRoleImplementer, only for returned requests | | | CHECK | core:returnRequestIdentityRoleImplementer | email | Same as core:changeIdentityRoleImplementer, only for returned requests | |
| | CHECK | core:wfTaskAssigned | email | If an approval task is created for the user, the user will be notified about the task. This is must be enabled by configuration property ''idm.sec.core.wf.notification.send=true''. The notification contains URL to the task, so URL of the server (e.g. https://idm.domain.tld) must be set as first value in the configuration property ''idm.pub.security.allowed-origins''. | | | CHECK | core:wfTaskAssigned | email | **Disable** this topic, if you use version **10.4**, because it causes duplicate notifications on this version ([[https://redmine.czechidm.com/issues/2383|see more]]). For older versions, it's recommended to disable it as well. For 10.5+, this topic will be deprecated/removed. | |
| | CHECK | core:wfTaskCreated | email | If an approval task is created for the user, the user will be notified about the task. The configuration is same as for core:wfTaskAssigned. | | | CHECK | core:wfTaskCreated | email | If an approval task is created for the user, the user will be notified about the task. This is must be enabled by configuration property ''idm.sec.core.wf.notification.send=true''. The notification contains URL to the task, so URL of the server (e.g. https://idm.domain.tld) must be set as first value in the configuration property ''idm.pub.security.allowed-origins''. | |
| | | vs:vsRequestCreated | email | If a new request on a [[devel:documentation:modules_vs|virtual system]] is created, the implementer of the virtual system will be notified about the request | | | | vs:vsRequestCreated | email | If a new request on a [[devel:documentation:modules_vs|virtual system]] is created, the implementer of the virtual system will be notified about the request | |
| | | core:changeIdentityRole (**topic: core:roleRequestRealizedApplicant**) | email | After changing assigned roles of the user manually (after the role request is **finished on all systems** - by default without approving), IdM will send the information to the user, whose roles were changed. This can be turned off by the configuration property ''idm.sec.core.wf.notification.applicant.enabled=false''. [[devel:documentation:roles:adm:role_assignment#notification|Read more]]. It can be turned on by activating the topic. | | | | core:changeIdentityRole (**topic: core:roleRequestRealizedApplicant**) | email | After changing assigned roles of the user manually (after the role request is **finished on all systems** - by default without approving), IdM will send the information to the user, whose roles were changed. This can be turned off by the configuration property ''idm.sec.core.wf.notification.applicant.enabled=false''. [[devel:documentation:roles:adm:role_assignment#notification|Read more]]. It can be turned on by activating the topic. | |