SR-116764 · Issue 199322
modal dialog retains fixed size when traversing a flow
Resolved in Pega Version 7.1.8
When a modal is configured to have different formats, those formats were missing upon going to the next assignment. This was caused by the format of the modal being reset Configured Modal Format was not being applied once we process flow in modal dialog. This has been fixed by passing the modalStyle parameter to the modal dialog callback.
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-124298 · Issue 186402
SQL Merge use clarified for custom Tomcat installations
Resolved in Pega Version 7.1.8
Logic was added to ML7 to disable the SQL Merge command in environments that do not support it, but this was failing with an exception trying to parse the Tomcat name/version string if the installation was using a custom version of Tomcat and the string was not in the expected format. To handle this, the logic has been updated to to handle a custom Tomcat Name/Version string that may or may not contain version information. However, please note the following important information: The system will disable Merge if the out-of-the-box Tomcat version is detected where version If the system is using a custom Tomcat instance
SR-128684 · Issue 194308
Corrected save-as for Activity using API "02"
Resolved in Pega Version 7.1.8
In drop down generation, if a value was empty then adding the selected attribute for the first option assuming no options should have the empty value other than no selection text. To make this work as expected, if the value is empty then the system will add the selected attribute on the option which has empty value to avoid setting first option value to the hidden field.
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.
INC-182959 · Issue 668737
SQL queries modified to use qualified table references
Resolved in Pega Version 8.7
Portal launch in the development environment was taking an excessive amount of time, as were some standard reports. The PurgeAssemplyDatabaseCache agent activity also generated an error regarding "(internal.cache.RAPurge) ERROR - Purge, unexpected error in removeOldAppCentricCacheData". These issues were traced to SQL queries that contained pr_sys_app_hierarchy_flat without a schema qualifier, and have been resolved by changing to class qualified table references.
INC-185760 · Issue 668742
SQL queries modified to use qualified table references
Resolved in Pega Version 8.7
Portal launch in the development environment was taking an excessive amount of time, as were some standard reports. The PurgeAssemplyDatabaseCache agent activity also generated an error regarding "(internal.cache.RAPurge) ERROR - Purge, unexpected error in removeOldAppCentricCacheData". These issues were traced to SQL queries that contained pr_sys_app_hierarchy_flat without a schema qualifier, and have been resolved by changing to class qualified table references.
INC-174933 · Issue 651829
Special characters escaped for use in "is in List" lookups
Resolved in Pega Version 8.7
After creating a specific criterion on any proposition using a string property, the "Is In List" operator, and a customer list with one value containing a "$", clicking save or check in resulted in the exception error "Problem invoking function: pega_decisionengine_propositionfilterfua.pzPropositionFilterMethodBody--(PublicAPI,ClipboardPage) java.lang.IllegalArgumentException: Illegal group reference at java.util.regex.Matcher.appendReplacement(Matcher.java:857) ". This has been resolved by escaping regular expression control characters in string replacement, which will allow the use of characters such as the $ sign for "is in List" lookups.
SR-122500 · Issue 183869
Smoothed use of Row Repeat with a Repeating Grid that shares references
Resolved in Pega Version 7.1.8
Issues were found with the display of Row Repeat. It was not displayed when a section contained a repeating grid and row repeat layout that had the same pagegroup property reference, and in other cases was displayed improperly after taking the wrong class for a 'when' condition. The failure to display was due to the active page being the last page of the page group as set by Repeat Grid. The RepeatGrid layout generation was changed beginning in v6.3 onwards, and now uses a method-based engine. However, the RowRepeat layout has been deprecated and therefore still uses the previous generation method. This difference creates a conflict when the RowRepeat kicks off in the same stream generation. Furthermore, this issue arises only when the two layouts bound to same PageGroup property source, and not with a Pagelist property. To resolve this, the system now resets the activePage to that of the primary page in case of page group data source in the Repeat Grid generation so that the Row Repeat gets the proper active page for its generation. The issue with displaying when it should not has been resolved by retaining the existing business logic wherever the section rule with body visible when condition is used in a repeating layout.