Giuseppe Iannacone Posted April 13, 2021 Share Posted April 13, 2021 I'm receiving this error message while trying to validate the priority of a request, based on a task field outcome Link to comment Share on other sites More sharing options...
Giuseppe Iannacone Posted April 14, 2021 Author Share Posted April 14, 2021 @Victor can you help me in addressing this issue? thanks Link to comment Share on other sites More sharing options...
Steve Giller Posted April 14, 2021 Share Posted April 14, 2021 Without looking at the Workflow itself it is tricky to diagnose, but the error refers to TaskAnswers - you have three inputs to the previous Parallel Processing node; from Request Validation IN, Request Validation SR, and No Match. If the Decision node that is in error is branching on either of those tasks it can only have a defined answer for one or neither of them, never both. If it's branching on the results from a different Task we'll need a wider view of the Process. Link to comment Share on other sites More sharing options...
Giuseppe Iannacone Posted April 29, 2021 Author Share Posted April 29, 2021 @Steve Giller in regard of this topic, you have identified a defect and I know you are working to solve in a future update of Service Manager. When a new BPM has spawned all the custom field get reset or the data are persistent? 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