SR-B31094 · Issue 288810
Removed uppercase shift from GetColumnInfo and ValidateDBTable
Resolved in Pega Version 7.3
The Connector wizard was failing against external Sybase DBs due to the schema name being sent uppercase. This has been resolved by updating the activities GetColumnInfo and ValidateDBTable to remove the code that converts the names to uppercase.
SR-B31210 · Issue 290303
Draft mode defaults to off for SaveAs in Screen flows
Resolved in Pega Version 7.3
After upgrade, the behavior of Save as for Screen flows changed from defaulting from draft mode being off to draft mode being on. This was a missed use case, and has been fixed with a check in the Validate Rule-Obj-Flow activity that will not set defaultOn to true if the operation is SaveAs.
SR-B31303 · Issue 288518
Revision management GET logic revised
Resolved in Pega Version 7.3
When the revision manager creates a new revision, the second step is to add rules (strategies/data transforms etc.) into that revision so that a strategy designer can work on that. However, it was found that if one of the HTTP requests was of GET method, selecting the rules and hitting 'submit' constructed an oversized URL which listed all the rules listed on the Revision page and the browser would hang due to the GET exceeding the character limit. To avoid this, the logic used to create the post body has been modified to creating avoid long parameter values.
SR-B31462 · Issue 292183
PRDistributedMap allows custom cache
Resolved in Pega Version 7.3
A class has been added to the supported classes list in the distributed map object manager for DSM In order to support using PRDistributedMap to create an instance with its own cache.
SR-B31524 · Issue 293666
File Listener help updated to clarify duplicate checking
Resolved in Pega Version 7.3
The help file for File Listener has been update to clarify that the duplicate checking from 'Ignore duplicate file names' will be across ALL listeners once the file name has been processed by one listener. The duplicate is flagged for ANY listener processing the file
SR-B31533 · Issue 290736
Fixed wide repeat grid focus jump in IE
Resolved in Pega Version 7.3
When clicking on a wide grid in Microsoft Internet Explorer 11, the focus jumped to the left automatically even when all click/focus events have been removed from the grid. This has been resolved with a check so the system will not capture focus in cases where a horizontal scroll bar is present.
SR-B31589 · Issue 301671
Workaround for Oracle SMA query timeout
Resolved in Pega Version 7.3
A bug in Oracle can cause an SMA query involving all-constraints to take a long time to execute, which in turn can cause RAP/application bundle imports to hang. The workaround for this is to set the Oracle parameter _optimizer_push_pred_cost_based to false before the execution of the SMA query involving all-constraints, then set it back to true after its execution at the session level.
SR-B31631 · Issue 289775
Installation documentation updated re: postgis use
Resolved in Pega Version 7.3
To avoid confusion, the documentation for the installation process has been explicitly updated to indicate that data and rules schema cannot have postgis extension applied.
SR-B31665 · Issue 291063
TaskMethodHeader RUF updated to pass the param page
Resolved in Pega Version 7.3
The activity method History-Add was not adding pyTaskName in Flow FUA. This was caused by a difference in handling: Status Update via an Assignment uses the UpdateStatus activity by passing a new parameter page with only the target status value to be updated. Status Update via a Utility uses the same UpdateStatus activity by passing a parameter page created using the "CreateNewParamsPage" private method with all the required information. In order to ensure all of the needed information is available, the TaskMethodHeader RUF has now been updated to pass the param page by calling the "CreateNewParamsPage" private method.
SR-B31667 · Issue 291704
Consistent Work IDs between case types created in different implementations
Resolved in Pega Version 7.3
Creating an Implementation layer on the Warranty application using the New Application wizard of Pega 7.22 GA was resulting in a different Work ID prefix of some case types like Claim Unit or Appeal than when the same case types were created in the built on application. This was traced to different activities being used to populate the data page, and has been updated to ensure uniform work ID generation.