gotoif Process works perfectly in Test area, Immediate goto if error in Prod

[mmensah]

Dear Hornbill Team,

 

I've made and successfully tested a devlopment for my department's recharge process in the test area of the platform.

 

However when I made a copy of the process & and repointed the mailboxes and teams nodes to the live platform areas, every request ive made immeadtely has a goto if error in the 1st stage despite it being a simple yes/no decision.

With the exception of repointing mailboxes and teams, no other change has been made to the process.

Please can comeone clarify why this is happening as it seems that theres something about the live platform that's hindering it from recognising a decision match?

 

Please see the images attached of the working test version and the failing live version of the process in action.

[Steve Giller]

No Matching GotoIf means that none of the criteria you set for the Decision branches were matched and you do not have a "No Match" branch.

Note: You should always have a No Match branch for this reason.

As you have not shared the contents of the branches there is no way of knowing why they did not match, but from the error provided that is the reason.

[mmensah]

Hi Steve,

 

i originally used no match in the decision branch, but testing showed that requests kept defaulting to the no match option so i opted to use this method and it seemed to work. please see the contents below and the field the condition is based on

[CraigP]

Yes, one would expect it to always go down the No Match branch because the issue seems to be that for whatever reason it can't actually see the question/answer you've got it looking for.

The way the decision node logic is displayed in the BPM isn't very useful to be honest. It shows the "display" text for the question even though I'm fairly certain it's still looking at whatever the ID of the field and form was when you set it (in my experience you can change the wording of the question but leave the ID and the workflow will still work even though the display on the decision node logic in the BPM designer still shows the old wording). From the limited information presented, I wonder if you may have changed the ID of the question or the form itself after you set up these decision nodes in the BPM. Are you using the exact same Progressive Capture for your "Dev" version and "Production"? If you created a new Progressive Capture for production, does it have the same field and form ID as the dev one?

[Steve Giller]

An example of what Craig's describing would be if you've added a space to alter the name of the Capture from "MM Digital& IT Recharge Form v1.1" to "MM Digital & IT Recharge Form v1.1", or done something similar with a form or field ID.

[mmensah]

Hello Everyone,

I copied the InCap and repointed the necessary branches and that seems to have resolved the issue.

 

Thank you both for your help.