Update Status node

[Neil Smith]

Hi,

I am aware that there have been issues with the Update Status node, after a deployment in October, and a workaround, and a subsequent fix was provided.

However, we are still having issues with processes where there is an auto update status node.  For example. we have approval tasks on requests, and we have set an expiry deadline on those.  Once those tasks have expired, the customer is emailed, and the status of the request is automatically set from Open to Cancelled.  The later automation is the piece that isn't functioning.  

We are not seeing any errors in the workflow, and we have applied the necessary workarounds, and are now up to date with patching, so I'm at a loss as to why this has now stopped working, as it has worked consistently for the last year.

Are you able to advise?

Many thanks,

Neil

[Victor]

@Neil Smith can we have a look at that configuration? Screenshot or a copy of the BP definition file?

If you post a file make sure it does not contain any sensitive or confidential data (name, emails, etc.)

[Neil Smith]

[Neil Smith]

@Victor Screenshots above, thanks.  The highlight box is where the issue appears to be, as the preceding email notification is sent out ok, and the subsequent Expired checkpoint is marked too.

Would appreciate any help you have.

Thanks,

Neil

[Steve Giller]

@Neil Smith
Looks pretty straightforward - you're not setting the status to anything.
Change the Status parameter to "Manual" with a value of "Cancelled" and it will work as you intend it to.

[Neil Smith]

 

Hi Steve, it was set to that previously, but had issues since the October build, so we've tried the original workaround (ignore) and then we tried Auto.  Still no luck.

 

Thanks

[Steve Giller]

Hi @Neil Smith

Ignore does exactly what it says on the tin.
In this case there's nowhere for Auto to Automatically pick the value from.
The only option that can work in this scenario is Manual.
If you set it Manual with a value of Cancelled, run some tests on it and it's still not working then we can look into it further - all we can say from the screenshot provided is that your node is set up to not change the Status.

[Neil Smith]

Thanks Steve.  I've tried testing with the following configuration. but there's still no change in status happening.

[Victor]

@Neil Smith can you try putting a value in "Result Reference" field, something like "resultRef" (no apostrophes). Might be that the node fails to output values for the params due to the missing value and failing the whole operation due to this...

[Neil Smith]

Hi @Victor Appreciate the quick response.  Unfortunately that didn't work.  The tasks expire, but the status remains at Open.

[Victor]

@Neil Smith it can be that the workflow does no go via the "Expire" route... can you highlight and post the expression for the "Expire" branch?

[Neil Smith]

[Neil Smith]

Hi @Victor The preceding task (email to customer) is functioning ok, and the Expired checkpoint is met too, so it seems to hit the Expired route (see above).

Let me know if you need any further info.

Thanks,

Neil

[Victor]

@Neil Smith ah...so it does reach the "Expired" stage checkpoint.... meaning we know for sure it went down this path... another thing to check, just to be sure, do you publish the workflow every time you made a change?

 

[Neil Smith]

Hi @Victor Yes I'm publishing the process every time we make a change.  This is happening on all our service request processes, so I've taken a copy of one of them, and applied them to our test service, so we can test in isolation. 

The live processes have not been republished for quite some time, which is why it seems odd that it was working previously, and now it isn't.

Appreciate your help.

[Victor]

@Neil Smith ok, can you send me a copy of the BP definition file via Private Messaging?

[Neil Smith]

@Victorwill do, thanks.

[Neil Smith]

@Victor Hi Victor, did you manage to review the process I sent through? 

Thanks,

Neil