and more in a single search tool across platforms. Read the announcement here. |
04/24/2023 11:51 PM - edited 04/24/2023 11:51 PM
Good morning experts,
I have a workflow for create user request as well as update user request that contains some multiple if else conditions.
The first part if employeetyoe eq to 'Staff' works as expected, although i have another If else condition on the false leg of this one for employeetype eq 'Saviynt Admin'. This last portion gets bypassed however and goes straight to the false leg of second if else condition which we use for third party user creation.
Below screenshot depicts current workflow. the second if else was added recently but cannot get working so right email templates can go out to approving manager.
When request is approved (which was sent on third party part of workflow) account gets created and EmployeeType is indeed 'Saviynt Admin'
Any advise on above.
Thanks in advance
Solved! Go to Solution.
05/02/2023 11:04 AM
Hi @fouriefb
Thanks for reaching out.
Thanks.
05/03/2023 02:10 AM
We got this resolved though, but you are right.
As the user's employeetype only gets populated at creation, we used the employeeType from Dynamic attribute instead and this worked.
05/02/2023 11:17 AM
Hard to see image (share xml) and confirm 'Saviynt Admin' and not end with 'Saviynt Admin"