SR-D18209 · Issue 489547
Check added to avoid unnecessary show-harness when offline
Resolved in Pega Version 8.3
After upgrade, clicking on the Optional Process from the Action menu resulted in the error "The Operation completed successfully, but returned no content". This was traced to an unnecessary call to a show-harness step when offline, and has been resolved with the addition of a 'when' check.
SR-D15275 · Issue 490024
Report title displayed properly when prompting for filter changes
Resolved in Pega Version 8.3
Launching a report from the report browser showed a blank for "Report tab title" if the option "Prompt for filter changes before displaying report" was checked. This has been corrected so the name of the report is properly displayed when prompting for filter changes.
INC-164947 · Issue 639862
Handling added for missing div when opening work object
Resolved in Pega Version 8.7
In mobile offline app, opening a work object in a specific scenario for the second time resulted in an endless busy indicator. It was not possible to navigate away, and the app had to be closed and reopened to continue. Investigation showed that some app sections had an action that tried to load a harness section where one specific div was missing, and this has been resolved by updating reloadSectionOSCOHandler to handle the missing div in the failure callback. Additionally a console.error() will appear for the missing section.
INC-174625 · Issue 655242
Admin Studio will consider cluster protocol when returning listener status
Resolved in Pega Version 8.7
When using a few nodes in standalone mode for BIX extract combined with server nodes using Hazelcast, opening the admin studio pages with service discovery caused an error to be thrown. This was traced to the system writing an entry to pr_sys_statusnodes table as an embedded node whenever a BIX extract was triggered, causing those standalone nodes to be incorrectly considered by the listener landing page. This has been resolved by configuring the system to either return the local member when the cluster protocol is standalone or to return all Hazelcast members if the cluster protocol is Hazelcast.
SR-D10100 · Issue 464283
Bulk actions filter works properly when additional filters are added
Resolved in Pega Version 8.3
The Bulk Actions filter was not working if other filters were used in conjunction with it. Investigation showed that when 'assigned to operator' was given a value, the values were fetched properly. When an additional condition was added, the section 'pyBulkProcessingSearchSection' activity called 'pzDefaultOperators' which then set the 'pyUserIdentifier' value to null, and no results were returned. As the activity already had a step to check if the .pyUsage!="Operator" and only then property-set, pyUserIdentifier = "", the subsequent step to set the pyUserIdentifier = "" and override the previous step has been removed.
SR-D38450 · Issue 505656
Added workaround to handle HiddenPropertiesToIgnore when a page is in Read Only mode
Resolved in Pega Version 8.2.4
A 'WrongModeException' was generated while trying to use the Data Transform pxHiddenPropertiesToIgnore to remove system properties from page. When the Datapage was set to Editable/Savable mode, the Activity ran without an error and executed the Data transform. When the Datapage was in Read only mode, the error occurred. This was traced to a process that previously was allowed to set a page to an empty string, but which was removed during recent work. To resolve this, four instances of pxHiddenPropertiesToIgnore that included Single Page Value properties have been updated by moving them to the bottom of the Data Page and changing them to an "Update Page" from a "Set".
SR-C84294 · Issue 422375
Pagination repaired for RD using alternate database
Resolved in Pega Version 8.3
On selecting "Use alternate DB" option available in Report defenition and fetching the results of the RD to a grid, the results were not being fetched from the alternate DB but were fetched from the Pega DB only. This was traced to the property pyUseAlternateDB being overridden in step30 of pxRetrieveReportData activity. This step is skipped if it's report viewer, so if the same report is invoked from report viewer iit worked properly. To resolve this issue, the system has been modified to skip the step30 not only for report viewer but also if Param.pyUseAlternateDB is empty.
SR-D6947 · Issue 446500
Email AttachmentPage updated to support use of Data-WorkAttach
Resolved in Pega Version 8.3
Attachments were not getting appended in the email sent by the Agent SendCorr. This was traced to a null Page that resulted if the attachment was of type custom Data-WorkAttach, and has been resolved by modifying the condition check on the objclass of AttachmentPage to change it from equalsIgnoreCase(Data-WorkAttach-File to startsWith(Data-Work-Attach-) .
SR-D13880 · Issue 483330
Support added for using WorkPage class for FieldValue evaluation
Resolved in Pega Version 8.3
The Instructions provided under the Assignment details section of an assignment shape were not evaluating the FieldValue for the work object's audit history entries unless the field value was defined only at @baseclass. This was due to WorkPage class not being considered while evaluating a FieldValue, and has been resolved by modifying the InstructionsLookup control to use work class instead of the hard coded @baseclass.
SR-D34806 · Issue 506558
Horizontal scroll added to grids using Table Personalization
Resolved in Pega Version 8.2.4
After configuring “optimize code” and “personalization” options on a table which had more than 15 columns, the Optimization option on the table removed the horizontal scroll option from the screen and made some columns unviewable. If “optimize code” was not configured on the table, the horizontal scroll option appeared as expected. This was traced to the grid container not having scroll defined on it, and has been resolved by adding code to make the overflow columns visible.