Steve Giller Posted October 18, 2018 Share Posted October 18, 2018 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? Link to comment Share on other sites More sharing options...
Miro Posted October 18, 2018 Share Posted October 18, 2018 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 Link to comment Share on other sites More sharing options...
Steve Giller Posted October 18, 2018 Author Share Posted October 18, 2018 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. Link to comment Share on other sites More sharing options...
Miro Posted October 22, 2018 Share Posted October 22, 2018 @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? Link to comment Share on other sites More sharing options...
Martyn Houghton Posted October 23, 2018 Share Posted October 23, 2018 @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? Cheers Martyn Link to comment Share on other sites More sharing options...
Guest Ehsan Posted October 23, 2018 Share Posted October 23, 2018 Hi @Martyn Houghton, I'm looking into this. Thanks, Ehsan Link to comment Share on other sites More sharing options...
Martyn Houghton Posted October 23, 2018 Share Posted October 23, 2018 @Ehsan Thanks Martyn Link to comment Share on other sites More sharing options...
HHH Posted October 23, 2018 Share Posted October 23, 2018 I noticed the same with our instance 1 Link to comment Share on other sites More sharing options...
TrevorKillick Posted October 23, 2018 Share Posted October 23, 2018 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 1 Link to comment Share on other sites More sharing options...
Miro Posted October 23, 2018 Share Posted October 23, 2018 hi @Martyn Houghton, It seem like we have a hiccup with that release. We did another one and should be there. Sorry for any inconvenience. Thanks, Miro Link to comment Share on other sites More sharing options...
Martyn Houghton Posted October 23, 2018 Share Posted October 23, 2018 @TrevorKillick, @Miro Is there any update on when the Collaboration release with this PC fix in it will be released/applied? Cheers Martyn Link to comment Share on other sites More sharing options...
Martyn Houghton Posted October 23, 2018 Share Posted October 23, 2018 Ok, it would appear the replacement Collaboration 952 build has now auto applied to our instance. Cheers Martyn Link to comment Share on other sites More sharing options...
Miro Posted October 23, 2018 Share Posted October 23, 2018 @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 Link to comment Share on other sites More sharing options...
Martyn Houghton Posted October 24, 2018 Share Posted October 24, 2018 @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 Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now