Auto-Generated Data Page Name Weirdness (BBBBBB vs. BBBBBBB)
New here. I'm running into a problem when deploying to different environments. In our development environment, the page pgRepPgSubSectionpyWorkListWidgetGridsAuto, from the Code-Pega-List class, is generated by Pega with six Bs at the end. Once deployed to our testing environment, the page is generated with seven Bs, breaking functionality since we're looking for the page with only six Bs. The functionality is implemented in an activity where it takes a number of selected assignments and then transfer them to a specific user.
A temporary fix is to attempt to get the value from pgRepPgSubSectionpyWorkListWidgetGridsAutoBBBBBB, check if a value is present, and if not, copy the value from pgRepPgSubSectionpyWorkListWidgetGridsAutoBBBBBBB (with an extra B). This is obviously not ideal since I still don't understand the methodology behind how the page name is generated.
Has anyone else observed this behaviour? What controls the generation of page names in Pega? Is there a better way to get the value which won't be sensitive to a change to the page name?
I already replied similar post on another forum. Here was my response.
As far as I understand these page names are generated at design time while saving section and not auto-generated at runtime. Secondly our application code should never use these pages directly as this page name generation depends on the layouts in section. These page names are generated for grids that reference the Report definition directly to contain the results of report definition.
Any application which wants to utilize such results in their code should provide a custom page name instead of relying on auto-generated name. (Sample screenshot below)
I would suggest to customize configuration to use custom page name to fix the issue.