SR-114184 · Issue 162116
Withdrawn non-empty classes caused JVM restart issues
Resolved in Pega Version 7.1.7
After withdrawing non-empty classes, attempting to restart the JVM system resulted in a null pointer exception due to the system trying to map the withdrawn classes. The system has now been updated to prevent the deletion of a class if it is not empty.
SR-114543 · Issue 163265
Withdrawn non-empty classes caused JVM restart issues
Resolved in Pega Version 7.1.7
After withdrawing non-empty classes, attempting to restart the JVM system resulted in a null pointer exception due to the system trying to map the withdrawn classes. The system has now been updated to prevent the deletion of a class if it is not empty.
SR-114312 · Issue 174692
Check added to handle invalid input in the year field for datetime
Resolved in Pega Version 7.1.7
Previously, when a date time property was provided with an invalid year containing more than four characters (such as 20142014), the date defaulted to 12/20/8963 when the form was submitted. A check has been added to catch dates of more than four digits when attempting validation.
SR-114479 · Issue 165273
Corrected locking for custom Access Roles
Resolved in Pega Version 7.1.7
After adding a custom Access Role to an Object in the WO class with an Access When rule defined to allow opening a instance, Obj-Open-By-Handle failed to lock the work item correctly and two operators could have it open simultaneously. This was caused by the custom stack inheriting parent state for all members, and has been changed.
SR-115026 · Issue 164316
Exceptions logged for PegaAESRemote with split schema
Resolved in Pega Version 7.1.7
In a split schema environment, the SPPR_POPULATE_INDEX_DATA stored procedure operates on the AES-related table PR_INDEX_INFO and is used to get index information. This stored procedure does not work with split schema because the stored procedure is not in the same schema the request is run in and the stored procedure is not schema-qualified. This issue only causes an exception in the log periodically when AES asks for index info. To avoid this, PegaAESRemote will not attempt the call to the stored procedure causing the exception, and all Connect SQLs are being updated with class reference in place of refer tables.
SR-115127 · Issue 163700
Viewing generated Java code with Tracer
Resolved in Pega Version 7.1.7
Previously, Tracer automatically returned the source for generated Java. This functionality was inadvertently removed, and has been restored.
SR-115133 · Issue 166141
Localization added for column section summaries in Report Definition
Resolved in Pega Version 7.1.7
The summarize column section displayed while running the Report Definition now accepts localization.
SR-115308 · Issue 173906
Japanese character support added to Report Definition PDFs
Resolved in Pega Version 7.1.7
When Report Definition contains Japanese characters in its report name, column, value, etc., the exported PDF was not showing the Japanese characters incorrectly. This was due to a missing font-family for the PDF export mode, and has been corrected.
SR-115313 · Issue 164520
BIX execution history did not update all Extracted rules
Resolved in Pega Version 7.1.7
If a BIX (Business Intelligence Exchange) extract was run with two extracts from the same shell script, the execution history was updated for only one of the extract rules. This was caused by the entry in the execution history (pr_log) is being overridden when the -i command line option is used. To ensure complete logging, the system has been updated to add a new entry to pr_log for every value when invoking the -i option.
SR-115378 · Issue 168818
Corrected horizontal scroll bars for listviews with custom searches
Resolved in Pega Version 7.1.7
Horizontal scroll bars were not appearing when using custom search section in a list view. This error was caused by missing logic for resizing the window width, and has been corrected.