SR-116681 · Issue 169378
BIX Column length increased
Resolved in Pega Version 7.1.7
At runtime BIX checks the target DB metadata for column length. If it could not find the metadata with schema associated with the BIX DB user, it was setting the length at 32 characters even if a larger column length was specified in PRPC and SQL. This was due to a mismatch in the stored value location, and has been corrected so BIX will reflect the length specified on the Extract rule form.
SR-116716 · Issue 167507
Execute RDB runs in batch mode for very large data sets
Resolved in Pega Version 7.1.7
The executeRDB query was not able to handle very large large data sets, resulting in an OOM error after clicking on "Create Prior Authorization". ExecuteRDB (which is a select query) has been modified to run in batched mode, i.e. run the same query with limit on max rows, so as to avoid OOM when copying the whole result set into the memory object (similar to Report Definition paging).
SR-117039 · Issue 169671
Standardized class display options for App Explorer
Resolved in Pega Version 7.1.7
Inconsistencies had appeared in how Application Explorer handled switching the display between name and label (short description) in the class hierarchy display. The App Explorer menu now shows the option to toggle between Class labels and Rule names, with a default setting of displaying Rule names. In addition, the short description display will not include the rule purpose.
SR-117158 · Issue 169361
Corrected inclusion of "Other Specifications" in Document Wizard
Resolved in Pega Version 7.1.7
The 'Other Specifications' section of the application doc was being included regardless of whether the checkbox was selected in step 4 of the Document Wizard. This has been corrected to ensure 'Other Specifications' are documented only when they are selected.
SR-117391 · Issue 170006
Export to Excel replaces embedded control characters in APW
Resolved in Pega Version 7.1.7
In Application Profile Wizard, attempting to Export to Excel would fail if any specifications text contained an embedded control character (such as might appear after cutting and pasting from a Word or text file). To prevent the exporting failure, any control characters introduced into the generated data are now replaced with spaces during the export process.
SR-117461 · Issue 169210
Delete All Links' button disabled if rule is read-only
Resolved in Pega Version 7.1.7
When an Application Requirement rule is read-only due to being in a locked ruleset etc., the Delete All Links button was offered as an option. In order to avoid confusion, the Delete All Links button is now readonly when the rule is not editable.
SR-117604 · Issue 169493
Increased limit for Application Document flows
Resolved in Pega Version 7.1.7
Application Document previously limited the number of flows to 50 and would not list those exceeding the limit. This limit has been removed.
SR-117840 · Issue 170516
Autopopulate correctly set/disabled in the CSR portal
Resolved in Pega Version 7.1.7
Switching to some clipboard pages caused a null pointer error in the CSR portal for the operator. This was caused by an autopopulate call being made even when autopopulate was disabled. This has been corrected.
SR-117921 · Issue 174204
Warning message displays for ruleset save in lower version
Resolved in Pega Version 7.1.7
If a developer tried to save a rule in lower ruleset version while the same rule is already in a higher ruleset version, this was allowed with no warning. This behavior has been corrected.
SR-117961 · Issue 174233
Datetime conversion smoothed for SQL queries
Resolved in Pega Version 7.1.7
If the date time format on an SQL Server 2008 instance is set to ydm, a datetime conversion error was created due to the PRPC query using ymd format. In order to support all date formats for SQLServer, Timestamp is now formatted as "yyyyMMdd HH:mm:ss:SSS".