Jump to content

Progressive Capture following 'no match' but no changes made?

Gemma Morrison

Recommended Posts



We are experiencing our service requests and incidents progressive captures following our 'no match' option via the selection progressive cap which use 'switch capture' nodes...we have made no changes and cannot find what the issue is to fix it.


The BPM's seem to be in working order.


Any ideas @Bob Dickinson @Victor - This has been raised via the support process via Paul Wilcock but we really need an answer/help please :D 

Link to comment
Share on other sites

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