BPM Editor - Weirdness

[Jeremy]

So this morning I have been doing some work in our BPMs and when adding multiple decisions when you add more than one it removes the previous decision.

I have recorded this behaviour and can be viewed below, but this is causing some headaches for us this morning....

https://drive.google.com/file/d/10c-y24B3CcyBDcNl9UrAvgl-Ul19jEJQ/view?usp=sharing

[Jeremy]

As there appears to be others that have BPM issues, my guess would be that one of the updates that was applied earlier has broken something...

[Adrian Simpkins]

Hi Jeremy I have come across the same issue I inserted a new decision node then the follow on decision nodes errored out, and now I can not get it working ! Error code I am getting:
Error: decision ("s1"/"decision-871260cb") parse: at 2/10: "Uncaught SyntaxError: Unexpected token )" return [() == true, (true) == true]; })()" ------------------------------ (function()( var outcome=false;if(global{"inputParams"]["outcome"]) {outcome = global["outputParams"] ["outcome"];}else {outcome = global["flowcode"]["outcome"];} return [() == true, (true) == true]:})()

[Jeremy]

This is still causing us issues here, has there been any investigations....

[Victor]

@Jeremy @Adrian Simpkins yes, we have benn made aware of the issue and development team was investigating. Sorry for not replying sooner. We had a bit of trouble finding why this happens but development found some inconsistencies with these nodes which appear to cause this issue. This is being worked on now.

[Jeremy]

@Victor thanks for the update

[Jeremy]

Has there been any further progress on this BPM issue?

[HHH]

I've found that editing a node breaks the connections following the next decision node

[Victor]

@HHH we are aware, working on a fix. There might be a workaround to avoid the issue. For any "broken" branch on a decision node, edit the current outcome, change it to something else then change it back to what it needs to be. This should fix the issue for the "broken" branches. @Jeremy @Adrian Simpkins FYI

[Adrian Simpkins]

Hi Victor

Thanks for the above I will give this a try and let you know if it works ok

Many thanks

[Jeremy]

@Victor we tried the workaround and it did not work for us so guess we will await the fix.

[Victor]

@Jeremy can you send me the workflow in the private conversation we have for the "View Email" issue?

 

[Victor]

@Jeremy @Adrian Simpkins this issue has been addressed in the latest admin tool update: 

 

[Adrian Simpkins]

Thanks Victor and to all the team, appears ok I have tried a small update just now and no issues any problems I will shout

Many thanks as always