09/24/2023 10:10 PM
09/25/2023 07:50 AM
@shivmano , this is expected behavior. System will trigger only one email per request. It will pick new account task on priority if present, else will pick any one of the add access tasks present.
This is done to avoid multiple emails for same request to the user.
09/26/2023 01:46 AM
@nimitdave thank you for the response. This behavior could be a concern from end users perspective when entitlement is made mandatory as well as there is a different call for creating a new account in the target application. In such scenarios we will need to have a way to communicate to user that the access has been granted successfully that they requested.
Is there a way to print the entitlement in the new account's task completion email when a new account is requested along with the entitlement ?
09/26/2023 09:23 PM
@nimitdave / Team - regarding the above issue, I have tried using the ${entitlementshtmltablerows} variable in the task completion email but that does not seem to be allowed for use in task completion email.
I have also tried running the provisioning job in a trigger chain sequence with the first provisioning job only processing the new account task and the 2nd one processing the add access task. In this case, the 2nd job is not being triggered and is being ignored.
Can you please advise if there is any other alternative that can be put in place here?