Segment fails to populate at parent level
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:
Error whilst refreshing child segment ChildSubs:
(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 &#39;AI&#39;, &#39;BST1&#39;, &#39;CT&#39;, &#39;DP&#39;, &#39;DSTR&#39;, &#39;DSTR1&#39;, &#39;DSTR2&#39;, &#39;DSTR3&#39;, &#39;DSTR4&#39;, &#39;DSTR5&#39;, &#39;DSTR..."
is too long, maximum length allowed is 255</pxMethodStatus>
Steps to Reproduce
- Have a parent segment referencing a child segment
- Have a child segment containing GroupName exceeding 260 characters
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.
Perform the following local-change:
Use shorter GroupNames.
Published May 7, 2019 - Updated December 2, 2021
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.