State on RITM Set By Workflow Being Overwritten

[jmiskey]

So, we currently have a Catalog Item that has a workflow attached to it.  The workflow runs off of the sc_req_item table and has some Approvals.  I have it set so that if an Approval is rejected, the workflow goes to a "Set Values" action that sets the "State" of the RITM to "Closed Rejected", and then sends out a Notification and goes to the End.

Whenever I test one, and Reject an Approval, it looks like it is going down the correct Workflow path, but for some reason my State appears to be overwritten, as it is always set to "Closed Complete".  And it isn't just this one workflow, but this appears to be happening to all of our workflows that are trying to set the State to "Closed Rejected". 

Here is what my action looks like. 

I have tried it with various different values for Stage ("Request Cancelled" or "Completed"), but it does not appear to make any difference.  

We checked the Business Rules, and I could not find any which appear to be interfering with this.  Is there anything else which could be causing this to happen?  How can I find out what is causing this?

Thanks

[Steven Parker]

Could try putting like a 5 minute timer activity after you set the state to "Closed Rejected" and see if it changes although you should see that activity in history.  Possibly even try a run script and set "current.state" instead of the set value activity.

[jmiskey]

So, I replaced it with a Run Script that only does the following and added the 5 minute timer.  Here is what the "Run Script" code looks like:

current.state = 'closed rejected';

And nothing happened (stayed in an "Open" state).

So I tried using the value instead (and keeping the 5 minute timer): 

current.state = 8;

and it immediately went to state "Closed Complete", even with the 5 minute timer.

So it looks like it is completely bypassing this state.

I double-checked to make sure that there were not any other Choices in the Choice list for that element with a value of 8, and there are not.

[Steven Parker]

I just tested this in our instance using out of the box "Pending" state and it worked fine with the Set Value activity (3 minute wait just to test):

[jmiskey]

As you pointed out, "Pending" is an out-of-the-box choice, while "Closed Rejected" is not.  If you add a custom value of "Closed Rejected" to your choice list, can you still set it to that value?

It seems to me that the two most likely issues are:

- For some reason, it won't set it to Custom added values to that choice list

- There is something else overriding my change

[Steven Parker]

You have something overriding your changes or something else happening since it's just skipping your setting of the state value.  The custom "Closed Rejected" state worked fine in my instance with just a 1 minute wait this time: