update the workflow on existing tickets

[Gary@ADL]

hi guys, it looks like a recent update has broken a poorly configured node in my workflow, is there anyway to update the workflow for multiple tickets, or a way to force the ticket to use the latest workflow, rather than having to fix each one by manually editing the node with the running workflow?

my poorly configured node here is referencing "service manager" rather "board manager", this hasn't caused any problems in the past, but now it throws an error saying cannot find board, i can fix this by changing the value to board manager, but we have quite a few tickets that will be affected by this,

 

many thanks

[EWA]

i get the same error

[Jim]

I create an auto task, set it to change bpm to the 'wrong one' or any alternative one, then set it to go to the original bpm, great way to restart request processes on the latest version :) 

[Jim]

the node for that looks like this

 

[HGrigsby]

Hi 

Our change workflow has started giving errors suddenly on the  "get user custom attributes" node.   

It has been in use for some time and no recent amendments have been made to it.

 

Have removed the above node to test some more and the next one stopped at a Move Card node with a similar error.

Will raise as a support call.

Helen 

 

[EWA]

I already did, as my flow is using Board Manager

[Gary@ADL]

thsnks for this @Jim

 

ive got the button working, however we are now getting failures if we have a node which auto-adds the card to the board, this now fails due to either the card already existing, or if we delete the card it still cannot add,

 

this has bricked hundreds of our key tickets we have open.

 

 

[Jim]

I've never had that error before and its been done on processes we use cards on very heavily, such as starters and leavers, I'm thinking Hornbill are doing something with the boards as a fair few people have reported issues with it, I'd possibly add a get card ID node in with a decision if found do x if not add card to cover the error then use the button again to pick up the new workflow

[Gary@ADL]

thanks again @Jim this seems to have worked to skip this node, however its now re-prompting for tasks to be completed which have already been completed, so i can now progress the tickets but will have a load of rework to do on each ticket

[Jim]

Hi @Gary@ADL, in my case i do it to restart them completely sometimes but you could make use of decision nodes to skip to a certain stage if certain custom fields exist for example, and as part of the auto task set that field, I usually use integer fields for this scenario. How many requests are we talking here also? I have a script that can trigger the auto task from a csv of request ids, as I had to move around 600 leaver requests onto a completely new request that I'm happy to share with you 

[Gary@ADL]

many thanks @Jim ive emailed hornbill support on this, i cant be expected to fully re-write and test multiple flows with these checks at every node it would take me at least a full day or 2, Hornbill have depreciated nodes before but it doesnt cause this , so i am hoping they will fix.  probably affecting 500~ tickets, 

 

thanks for the offer RE the script, i'l drop you a message if we need it  

 

 

 

 

[Gary@ADL]

it looks like other nodes are no longer working too, im getting a failure updating the card too doesnt sem to like the card ID im providing, but this has always worked prior to this

 

&[global["flowcoderefs"]["getCardInformation"]["cardId"]] - this references the node i have 2 nodes back.

 

ive also tried setting the card id to auto but this fails too saying the property was expected. 

 

[HGrigsby]

Also getting failures of different nodes later in the same workflow which has worked fine for months

These include :- Assign to peer review, Get user details, move card on board and get manager details.

Would appreciate it if this could be investigated as soon as possible

Helen

 

 

[Gary@ADL]

hornbill have advised this as fixed now FYI, i have reverted my workflows back to how they are and they seem to be working, but am monitoring still,

 

cheers