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

Segment rules cannot be included in App Overlay Defintion



Validation error thrown when including existing segment rules are included in the Application Overlay rule.

Error Messages

Failed to save rule into revision ruleset. For the rule : AccytStatusAndRelatePT, Reason: ** SaveAs failed: Trying to save an invalid page: Trying to save an invalid page: page is not valid
.pyUI.pySource.pyJoinInfo(1).pyFilters.pyFilter(1): ** .CustomerID[VARCHAR2],MCDB.CustomerID[NUMBER] are not of hte same exposed type.
.pyUI.pySource.pyJoinInfo(2).pyFilters.pyFilter(1).pyFilterValue: ** An invalid comparison value or an invalid column has been entered for the right-hand side of a filter condition: 'J1'. Enter a valid column, calculation, or literal value.

Steps to Reproduce

Add segment rules in existing App overlay definition.

Root Cause

A defect in Pegasystems’ code or rules In the the Customer class, the key property is of text type whereas the mapped table column is of type NUMBER.

When a segment is created or saved-as, the report definition is also created and a join between the Segment class and Customer class is defined in the report definition.

When including a segment rule in application definition, it actually performs a Save-as of the segment rule to overlay application's ruleset. and the validation error when saving the report definition rule is thrown.


Apply HFix-29678, and HFix-29521.

Note: HFix-29521 is a PRPC hotfix and prerequisite to Pega Marketing HFix-29678.

Published August 23, 2017 - Updated December 2, 2021

Was this useful?

100% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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