Set Values workflow activity is not setting REQ field values from the RITM workflow - Known Error

Set Values workflow activity is not setting REQ field values from the RITM workflow Description Within a workflow on a RITM, attempting to use a Set Values workflow activity to set some value on the Request (e.g. "Request.Approval = 'Rejected'", etc) does not work.

Steps to Reproduce

1. Create a new Workflow on the sc_req_item table.

2. Once the new Workflow is open, add a "Timer" activity for 10 seconds immediately after the "Begin" activity.

3. Place a "Set Values" workflow activity and set "Request.Approval" (dot-walk the field value) to a value of "Rejected".

4. Save and Publish the Workflow.

5. Create a new Catalog Item and associate the "Workflow" in the "Process Engines" tab of the Catalog Item.

6. Using the "Try it" functionality, order the item and go to the Requested Item. Click the "Show Workflow" related link and refresh the workflow (top right icon) until the "Set Values" activity has passed.

7. Go into the REQ record and note that even though the "Set Values" activity completed, the value does not change. Creating a "Run Script" activity in place of the "Set Values" activity with something like the below workaround code resolves the issue and sets the desired values.

Workaround After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make this decision lightly, and we apologise for any inconvenience.

Utilize a Run Script workflow activity instead of a Set Values activity. Sample script below:

var req = new GlideRecord("sc_request"); req.get(current.request); req.approval = "rejected"; req.update();