SR-119114 · Issue 173899
Security Enhancement to the pzTransformAndRun activity
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
As a security enhancement, a new pyAllowTransformAndRun 'when' rule (available rule) can be invoked by the activity pyTransformAndRun. By default this 'when' rule returns true, but this rule can be customized to validate the values of the parameter pyPreActivity and return true if it contains an invalid activity name.
SR-119130 · Issue 173876
"?" character allowed in URLs with get requests
Resolved in Pega Version 7.1.7
When specifying an Alternate Domain URL for a link, if the URL contained a GET request followed by parameters ("?get&p1"), the URL was modified by SafeURL to include an "=%26" between the "?" and "get" ("?=%26get&p1") (%26 is url encoding for an ampersand & ). In order to ensure alternate URLs are properly processed when they contain "?", a check has been added.
SR-119148 · Issue 173101
MSSQL columns with spaces in the name will generate an error seeking correction before submission
Resolved in Pega Version 7.1.7
While Microsoft SQL Server (MSSQL) tables allow columns with spaces in their name, the PRPC engine does not allow such names at this time. In order to handle the incompatible name issues, the Integrator Wizard will detect that it is dealing with a table that has spaces in its column names, and fail up front with a targeted error message.
SR-119158 · Issue 175351
Amended login caching to be compatible with new versions of Firefox
Resolved in Pega Version 7.1.7
When using the latest versions of FireFox browser (32+), there was a problem with logging in again after logging out. This was caused by a change in the cache engine for Firefox, and the system has been updated to compensate for the difference in caching.
SR-119223 · Issue 177088
DefaultValue API updated to retain values after deleting rows
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When deleteing rows from a repeating grid configured with readonly dynamic select control, the remaining rows were not properly holding their values. For example, if the row number to be deleted was "x", the "x+1" row occupies the Xth row place, but x+1th row's drop down value becomes lost and resets to "-Select-" value (Default Value). This was caused by the setOptionAndCaption API setting default caption instead of default value for the option tag. To rememdy this, the DS_setDefaultValue API has been updated.
SR-119239 · Issue 173898
Max limit error localized and variable added for unsaved work items
Resolved in Pega Version 7.1.7
In order to allow a local value for the number of unsaved work items, a new Field value has been created : MAXIMUMTABSALERT. In addition, the error message text "You have reached the maximum limit for pending changes. Please commit/cancel one or more changes to continue" is now available for localization.
SR-119246 · Issue 178095
Localization improved for Lithuania
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
If the localization was set to Lithuania, using a property of type Date with a control pxDateTime and configuring its display mode to Dropdown Lists only allowed 'month' to be selected rather than the whole date. In addition, the three letter month abbreviations were ambigious, using "Rug" for both Rugpjutis (August) and Rugsejis (September) rather than Rgp and Rgs. These issues have been fixed.
SR-119342 · Issue 176846
Purge/Archive on a cover case now auto-includes the covered objects
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
On running the Purge/Archive wizard over a cover case, only the cover case was archived while the underlying covered objects were not purged. This was caused by code that required the classes of the covered items to also be selected for purging. Since this was not the expected behavior, the code has been updated so that if a cover class is archived or deleted, its covered classes will also be included.
SR-119537 · Issue 174774
Improved speed for deleting repeat grid rows with Dynamic Select
Resolved in Pega Version 7.1.7
When deleting rows from a repeat grid with Dynamic Select and heavy HTML, deleting the first one was very fast but a delay appeared when there was one row left in the repeat grid. The browser message "Pegacloud not responding due to a long-running script" would also be displayed. This was found to be caused by a list-to-list control function being invoked for each processOnBeforeSubmit call which generated an increased number of input elements in the form. This has been corrected.
SR-119538 · Issue 177397
Detection added for custom work history tables
Resolved in Pega Version 7.1.7
In order to fully embrace mobile capabilities, columns were added to the work history tables to allow actions to be tracked as a geographical map where each history event is a numbered locale indicator on a map instead of a row of entries. From lat/long it is also possible to call a Google service and get the street address as well. However, this functionality caused some issues post-migration with if there were customized pc_history_work tables mapped to custom classes. To remedy this, a check has been added to only query for pxlatitude/pxlongitude if columns are exposed and shown, and that will detect if the columns aren't present.