Can someone let me know why this working flow is hitting on TRUE (correct) as well as False? I would expect it to only go the True route.
Can someone let me know why this working flow is hitting on TRUE (correct) as well as False? I would expect it to only go the True route.
Your LHS variable in the decision node does not look right.
It needs to be in the format Job : Name rather than Name.
What product version?
What is the NAME variable in the screenshot above?
Is it a variable that you created in the workflow or some out of the box one?
Do you see what value NAME variable has during runtime?
I suggest you use SQL Select node to create a new variable and populate it with the required value and then use the new variable in the Decision node.
For example:
select ${access_request_cri_arole_name} as newvar from dual
Boris,
Can I leverage this to determine if the account that the entitlement change is associated with is already disabled, then process a different manual fulfillment? What would that look like?
We have an app that users are disabled when terminated but app roles are maintained. By the time users get around to doing reviews, some users have left and the accounts already disabled. I want to avoid sending the account team an email to remove an app role on an already disabled account. In this case the users leave AFTER the review has already been launched.
Did u try recreate the Decision node, true & false transition ?
1. Delete the decision node, true & false transition then save the workflow.
2. Then create back the decision node, true & false transition and save workflow
Are you able to view Runtime data in workflow and check what is the changeitems been generated ?
There is a alternative to get the Application(Business Source) Name, u can try use this variable
${access_request_cri_app_name}
Are the transitions from the decision node configured correctly?