Jump to content

Recommended Posts

Posted

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...

Posted

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]:})()

  • Confused 1
Posted

@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.

Posted

@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

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...