SR-127035 · Issue 193206
Improved opening custom flow rules with Microsoft Internet Explorer 9
Resolved in Pega Version 7.1.8
Opening up a flow rule with many sub-process references was taking an excessive amount of time when using Microsoft Internet Explorer 9 due to general browser slowness and the system loading all referenced flow rules at that time. This has been resolved by tuning the JavaScript code to improve the performance of the viewer and to disable drilldown functionality from the server.
SR-130696 · Issue 199065
Updated config query for VBD date/time support
Resolved in Pega Version 7.1.8
When following the recommendation to add required date-time columns on VBD configuration tables for Oracle Golden Gate set up, the VBD configuration could not be saved to a database table from PRPC. This has been resolved by adding an updated configuration query to support replication.
SR-130731 · Issue 198828
HTTPS support added to DSM applications
Resolved in Pega Version 7.1.8
If the PRPC instance is accessed via HTTPS and the DSM applications (ADM & VBD) are installed on the same Tomcat configurations, the DSM services landing page did not provide the ability to say if the services were accessible via HTTPS. This is now possible through an added configuration option on the landing page to enable secure connection.
SR-131929 · Issue 200525
Added ability to extend CDM logic with custom shapes
Resolved in Pega Version 7.1.8
In order to support adding customized shapes to strategy rules in the CDM layer, the extension point has been opened by enabling some configurations, mainly for canvas extension and shape validation.
SR-128463 · Issue 193907
Create KeyRing updated for split schema
Resolved in Pega Version 7.1.8
If a command line script is configured (viz. keyringGen.sh) to encrypt user passwords for prconfig.xml databases using Keyring utility, a prconfig.xml could have three database entries but the keyring tool only prompted for two databases and did not allow encrypting password for the user for the third database. The prconfig.xml file requires very specific location information to run: to resolve this, the variables to hold schema name in case of split schema configuration have been added.
SR-113624 · Issue 167070
Enabling out-of-the-box Security Policies now redirects immediately
Resolved in Pega Version 7.1.7
When enabling out-of-the-box Security Policies, it was not immediately redirecting to the change password screen but instead requiring the timeout interval to expire before redirect happened. This has been corrected.
SR-116508 · Issue 170253
Large flow handling improved for IE8
Resolved in Pega Version 7.1.7
When opening a large flow in IE8 which includes multiple sub flows, a long-running script warning is displayed. This is caused by too many calls being executed at once on IE8, and has been remedied by turning on the asyncProcessing parameter for IE8.
SR-116818 · Issue 167121
Corrected swim lane routing with shapes
Resolved in Pega Version 7.1.7
While using swim lanes, adding shapes into the flow caused unexpected and random behavior of the process modeler including failure to return control to the user after saving. This error was related to routing handling when swim lanes are present, and has been corrected.
SR-117228 · Issue 168249
Resolved issues with Flow shapes distributed across Swim Lanes
Resolved in Pega Version 7.1.7
Pool size is maintained as both pixels and inches, but auto conversion was failing if the pool dimension was very large. This created an error where saving a flow rule could cause the pool to drastically shrink (for example, 20 inches becoming 20 pixels). In order to maintain the proper dimensions, a check has been added for pool and swimlane to ensure the proper inch/pixel conversions.
SR-118880 · Issue 172588
Change Password redirect loop fixed
Resolved in Pega Version 7.1.7
When URLEncryption is enabled along with Security Policies, redirection to the Change Password screen caused the browser to loop into an endless redirect (HTTP 302 loop). This was caused by Incorrect (un-obfuscated) data being used internally when obfuscation was enabled, and has been fixed.