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-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-115719 · Issue 165692
WebSphere WorkManager pool setting correction
Resolved in Pega Version 7.1.7
Due to a coding defect, the WorkManager thread pool setting configured through WebSphere was not being utilized. As a consequence, a large number of daemon threads could be created during certain scenarios and the ability to make connections could be reduced. This has been fixed, and the system will now use the WebSphere WorkManager setting.
SR-115955 · Issue 167257
Enhanced task queue handling for custom applications
Resolved in Pega Version 7.1.7
In some situations, a custom agent would periodically fall over when processing a large backlog of queued items. This was caused by an exception thrown when placing a task in the queue when it is already present. The system has been updated to better handle this situation and allow agents to continue to execute with the present schedule when a duplicate task is found.
SR-119432 · Issue 175615
Enhanced task queue handling for custom applications
Resolved in Pega Version 7.1.7
In some situations, a custom agent would periodically fall over when processing a large backlog of queued items. This was caused by an exception thrown when placing a task in the queue when it is already present. The system has been updated to better handle this situation and allow agents to continue to execute with the present schedule when a duplicate task is found.
SR-116130 · Issue 168010
StackOverflow errors during passivation remedied
Resolved in Pega Version 7.1.7
An issue was found with StackOverflow errors thrown by the passivation daemon, requiring a restart of the JVM. This was found to be related to the AutoPopulate API, and has been updated.
SR-116146 · Issue 169058
CreateUniqueID enhanced to allow custom instances
Resolved in Pega Version 7.1.7
The out-of-the-box PopulateReport activity previously used shorthand notation when referencing the CreateUniqueID function instead of referencing the function using the RuleSet or library name. This caused an issue with systems that contained a custom version of CreateUniqueID in the CMSUtilities library, resulting in "Multiple suitable instances found" errors. In order to accommodate custom instances of CreateUniqueID, long hand notation will be used for matching in place of shorthand.