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

Segmentation population error

SA-20047

Summary



While trying to build a Segment of two, user deployed criteria of Age > 1, to be used as part of a Program run. 

In the visualization mode, when user runs the segment get a 'Segment Population Error'. Checked the segment classes created, the table, Report Definition and Data Flows are all created, however the database table was empty.

The issue appears intermittent as sometimes the Segment runs and sometimes it does not. When Segment does complete, tried to use it as part of a Program run, but the Program fails citing a problem with the Segment.

Error Messages



This segment has failed execution in the background due to the following error(s):
Segment population error
Last Run: Feb 2, 2016 2:12:32 PM

Steps to Reproduce


 

  1. Create new Segment at top level, add criteria (Age > 1) and Save. 
  2. Run Segment


Root Cause



Developer was using a custom Customer class, hence it is mandatory; after following all the changes mentioned under steps 1 and 2; developer was able to run the Segment and Program successfully without any issues.


Resolution




1)  to perform the following additional steps to be able to run the Segment successfully.

    Copying the below rules from 'PegaMKT-Data-Customer' class to 'Group-Data-Customer' class:

    1. The 'CustomerData' Data Flow
    2. For 'Customer', 'CustomerDDS' and 'CustomerNoPartitioning' Data Set,
        a. Ensure that the 'Customer' Data Set Rule maps to the new Customer class database table.
        b. Update the 'Customer' Page property on 'PegaMKT-Work-Offer' class to reference the newly created Customer class (Group-Data-Customer).
    3. The 'SingleCustomerData' Data Flow. 

After these changes, Segment population started working, however Program run was failing which was referring this Segment.

2) The campaigns were failing with following error: “Exception in stage: Offer Flow”. After enabling loggings for following Activities, the exception traces were captured in the log files.
              Rule_Obj_Activity.ExecuteProgramRun.PegaMKT_Work_ProgramRun.Action
              Rule_Obj_Activity.ProcessProgramRun.System_Queue_ProgramRun.Action
And, the error in the log - “The reference pyWorkPage.Customer is not valid.  Reason: Cannot modify value of Reference Property without first linking it to another property using Property-Ref”. This error was caused because the Customer Property under the PegaMKT-Work-Offer class having “Allow use as reference property in activities" option on the Advanced Tab was enabled. Since developer has already saved-as the Property in their application layer and changed the class, this option can be disabled.

After these changes, the “Exception in stage: Offer Flow” was no more observed.
Suggest Edit

Published March 2, 2016 - 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