SR-C85853 · Issue 425289
Currency codes updated
Resolved in Pega Version 8.1.4
The list of Currency Codes has been updated with the latest ISO changes, including Venezuela and Sao Tome & Principe.
SR-C86133 · Issue 426388
Logic updated to resolve Strategy Parser error using dateTimeToBigDecimal
Resolved in Pega Version 8.1.4
After upgrade, a Strategy run was failing with a SemanticAnalysisException error indicating "Type Mismatch in node 'ILTernaryOperation': False branch does not equal return type (DECIMAL ==> DATETIME)". Upon investigation, the issue was traced to a property set component with an expression using the "DateTime•dateTimeToBigDecimal Pega-RULES:08-01-01" function. To resolve this, the logic has been modified to set the return type of ternary node from the Java type, and to check that True and False branches match this return type as well.
SR-C86138 · Issue 431777
Security updates for avatar upload function
Resolved in Pega Version 8.1.4
Updates have been made to enhance security around the avatar upload function.
SR-C86195 · Issue 423608
Logic added to map shorthand timezones to their official counterparts
Resolved in Pega Version 8.1.4
When the time zone in the operator profile record was a non-standard value and no timezone was selected in the operator profile, the date picked in the calendar was reduced by 1 day each time a section was refreshed. For example, if the timezone "IST" was used for India in the Pega operatorID record while the official timezone name is "Asia/Calcutta", the date selection was off by a day after refresh. To resolve this, logic has been added for mapping shorthand timezones to their standard timezones.
SR-C86213 · Issue 424585
Corrected PRAuth URL handling for sessions on restarted nodes
Resolved in Pega Version 8.1.4
If a user session was in progress and the node restarted, attempting to refresh the session when the node came back up was not working. Launching a new browser session cleared the problem. A trace showed that the Authentication Selector screen was not loading because the PRAuth URL redirection was going into an infinite loop, and this has been corrected.
SR-C86260 · Issue 424929
RecordsEditor Section- Parameters for HideDelete and HideAdd held on clipboard for use
Resolved in Pega Version 8.1.4
On initial load of a RecordsEditor section, the delete and add options were properly hidden from the user. After using any sort option on any column, the parameters were not persisted and the delete and add icons became visible. To resolve this, the implementation has been updated so that the pyHideDelete and pyHideAdd parameters will be read from myParamPage on the initial load and saved on a clipboard page for use.
SR-C86822 · Issue 424717
50 count limitation removed from application list export
Resolved in Pega Version 8.1.4
Previously, using Designer Studio -> Application -> Distribution -> Export to export the list of applications limited the results to 50. This number was hardcoded in the page size count setting for the Report Definition. In order to better support complex installations, this limit has been lifted.
SR-C86952 · Issue 428817
Viewing screen capture attchments no longer requires IE/Silverlight
Resolved in Pega Version 8.1.4
Previous versions of the Pega Platform required the use of the IE browser with Silverlight to access old attachments added using the screen capture feature. In order to support multibrowser compatibility, the system has been updated to use javascript functions to display these images so IE/Silverlight are not required.
SR-C87309 · Issue 430091
Shortened cleanup time for unauthenticated requestors
Resolved in Pega Version 8.1.4
Any type of probing done to the system with a public URL was generating many unauthenticated requestors that had a one hour lifetime if the user hit /PRAuth and left before reaching the postAuthenticationActivity. In order to speed cleanup in such cases, the system has been updated to ensure the postAuthActivity that sets setShortTimeout(true) is called even if the authentication isn't completed.
SR-C87399 · Issue 426185
pzEditSkills activity updated for better skill matching
Resolved in Pega Version 8.1.4
In the pzEditSkills activity, a select skill is added to the operator. A check is made using a comparison of pyRuleName equal to pySkillLabel to see whether this skill exists in the system; if it exists it is directly added to the operator profile, and if it does not it is created and added to the operator profile. However, pyRuleName uses a short skill identifier string, for example ‘XML’ whereas pySkillLabel is the longer human readable string, for example ‘XML programming skill’. Therefore, it was possible for Pega to determine the skill did not exist and proceed to creating a new skill with pyRuleName equal to the pySkillLabel of the existing skill in the first available unlocked ruleset. In order to ensure the proper matches are made, the pzEditSkills activity step 4.1 has been modified to get the rule name instead of skill name.