The user is facing an issue with their Workflow "General Software Request" where the Approval activities inside of the workflow were unexpectedly approved (hint: they have an activity.result of "skipped"). The user wanted to know why this is happening.


It was found that the Approval activities in question could not resolve the parameters that had been set in them. Hence, when they tried to pull approvers and no approvers were returned from the search, the Approval activities were skipped (i.e. took the "Approved" path which has a condition of "activity.result == 'approved' | activity.result == 'skipped'").

Below are the failed parameters:

    • ${u_requested_for.manager}
    • 6a3a9eeb22393a00b94222131f9619ad

With regard to the first parameter ${u_requested_for.manager}, when navigating to the RITM record where the workflow is attached and viewing the XML for that record, the field "u_requested_for" was found to be empty. Hence, the workflow says, "As I am not able to find any value of any user in the 'u_requested_for' field, I cannot dot-walk to pull a non-existant user's manager. So, let's skip this" (i.e. take the "activity.result == 'skipped'" path).

This first parameter is on both approval activities, so it fails for both of them.

The second approval activity also contained a possible group (sys_user_group) to populate. In this case, the group which this sys_id is pointing to does not exist in the reported affected instance - hence, the approval activity cannot resolve this parameter either:

      • /

Article Information

Last Updated:2019-11-20 07:30:44