SR-119074 · Issue 176791
Calendar Control accessibility enhanced
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
In accessibility mode, the Calendar Control defaulted to the current year +/- 10 years. This did not allow dates for lifetimes or for long-term activity dates. In order to improve functionality, the dynamic system setting 'pyNumberofYears' has been inserted to allow modification of the datetime cell properties as desired.
SR-119095 · Issue 174195
TagCloud rendering corrected
Resolved in Pega Version 7.1.7
When opening pxTagCloudViewGadget it generated the error: 'Unable to open an instance using the given inputs: pxObjClass = "Rule-Obj-Report-Definition", pyClassName = "", pyStreamName = ""' . The tag cloud gadget reported "Can not render @baseclass.pxTagCloudInit", and when run or included in a section, it did not render any tags. This was found to be a design time error in Obj-Open of the report definition, and has been fixed.
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.