SR-D30505 · Issue 501895
Revalidate and save works for Service Packages using OAuth2.0
Resolved in Pega Version 8.2.3
Revalidate and Save was failing for service packages of type Data-Admin-ServicePackage which used authentication type as OAuth2.0 . If this was modified to basic authentication / unchecking authentication, revalidate and save was successful. Historically, the implementation of pzOnlyRestServiceType always assumed the primary page was the Service Package rule itself. To support this alternate use, the logic has been updated and a check of the Service Type has been added for the pxResults of the data page.
INC-211248 · Issue 713157
Survey navigation type set for use with complex CB refresh
Resolved in Pega Version 8.8
After upgrade from Pega 7.1 to Pega 8.5, creating a legacy survey used in pxSurveySection with a complex CB question page that contained a refresh option had collapsed tree navigation, the survey name was blank, and duplicate labels were found in picklist questions. To resolve this, an update has been added which will set the navigation type in parameters after a complex CB refresh and skip page copy while upgrading survey work objects.
INC-220893 · Issue 728488
Errors persisted for single case runs using a custom error handler
Resolved in Pega Version 8.8
Single case processing (SingleAccountData) had failed records when opening the SubscriptionData dataset, but it was not possible to see the failed record details for further investigation. Investigation showed that when running a single case run with a custom error handler, errors were persisted as part of the dataflow metrics, but not written to the database. To resolve this, an update has been made to ensure errors are persisted for single case runs configured using a custom error handler.
SR-D24318 · Issue 494057
Dom API updated to resolve IE11 not loading async data with refresh when
Resolved in Pega Version 8.2.3
The browser was continuously showing "loading" if IE11 was used for a section which was sourced from a data page and configured to load the data asynchronously from a external service while calling an activity and using a 'refresh when' rule to refresh the section if a property changed. Investigation showed that the initial data load was successful and the section with the data was visible, but if the property changed and the section loaded once again due to the 'refresh when' condition, the browser was unable to render the defer loaded section case because the dom returned had the wrong value. To resolve this, the API used to check for the dom element has been updated.
SR-D14630 · Issue 491164
Thread label clipboard issue resolved for work objects using skipDCDataModelUpdation
Resolved in Pega Version 8.2.3
n some cases, when a case ID was opened in Designer studio, its corresponding thread name in clipboard was pxThreadName instead of caseID or workID. Tab labels are handled through the Declare_pyDisplay data page. Investigation showed the child page pyDisplay(Developer) of the parent page Declare_pyDisplay, which was expected to contain pyUIElements for each tab, was missing an element for the tab whose label was shown as threadName. As this error was only reproducible for work objects with the 'skipDCDataModelUpdation' property set as true in the 'pyWorkPage', this issue has been corrected by updating the show-harness activity step-2 so the 'skipDCDataModelUpdation' property value is explicitly copied from primarypage ('pyWorkPage' in this use case) to 'parameterPage'. In addition, an issue with filtering records based on Operator Preferences has been resolved by updating ActivityStatusContentHandler to use a simple Show-HTML of the same "ActivityStatusSuccess" content instead of going through an unnecessary harness execution during activity when there is no session established.
SR-D7323 · Issue 493177
Pin Case to Board updated to use unique IDs for different workpools
Resolved in Pega Version 8.2.3
When using the Pin Case to Board functionality, it was only possible to find and pin cases in the default/current work pool of the working access group and not any other cases in any other work pools which allowed access to open/search/process. This was due to pyLabel being used to compare if a value entered was valid, which was not a unique key. To resolve this, the pyValidatePinDetails activity in Pega-Ext-Mentions-Documents, Pega-Ext-Mentions-Cases, and Pega-Ext-Mentions-Groups classes have been updated to compare pzInsKey instead of pyLabel to check for validate pin.
INC-142223 · Issue 600456
Mobile List rule correctly removed when case type creation fails
Resolved in Pega Version 8.4.4
When trying to create a new case type, a "Branch ruleset not candidate" error occurred. During this error process, the Mobile List rule that was created did not get removed. As a result, an InstanceAlreadyExists error occurred once the first issue was addressed and the attempt was made to create the case type again. Investigation showed that Mobile related views are created in pxCreateNativeListPageForCase activity but on failure during case type creation they were not rolled back in pzRollbackAndDeleteCasetypeAssets activity. This has been corrected.
INC-224954 · Issue 727045
Enabled turning off general metrics when queue processing metrics are disabled
Resolved in Pega Version 8.8
A memory leak related to QPGeneralMetrics was consuming heap and causing performance issues. Investigation showed queue processor metrics were gathered even when disabled. To resolve this, turning off "General Metrics Handler" while turning off the QPGeneralMetrics has been enabled. Queue processors should now skip the process of collecting general metrics while running activities. This will prevent storing unused (and uncleared) metrics in memory and prevent heap exhaustion.
INC-218001 · Issue 719920
Error text revised for parameterized data page used for token generation
Resolved in Pega Version 8.8
While trying to add a claim in the header of a Token Generation Profile instance, selecting Map From as "Clipboard" and trying to give any DataPage(parameterized) as the source property failed to be saved and the error "JWS Alias— Please provide correct algorithm key with correct key length." appeared. Changing the "Map From" to a Constant and giving a dummy value worked as expected. Tracer showed the error "declare page parameters not supported by PropertyReference", indicating the actual issue: at this time, the Token profile does not support using a parameterized data page. This has been addressed by ensuring an appropriate error message is shown on save of the token profile rule form when a parameterized data page reference is configured. The error will now read "The reference D_pzPreferenceStore[PreferenceOperatorID:"[email protected]"].pxObjClass is not valid. Reason: Parameterized data page reference is not supported." Support for a parameterized data page used with Map From will be taken as an enhancement for a future release.
INC-142223 · Issue 598648
Handling added for new case type using reuse case life cycle
Resolved in Pega Version 8.4.4
Creating a new Case Type in a branch ruleset using the 'Reuse case life cycle' option was not working, and the error "branch rulseset not a candidate" was generated. pxCreateCaseDataPages that are called as part of creating a case rely on Param.RuleSetName; generally this parameter is set in the param page when other assets are created. When Reuse case life cycle was selected, other assets were not created and param.RuleSetname was not set. This affected pxCreateCaseDataPages when branch parameter was provided. This was a missed use case, and has been resolved by setting param.RuleSetName from param.ruleset to fix the issue.