SR-B36134 · Issue 294147
Security fix to prevent URL tampering
Resolved in Pega Version 7.3
Pasting a URL that corresponds to an activity to invoke express on the browser URL allowed end users to get the express experience. To secure the system, the portal switching logic has been hardened to reinforce a portal check against access group privileges and to allow for equivalencies.
SR-B36418 · Issue 293162
More descriptive error message for RAP import
Resolved in Pega Version 7.3
In order to clarify that Schema migration does not support importing a table with the same name as an existing view or a view with the same name as an existing table, the code has been updated to throw a more descriptive exception.
SR-B36743 · Issue 293937
BLOB data save performance improved
Resolved in Pega Version 7.3
In an installation with many large work objects, performance issues were seen when saving a BLOB. This was due to the BLOB still saving data for properties that had been removed, and has been resolved through better tracking of orphan entries of list type properties like string list and java object list.
SR-B37139 · Issue 294520
Installation guide updated to reflect that ADM is supported on MS SQL.
Resolved in Pega Version 7.3
The installation guide has been updated to reflect that ADM is now supported on MS SQL server.
SR-B37923 · Issue 295190
null-pointer exception fixed for ForceCaseClose
Resolved in Pega Version 7.3
An exception was generated when running pxForceCaseClose due to an explicit call to the function before the Step Page was passed. This has been corrected.
SR-B39528 · Issue 303228
Node startup modified to support very large clusters
Resolved in Pega Version 7.3
Node startup was failing if the cluster had more than 50 nodes. This issue was caused by the query to the "pr_sys_statusnodes" table only returning 50 records; this limitation has been removed.
SR-B39730 · Issue 301187
tempItem parameter added to createworkprocess API
Resolved in Pega Version 7.3
The parameter tempItem has been added to the createWorkProcess API to hold a temporary work object which is passed to AddWork activity. The same naming convention is used.
SR-B39792 · Issue 298418
Validation removed for survey name property
Resolved in Pega Version 7.3
If the survey driver parameter "survey" was configured with a property reference to provide the survey name in the subprocess SurveyDriver, adding validations to it caused the property panel to generate an error. This was due to Validations on the pySurvey property checking if the survey existed with the configuration. To avoid this, validations on the pySurvey property have been removed and an added required condition has been put on the pySurvey
SR-B40657 · Issue 298764
Clarified database privileges to start Pega
Resolved in Pega Version 7.3
The documentation has been updated for clarity regarding database privileges for start up. The text "Pegasystems recommends that you create an Admin user separate from the Base user; however, if you opt for a single Base user, grant these permissions to the Base user" has been modified to read: "Pegasystems recommends that you create an Admin user separate from the Base user; however, if you opt for a single Base user, grant the Base user both sets of privileges listed above."
SR-B41106 · Issue 298379
Bulk process with only 'case type any' properly assigns all processes
Resolved in Pega Version 7.3
When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.