SR-A19820 · Issue 237850
Landscape iPad modal windows improved
Resolved in Pega Version 7.2.1
Modal windows in the iPad landscape mode were cut off and did not display the Submit and Cancel buttons. This was due to improper height calculations in the modal dialogue, and the code has been changed to prevent the body scrolling when modal is opened and to prevent modal mask for height change when a dropdown is opened inside a modal dialog.
SR-A19844 · Issue 240019
Read-only section handling fixed for progressive grid modal window
Resolved in Pega Version 7.2.1
Despite setting read-only mode on sections fetched for display in the expanded view of a nested progressive grid, the newly loaded rows were loaded with read/write enabled. The system has been updated to ensure read-only mode is correctly maintained.
SR-A19858 · Issue 236943
Dialogue handling updated for WS-Security Profile password
Resolved in Pega Version 7.2.1
The presentation format for the password field of the WS-Security Profile outflow page has been changed to no longer display the password in the clear in any resulting dialogue.
SR-A19865 · Issue 240029
Migration script checks for compressed data before inflating
Resolved in Pega Version 7.2.1
While upgrading, the migrate script was failing while trying to create the tables.txt file content. This was traced to data handling. During engine start-up, a check is performed to determine whether bytes are compressed or not, and inflate those that are compressed so they can be read. The migration utility did not have this check, and by default went ahead and inflated. This caused exceptions when encountering BLOBs, as a BLOB contains both CompressedBytes and UnCompressedBytes. A check has now been added to the migration script so inflation is only done as needed.
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.