INC-133615 · Issue 581399
Rendering corrected for contextual prompt in Case Type
Resolved in Pega Version 8.3.5
In Case Type with multiple stages, clicking to add step->More at the last stage caused the More menu to be distorted and not usable. Investigation showed that whenever the contextual prompt was opened in this way and the layout had no space on the right side, it shifted left and moved beyond the visible layout. This was traced to the two column layout in pxContextualPromptWithPreview having display styling set to block, and has been resolved by updating this setting to display as table.
INC-136327 · Issue 591468
Stage keeps proper order placement on restart
Resolved in Pega Version 8.3.5
When a user restarted a stage, the stage moved to the end of the list of stages and stayed there even when completed. Investigation showed that when pxRestartStage was configured as a post-processing activity for a flow action, pxStageHistory was updated with a new list item which considered pxCameFrom and pxStageId as the same. Due to this, the current stage was moved to last in the chevron. This has been resolved by adding a new 'when' condition to pzLoadStageStatusDP that will skip the item of pxStageHistory (Alternate stage) if both .pxCameFrom and .pxStageId are same.
INC-139861 · Issue 594008
Cross-site scripting protections added to Case Email
Resolved in Pega Version 8.3.5
Cross-site scripting updates have been added to rules handling linked email correspondence.
INC-143320 · Issue 602281
Support added for email addresses with hyphen in domain name
Resolved in Pega Version 8.3.5
When attempting to enter a email with a hyphen '-' in the domain part of an email ID ([email protected]), the reply button was getting disabled. This was caused by the regex validation implemented in the "pzValidateEmailAddress" (Work-Channel-Triage-Email) standard activity not covering all the possible cases. To resolve this, regex has been changed to instead use a platform-provided rule to ValidateEmailAddress.
INC-146030 · Issue 602605
Added queue process tracer cleanup on node restart
Resolved in Pega Version 8.3.5
If a node restart occurred while a queue process trace was in progress, some entries in the tracer distributed map were not cleared properly and a subsequent tracer failure was encountered indicating a current trace by a requestor on same operator Id was already running. This has been resolved by clearing the tracer distributed map on node startup for stale entries associated with this node.
INC-139802 · Issue 594033
Extra logging and more resiliency for cleanup daemons
Resolved in Pega Version 8.3.5
Null pointer exceptions thrown by daemon threads that clean requestors and handle agent changes can result in a high number inactive requestors. Additional logging has been out into place to help capture information to identify the offending data, and master daemons for requestors and for new agents have been made more resilient to any Null pointer exception thrown by the diagnostics code so they do not stop their work.
INC-142629 · Issue 594555
Resolved alert from disabled job scheduler
Resolved in Pega Version 8.3.5
An urgent event alert was seen for scheduler which was disabled in production. This was traced to null pointer exceptions originating in the JobSchedulerLifeCycleManagerImpl call, and has been resolved by fixing a potential null dereference. Additional logging has also been introduced.
INC-122112 · Issue 599794
Updated SLA table clearance
Resolved in Pega Version 8.3.5
After cases were resolved, SLA entries were not getting cleared from the SLA table. This caused the SLA table to have a huge number of Overall SLA and PendFlow details present for cases that were resolved or moved to the next state, which impacted case processing via SLA Agent. This was traced to SLA queue-items not being removed by delete-deferred as expected, and has been resolved by invalidating the deferred operations and scheduling item removal.
INC-136817 · Issue 596489
Added database query optimization and cache invalidation logging
Resolved in Pega Version 8.3.5
Web nodes were going down during deployment due to failed health checks. This was traced to queries firing even when there was no rule change, and was due to unnecessary cache invalidations. An update has been made which will optimize and analyze declarative database queries and capture diagnostic details on any invalidation of the declarative reference information cache.
INC-135065 · Issue 598718
Added database query optimization and cache invalidation logging
Resolved in Pega Version 8.3.5
Web nodes were going down during deployment due to failed health checks. This was traced to queries firing even when there was no rule change, and was due to unnecessary cache invalidations. An update has been made which will optimize and analyze declarative database queries and capture diagnostic details on any invalidation of the declarative reference information cache.