Jump to content

Recommended Posts

Posted

Since today's update I started getting an error "No GotoIf found" and on investigation it appears that the comparison is being made against the description rather than the value.

Is that the case, or am I mistaken?

 

Posted

Hi @DeadMeatGF,

Could you provide more info? When it happen, what is the flow? Are you able to create an example flow that is giving you that message?

Thanks,
Miro

Posted

The flow is 'DC Reprographics Request'
The first error was mentioned about 10:20 today - a few minutes after I applied the latest Service Manager update.
I adjusted the BP to compare both description and value and the error stopped.
There is no 'No Match' option on that node, as it's from a mandatory PC question which is a radio button so there can only be one of two possible answers.

I'll see if I can knock up a test flow shortly.

Posted

@DeadMeatGF there was a release with fix today - branching was not working properly with values from checkboxes. Could you check if this was related to the problem you found?

Posted

@Miro, @Ehsan

Our instance has yet to update to Collaboration build 951, which I presume would normally be undertaken automatically as there is not an option in the Admin Tool to manually apply it.

How do I force the update to this as we are waiting on this to be applied before we proceed with Service Manager build 1364, due to the issue it fixes in progressive capture?
image.png.9ce76e8026d6d2a07a2b745a9c3935f9.png
 

Cheers

Martyn

Posted

Something went wrong when the build was pushed to live we are reviewing the logs and rebuilding this version which should go out as 952 shortly.

Kind Regards

Trevor Killick

  • Thanks 1
Posted

@Martyn Houghton the fix regarding problems with branching over variables set by custom question checkbox list is already released  - Collaboration Core Build 952 (23-Oct-2018).

If you still have problem then it must be something different. Creating simple flow that I can use to replicate your problem would definitely speed up things.

Thank you,
Miro

Posted

@Miro

We had not applied SM1364 at the time of my original post, as we were wanting on the delayed Collaboration build. We have not just applied SM1364, so will monitor but hopefully we will not have any issues now following the fix  in collaboration build.

Cheers

Martyn

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