SR-A14740 · Issue 232864
Edit button page retrieval updated for better accuracy
Resolved in Pega Version 7.2.1
Due to the Edit button configuration for Data types passing the identical name "Data Type" to the Landing Page action configuration, the pages being retrieved for editing were inconsistent when moving between the Dashboard and the Manage Change screen. The system has now been updated to pass the unique pyInsHandle key for every data type to ensure expected results.
SR-A18813 · Issue 236196
Support added for auto-generated numeric IDENTITY columns in RD
Resolved in Pega Version 7.2.1
Because IDENTITY auto-generated columns were not supported , RD did not identity the column of type numeric() IDENTITY and generated an error when accessing a table with NUMERIC column types in SQL Server 2012. Numeric() TYPE was already supported for generation in RD, and an SQL connector has been added to handle tables with numeric() IDENTITY as well.
INC-144917 · Issue 598200
Healthcheck will only initialize after successful node startup
Resolved in Pega Version 8.5.2
Nodes were not starting up, but because the Healthcheck service was initialized even though the node was not started properly, errors related to that were overriding the actual exception causing the node startup to fail and it was not possible to diagnose the startup issue. To resolve this, an update has been made that will ensure the Healthcheck service is only initialized when the node is initialized successfully.
SR-D8790 · Issue 487285
Corrected thread cleanup logic for doUIAction in WorkCover
Resolved in Pega Version 8.2.3
When accessing a case from the worklist or opening the case from worklist and refreshing the case by pressing F5, clicking Approve resulted in a java.lang.NullPointerException error. Investigation showed that the "pyWorkCover" page that the section was running on was being removed in the top navigation portal / SDM portal as part of the thread cleanup logic in doUIAction. This has been corrected.
SR-D5126 · Issue 487185
Corrected active state selector for IOS devices
Resolved in Pega Version 8.2.3
When scrolling RDL, gray artifacts were observed which did not always disappear from the UI. This was traced to the background color being applied wrongly due to an incorrect selector for active state in the layout that resulted in the gray region being visible. To resolve this, the selector has been updated to target only non-IOS devices for active state.
INC-190819 · Issue 681999
Wrapper added to set correct bulk transfer context
Resolved in Pega Version 8.7
Bulk transfer was not working as expected when transferring an assignment from a flow defined in data class. Investigation showed the bulk transfer UI was getting picked from work- class while the post processing was running under data class context: this has been resolved by creating a wrapper activity in baseclass to call the post processing activity Work- .
INC-179722 · Issue 659280
Added handling for legacy HTML formatting in Email Manager Bot
Resolved in Pega Version 8.7
When implementing Email Manager Bot features, pyBody fields were removing the additional spaces and causing the NLP model to not extract the correct data. Investigation showed HTML formatting from older version of Microsoft Outlook created nbsp; instead of space. This has been resolved by ensuring nbsp is replaced with spaces before calling JSoup clean.
INC-198632 · Issue 687582
Handling added to correct class setting during DX-API
Resolved in Pega Version 8.7
When a DX-API call was made (assignments/{ID}/actions/{actionID}/refresh) the ApplyPageInstructions activity was updating the case with an incorrect class, causing the rules from the wrong class to be picked and blocking the case progression. This has been resolved by setting the proper parameter Param.workPage while calling pzApplyPageInstructions from pzUpdateCaseWithRequestBody to calculate the proper class for the content.
INC-178214 · Issue 664890
D_ProjectList updated to resolve defined databases error
Resolved in Pega Version 8.7
After update, an API error for D_ProjectList indicating "No databases defined" was seen when trying to load decision and templates for the first time. The error did not reoccur after the initial save. This was has been resolved by updating the handling for loading the properties file during class loading. The error has also been changed to an exception.
INC-193289 · Issue 679210
Security updated for @baseclass
Resolved in Pega Version 8.7
After update, searching for a baseclass 'when' rule returned no results. Listing the rules under baseclass in App Explorer resulted in the error "Applies To: The Class with key value(s) %40baseclass does not exist". This was an unintended side effect of security updates, and has been resolved by creating an exception path for "@baseclass".