SR-A19871 · Issue 237975
MS Transport supports Global Resource Settings
Resolved in Pega Version 7.2.1
Documentation indicated that the JMS Transport data instance supported GRS syntax, but attempting to do so generated an error. That support is now available as indicated.
SR-A19932 · Issue 243259
Corrected cancel function in Calendar options
Resolved in Pega Version 7.2.1
If the pxCalendarViewGadget was launched in a modal dialogue, clicking the cancel button in the Calendar options menu caused the assignment to be submitted. This was caused by a form submit and harness refresh being incorrectly called together by the cancel, and has been changed so the click of cancel in calendar options will refresh the pzCalendarOptionsDefinition section but disable the form submit, resulting in the previous values being retained.
SR-A19972 · Issue 238961
Expanded search re-indexing submit methods
Resolved in Pega Version 7.2.1
When creating an index in the 7 series, the Search Landing Page for indexing did not indicate that the page needed to be submitted to enable the indexes before attempting to start the re-indexing process. An error was thrown in the tracer, but nothing was displayed on-screen to indicate why the system hadn't started indexing. To ensure the expected results, the indexing will begin after the "Submit" button is clicked or if the enable indexing check box has been checked to indicate the system has permission to start indexing without having an explicit submit.
SR-A19980 · Issue 242374
Added RunShortCut security for reporting
Resolved in Pega Version 7.2.1
Unauthorized users were able to run out-of-the-box reports through pxRunShortcut by updating the address URL and executing the final "pxRunShortcut" activity. pxRunShortcut now includes the function "pyCheckSecurity" for customers to write their own privilege conditions, and Page-Set-Messages will display a message created in the pyRuleSecurityErrorMsg HTML.
SR-A19986 · Issue 242898
getAppHashForApplication API updated
Resolved in Pega Version 7.2.1
When logged in from an end user portal, editing a decision table and clicking on the gear icon to add a function would show the Function's headers (Example, Activity, string, etc.), but the functions list would not be loaded. This was traced to a timeout resulting from having numerous functions running on the portal combined with a configuration that returned an unowned AppHash when calling a ruleset from the production layer rather than the application layer, and has been resolved by adding logic to write out the AppHash when the appInfo is created from opening the application.
SR-A19986 · Issue 244104
getAppHashForApplication API updated
Resolved in Pega Version 7.2.1
When logged in from an end user portal, editing a decision table and clicking on the gear icon to add a function would show the Function's headers (Example, Activity, string, etc.), but the functions list would not be loaded. This was traced to a timeout resulting from having numerous functions running on the portal combined with a configuration that returned an unowned AppHash when calling a ruleset from the production layer rather than the application layer, and has been resolved by adding logic to write out the AppHash when the appInfo is created from opening the application.
SR-A20030 · Issue 238280
Corrected sizing collapsed grid height to content
Resolved in Pega Version 7.2.1
A Repeating Grid using Progressive pagination and "Size grid height to content" with a configured number of rows to be shown without expansion was not accurately sized down when the content was below the display number. The function to adjust height of progressive grid has been fixed to display the content as expected.
SR-A20048 · Issue 237600
Error message for BIX DDL schema updated
Resolved in Pega Version 7.2.1
Attempting to create BIX DDL through the Designer Studio led to the error message 'No Instance found in the database' when an invalid schema path was used. This error message has been modified to more specifically identify the problem to assist in troubleshooting.
SR-A20058 · Issue 238045
PEGA0020 alert updated to include socket read time
Resolved in Pega Version 7.2.1
Socket read time was not unaccounted for in the PEGA0020 alert. Changes have been made to the invokeaxis2 activity to update the timer to include time related to reading the SOAP envelope.
SR-A20067 · Issue 243517
Fixed thread locking for authenticated SOAP
Resolved in Pega Version 7.2.1
Exception messages were being logged when the authenticated inbound SOAP service was called from a client application due to two threads simultaneously trying to load a data page at node level. The locking has been corrected to resolve this.