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 fails to populate at parent level

SA-65691

Summary



While configuring and testing multi-level segments with a parent segment invoking a child segment, the segment fails to populate at the parent level as it is unable to run the RefreshSegment activity after the child segment runs. This occurs at Step14 of the ExecuteSegmentDependencyTable activity.  If user removes JUMP on this step and moves it to a new Java step directly following Step14, the below code can be used to debug the failure of the RefreshSegment:
oLog.infoForced("Testing-pxThread\n"+ tools.findPage("pxThread").getXML());
 

Error Messages



Designer Studio:

Error whilst refreshing child segment ChildSubs:

PegaRULES log:

(port_Definition_Segment.Action) ERROR - RefreshSegment - Error processing segment: RULE-OBJ-REPORT-DEFINITION-SEGMENT APP-DATA-BAN PARENTSEG GMT Message: Error whilst refreshing child segment ChildSubs: 
(_Queue_DeferredSegments.Action) ERROR - The Segment Failed to open RULE-OBJ-REPORT-DEFINITION-SEGMENT APP-DATA-BAN PARENTSEG GMT


PegaRULES log: (with PrivateEdit to ExecuteSegmentDependencyTable) :

<pxMethodStatus>Fail: Database-BadInput-InvalidPage Trying to save an invalid page: page is not valid 
.Stage: "Set 1, Field class is equal to &amp;#39;AI&amp;#39;, &amp;#39;BST1&amp;#39;, &amp;#39;CT&amp;#39;, &amp;#39;DP&amp;#39;, &amp;#39;DSTR&amp;#39;, &amp;#39;DSTR1&amp;#39;, &amp;#39;DSTR2&amp;#39;, &amp;#39;DSTR3&amp;#39;, &amp;#39;DSTR4&amp;#39;, &amp;#39;DSTR5&amp;#39;, &amp;#39;DSTR..."
is too long, maximum length allowed is 255</pxMethodStatus> 



Steps to Reproduce

  1. Have a parent segment referencing a child segment
  2. Have a child segment containing GroupName exceeding 260 characters


Root Cause



A defect in Pegasystems’ code or rules. 'Stage Names' are created  by concatenating SetName + ", " + GroupName. The error is due to a group without label. The 'Where' clause is used since the group did not have the label.

Resolution



Perform the following local-change:
Use shorter GroupNames.

 

 

Suggest Edit

Published May 7, 2019 - 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