INC-164171 · Issue 644705
Support added for connect-SOAP run in parallel mode
Resolved in Pega Version 8.6.1
When connect-SOAP was configured to use the “run in parallel” mode, application settings derived through a datapage had incorrect values. While running the connect-SOAP through an activity, all the values were derived incorrectly. This has been resolved by adding a synchronization enhancement to support parallel run connect.SOAP.
INC-162426 · Issue 638769
Regex handling updated for Rich Text Editor spellcheck
Resolved in Pega Version 8.6.1
When using the Rich Text Editor and performing a spell check, the spell checker was adding additional CSS to the property. This was traced to the presence of a unicode newline character causing the existing regex to fail to strip the style tags. To resolve this, regex handling for the unicode newline character in the style tag has been added.
SR-D18741 · Issue 490420
GRS support added to Display name and Reply to for SendEmailNotification
Resolved in Pega Version 8.3
After upgrade, it was not possible to send email notifications when using a Datapage property in the email account rule. Investigation showed that there was a custom activity being used to call the SendEmailNotification activity and set the pyNotifyAccountName value as email account name by enabling Pass current parameter page, and the custom call was not functioning due to the SendEmailNotification activity being completely refactored in recent versions of the platform where GRS support (which was not a documented feature) was removed. For better backwards compatibility, this issue has been resolved by adding GRS support to Display name (pyFromFullName) and Reply to (pyReplyTo).
SR-C84788 · Issue 422936
Handling added to maintain custom modal template name after errors
Resolved in Pega Version 8.3
When using a grid where each grid row had an Edit button which launched a modal dialog with a custom modal template, the post action activity of the flow action introduced error messages on a top level page (not on primary or pyWorkPage). Clicking the submit button again caused the modal dialog size to shrink and not work after that. This was traced to the second submit using the system's pyGridModalTemplate instead of the custom modal template due to the modal submit button being replaced with new markup. To resolve this, the modal launch will now use the "pega.u.d.submitModalDlgParam.modalSection" variable which will have the modal template name. In addition, a check has been added to ensure this is not passed as null.
INC-158018 · Issue 633375
Archiving updated to include pxobjclass in CTE column list
Resolved in Pega Version 8.6.1
After enabling the case archival feature on a casetype, cases were getting stuck in the Archive-Ready state while being archived, and a 'column not found' error was seen. Investigation showed that the generated SQL statement used to retrieve the resolved case instances used a common table expression (CTE) whose columns were inskey, insclass, and parentinskey, and the query that referenced the CTE was attempting to compare the column pxobjclass when pxobjclass did not exist in the CTE's column list. To resolve this, the CTE column list has been updated to pzinskey, pxobjclass, and parentinskey to prevent the 'column not found error' from occurring, and the query that referenced the CTE was also updated to use the correct column names and aliases.
SR-D2796 · Issue 438392
Corrected Recents list resize issue in IE
Resolved in Pega Version 8.3
When using IE, opening the Pega Developer Studio to the landing page correctly resized the Recents list unless another tab was open. If there is another tab, the the resizing did not work and the scroll bar only allowed movement to the left. This has been corrected by setting the position to absolute for iframe(designer studio tabs) for IE.
SR-C95727 · Issue 435551
Enhancement added to automatically manage runtime context for background processing
Resolved in Pega Version 8.3
After creating a dedicated queue processor in a branch ruleset, the processor was not showing up in the queue processor list in Admin Studio. Attempting to queue something to this queue processor with a correct access group pointing to an application with access to the branch ruleset resulted in the error "Unable to find queue processor instance in memory". Moving the queue processor to a ruleset other than the branch worked as expected. This was traced to an issue with context management. In order to improve this process, an enhancement has been added for automatic management of the runtime context for the Background Processing mechanism. This will use system runtime context to discover queue processors and job schedulers that need to be run, and the context will automatically maintained by the platform when Applications are created, deleted, saved or imported. The system administrator is able to use a portal (studio) to manually modify the system runtime context by adding, reordering, removing Applications and changing the application version. To use this automatic management, check the "Include in background processing" checkbox on the application rule form (Advanced section): when checked, the application is placed on the list of System Runtime Context during application rule save (which happens e.g. during application import, migration, etc). If the background processing checkbox is not set, the runtime context of the background processing will continue to require manual management, but that management will now be in System Runtime Context instead in the previously used ASYNCPROCESSOR requestor type, which has been deprecated.
SR-D1386 · Issue 446261
Warning message visibility conditions updated for Records Editor
Resolved in Pega Version 8.3
The Report Definition Result screen was showing the message "Warning : We were unable to create columns to match the new properties added. This will cause performance problems when using this data type. Please click here to fix this." Along with the RD results screen, this particular warning message was also shown in the Records tab of the respective Datatype. Initially, the Records Editor was developed for Designer Studio and Express usage. When the delegation functionality was later given to portals, the 'when' condition for the warning message was not updated to restrict displaying it to portal users. This has been fixed by updating the pzManageRecords section to properly manage the visibility condition of the warning message.
SR-D6265 · Issue 477258
Cursor action corrected for pyRecents section refresh condition
Resolved in Pega Version 8.3
If a “Layout Group” was used to add content in the left panel of the User Portals, the inclusion of the out-of-the-box pyRecents section with the standard refresh condition resulted in incorrect cursor behavior when selecting landing page options, displaying the content in a tab while the cursor in the left hand panel jumped up or down one position. Investigation showed that the index in the bar menu was wrongly set in sessionstorage when separators were present, and the issue has been resolved by updating the setstate and maintainstate methods to not consider the menu-separator in calculating the index.
SR-C94549 · Issue 438432
Secure RESTful implementation for Websphere Liberty added
Resolved in Pega Version 8.3
Mbean server connection errors were seen when trying to configure remote SMA in Websphere Liberty 18.0. The local mode worked as expected. Investigation showed that some needed IBM classes and jars were not present because Websphere Liberty does not ship with the same Java Libraries as traditional Websphere, causing a ClassNotFoundException when attempting to use the admin client Java APIs needed to connect to remote nodes. To resolve this, a secure RESTful implementation for Websphere Liberty has been added. Additional configuration is required on the target nodes, prweb in order to use this RESTful API: see the following IBM documenation: https://www.ibm.com/support/knowledgecenter/en/SS7K4U_liberty/com.ibm.websphere.wlp.zseries.doc/ae/twlp_admin_restconnector.html The above configuration will only work with the new prsystmgmt WAR provided as part of this fix.