Question
Facing issue with Circumstance definition
Hi,
We have customized Perform harness which is circumstanced (CPMPortalType circumstance template). Modified the circumstance template in application ruleset to include application related portals. In runtime, even the conditions are satisfied the circumstance version of harness is not getting called. But When circumstance definition is been checkout in the developer portal and open the interaction case in portal, then circumstanced harness is being called. Can someone please suggest, what can be the issue!!
PRPC V7.1.8 and CPM7.1.3 is what we currently use.
We have created the same rule with different name from where perform harness is getting called. This solved the issue.