SR-B12374 · Issue 282127
Resolved StaleThreadError in LogHelper
Resolved in Pega Version 7.3
Repetitive stale thread errors were appearing in LogHelper. A check for thread destruction has been added to resolve this.
SR-B12374 · Issue 287614
Resolved StaleThreadError in LogHelper
Resolved in Pega Version 7.3
Repetitive stale thread errors were appearing in LogHelper. A check for thread destruction has been added to resolve this.
SR-B12451 · Issue 283057
Added case type propagation for layered applications built with NA wizard
Resolved in Pega Version 7.3
After creating an application on top of another using the New Application wizard and selecting the case types which need to be included the new application, not all of the cases and classes that should be present were shown. This was an issue with the correct pagelist not being checked while populating case types in the layered application, and code has been added to ensure all the case types of an existing application will come to a newly created application if the new application is built on top of an already existing application.
SR-B12474 · Issue 282643
BIX extraction config documentation updated
Resolved in Pega Version 7.3
When using command-line BIX 7.1 to extract records and write them to a secondary database, it appeared that some of the records got skipped. This was actually expected behavior: as the records got updated while the extract was running, those particular updated records got skipped as they did not fall into the time range that user was passing. To eliminate this confusion, the log message has been clarified. In addition, the information in the Guide indicated that if bix/useHistoryClasses was set to true, the generated query should always use the history table and not the actual work object table. However, it was not made clear that the BIX code does not use this option for explicit command line arguments. Therefore, the following text has been added to the BIX documentation under "Configuring the extraction environment" -> "Configuring optional prconfig.xml settings": Including class instances added during a batch run To ensure that class instances added to the Pega Platform database after a batch run begins execution are included in the extract, add the following property:
SR-B13088 · Issue 287632
SLA correctly reset after reassignment
Resolved in Pega Version 7.3
When the SLA values were updated on routing the task, the newAssignPage and assign table were updated with the new SLA details but the pxFlow page was still holding the old SLA values. This caused the updated SLA details to not be displayed in the out-of-the-box pyAssignmentListGadget section. This was an issue with the pxAdjustSLA and Reassign activities not completely updating the embedded page pxFlow in the WorkPage completely, and has been fixed.
SR-B13418 · Issue 283237
Attachments removed when work object withdrawn
Resolved in Pega Version 7.3
After adding an attachment and then withdrawing the case, the unneeded attachments were still being stored in the attachments section until a refresh was performed. This was traced to code in the UpdateAndDeleteAssignments activity that appended the target page rather than replacing. This has been modified to ensure attachments are eliminated when the status of a work object is moved to 'Withdraw'.
SR-B13647 · Issue 291863
Security Policy updates to handle big strings
Resolved in Pega Version 7.3
The implementation of a "one of" Access Control Security Condition that took the list from a Data Page was failing SQL construction due to the string exceeding 4000 chars. To resolve this, support has been added to SetClob() for page references, changes have been implemented in for the AllOf and OneOf functions, and a new property 'pyParameterValueUpdated' has been added to the Pega-RulesEngine.
SR-B13647 · Issue 291683
Security Policy updates to handle big strings
Resolved in Pega Version 7.3
The implementation of a "one of" Access Control Security Condition that took the list from a Data Page was failing SQL construction due to the string exceeding 4000 chars. To resolve this, support has been added to SetClob() for page references, changes have been implemented in for the AllOf and OneOf functions, and a new property 'pyParameterValueUpdated' has been added to the Pega-RulesEngine.
SR-B13702 · Issue 287232
SLA correctly calculated for migrated rules
Resolved in Pega Version 7.3
After upgrade, using the case designer view to look at a case type created in an earlier version displayed errors in the right panel for the goal-HH:MM:SS and deadline-HH:MM:SS fields if the assignment had the SLA rule "Default". This was an error in backwards compatibility related to whether the "pzIsAutoGenerated" property used to distinguish the SLA was auto generated or not, and has been corrected by setting the Visibility condition .pzAutoGenerated to 'true' in the lower Dynamic layout to avoid a null value in migrated rules.
SR-B13872 · Issue 290520
StartDependencies RUF logging updated from Error to Debug mode
Resolved in Pega Version 7.3
After calling a utility to create a child case through an activity on a parent sub-flow, updating the parent case status with the "UpdateStatus" activity logged an error message that the dependent had not been created successfully. This was an unintended side effect of a logging change made for diagnostic purposes, and has been fixed by changing the logs from Error mode to Debug mode in the pzStartDependencies RUF.