SR-A76837 · Issue 257171
Resolved blank property screen lock when WAI enabled
Resolved in Pega Version 7.2.2
When PegaWAI was enabled and a property-set-message method, run by clicking a button, set an error message to a blank property on the user portal (not in a flow), the screen became disabled. After entering a value in the field, the screen was still disabled and the error was not cleared and appeared in a fixed position on the page. This has been fixed by adding a null check to the displayError method in the harness_accessibility.js to handle conditions when there are no forms present.
SR-A95614 · Issue 263958
Modified logic for displaying default accordion tab with visibility when
Resolved in Pega Version 7.2.2
When the default tab selected in an Accordion was hidden by a visibility condition, the whole default tab calculation was incorrect and did not display properly. This has been fixed by modifying the defaultTab calculation logic when visible when conditions are present.
SR-A95614 · Issue 263995
Modified logic for displaying default accordion tab with visibility when
Resolved in Pega Version 7.2.2
When the default tab selected in an Accordion was hidden by a visibility condition, the whole default tab calculation was incorrect and did not display properly. This has been fixed by modifying the defaultTab calculation logic when visible when conditions are present.
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-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-A75998 · Issue 253191
Improved SOAP envelope cache for WSA/WSSE use
Resolved in Pega Version 7.2.2
After configuring and successfully using Connect-SOAP to a non-secure Endpoint, enabling WSA and WSSE for the connect-SOAP configuration and then disabling it again generated the error "Caused by: com.pega.apache.axis2.AxisFault: A required header representing a Message Addressing Property is not present". This was due to the way the SOAP envelope was being cached and the code has been updated to correctly reflect the desired header processing.
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.
SR-D35266 · Issue 509481
Check added to postOpenAssignment to support Ajax Container use
Resolved in Pega Version 8.2.4
After configuring an 'OpenAssignment' action on a begin button and giving the target as 'Dynamic Container', it worked as expected to open the assignment in a new tab on the Platform, but did not work from the Customer Service interaction portal. This was traced to the Customer Service portal using MicroDC to display the cases in the work area, which was not within the scope of the Ajax Container. Additional checks have now been added to the postOpenAssignment function to support this use.
INC-168253 · Issue 652547
Documentation updated for using Connect MQ with clustered queues
Resolved in Pega Version 8.7
After update to Pega Platform v8.6, an issue was seen with Connect MQ rules that used an alias queue. The support documentation has been revised to outline the necessary steps for updating an application to perform as expected. In the Pega-IntegrationEngine ruleset, create the following dynamic system settings and their default values: "mq/pmo" = 0 "mq/gmo" = 0 "mq/oo_request" = 1040 "mq/oo_response" = 16 For more information, dynamic system setting support articles are available.