Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Current interaction in composite is closed



When opening a work item from a search grid, the work item open in Review mode and actions cannot be performed. In particular, the entire section, SCMReviewIncludes, is missing.

Error Messages

Not Applicable

Steps to Reproduce

  1. Navigate to the Composite screen after account search and passing verification screen.
  2. Click any Service Intent.
  3. The Service Intent opens in Review mode. At this point, the Interaction details are not visible until the Service Intent is closed or the assignment opened.

Root Cause

A backwards compatibility defect in Pegasystems’ code or rules combined with a user error causes the issue. When the command executes, a particular circumstanced version of the Review harness should be utilized, one that is based upon the property, CPMPortalType. The application has a custom copy of the base Review harness, but no custom copy of the circumstanced Review harness. As a result, the base version is used, and this displays the incorrect result.

The solution is to create a custom version of the Circumstanced Review harness which is circumstanced on the property CPMPortalType.

The system does not allow two versions of the same-named harness to be created which are
circumstanced on two different properties. If the system has another Framework which was created independently of the PCS Framework, and it created its own version of the Review Harness, circumstanced on a different property, you will be unable to create the circumstanced custom version.

During a "save-as" on the Review harness circumstanced on property, "CPMPortalType", the following error occurs.
"pyCircumstanceProp: This rule already has a circumstance property defined (.harnessToDisplay): you cannot give it another"


Perform the following local-change:

Delete the other "Circumstanced" rules from the database. If you are not using the PegaFS ruleset, you can delete it from your application. Refer SA-9247,

If you need the ruleset, since the rules are marked withdrawn and are not intended to be used, you can create a custom SQL statement which deletes the circumstanced-withdrawn versions of the rule.

Pega is considering a future change in which withdrawn rules are not considered for this particular circumstanced validation check.
Suggest Edit

Published October 5, 2015 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us