SR-C84135 · Issue 424531
Metadatatree updated to be function-scoped in UI to resolve custom tab control display issue
Resolved in Pega Version 8.2.1
When switching rapidly between two custom tabs, especially clicking in and then clicking away before the busy icon could be displayed, the section containing the tab controls was intermittently refusing to display. Refreshing the browser or clicking on the Pega button made the section visible again. This was traced to the template "metadatatree" getting overlapped with subsequent template processing due to a timing issue as "metadatatree" was being maintained in the global window object. To resolve this, "metadatatree" has been updated to be function-scoped in renderUI to avoid timing issues.
SR-127806 · Issue 195855
Sort by ID enhanced to handle custom ID formatting
Resolved in Pega Version 7.1.8
Sort by ID was not working correctly for workbasket/worklist if the workID was in the format String-Number-Number and not in expected format of either String-Number or String-Number-String. The Pega-RULES:compareWorkIDs function responsible for sorting the workID assumed the ID would be in this format because it used pxRefObjectInsName - an internal property that could not be overridden. However, it was possible to create another property in the "Assign-" class of a custom rule set that could be updated with the value of pxRefObjectInsName by iterating it through the list, and then it could be configured in a grid as sortable row which could further be sorted through a custom sort function. An enhancement has been added to the compareWorkIDs function to handle IDs in the String-Number-Number format with additional handling for 2 part vs. 3 part IDs.
SR-121016 · Issue 179993
JMS handling enhanced for complex custom environments
Resolved in Pega Version 7.1.8
When a JMS message is created, a temporary JMS response queue is also created on the fly. The JMS response queue has a timeout parameter associated. After PRPC has consumed a message from the destination, it retrieves the response parameters from the message header and posts a JMS message to the temporary response queue to complete the cycle. In some complex custom environments, PRPC was not able to send a response message before the response queue timed out and an error was generated. In order to handle these situations, the JMS Listener has been modified to always close MDB response connection before continuing.
SR-121686 · Issue 183607
Email Listener timeout tuned for EAR deployments
Resolved in Pega Version 7.1.8
When the email listener encountered an error in installations with EAR deployments, it stopped processing emails until the listener was restarted manually. This was caused by the Timer variable being static in EAR deployments with no logic available to reset it, so it continued to grow over time and could result in sleep times of days. Logic has now been added to reset the timer. The default sleep time has also been set to increase 30 seconds each time an error is encountered to a max of 90 seconds (sleep times are 5 , 30 , 60, 90 seconds) at which point it will reset.
SR-127809 · Issue 192785
Stage processing refined for casetype launch
Resolved in Pega Version 7.1.8
If SLA was configured for the case type (case wide SLA) it caused the exception "Reconcile inconsistency in stage processing" once the SLA was triggered. This error also occurred when the flow was run on a modal dialog. This was caused by the pxStageFlowID not being set on the pxFlow of the custom flow being called from the SLA. Any flow started backdoor -- via activity, SLA, subprocess, etc -- should not be considered part of the stage processing, and the code has been updated to ensure flows that are not started in the context of the casetype or stage are no longer logged as part of stage history and do not go into stage flow end processing.
SR-127820 · Issue 192785
Stage processing refined for casetype launch
Resolved in Pega Version 7.1.8
If SLA was configured for the case type (case wide SLA) it caused the exception "Reconcile inconsistency in stage processing" once the SLA was triggered. This error also occurred when the flow was run on a modal dialog. This was caused by the pxStageFlowID not being set on the pxFlow of the custom flow being called from the SLA. Any flow started backdoor -- via activity, SLA, subprocess, etc -- should not be considered part of the stage processing, and the code has been updated to ensure flows that are not started in the context of the casetype or stage are no longer logged as part of stage history and do not go into stage flow end processing.
SR-123478 · Issue 186770
Defined order of execution for FinishAssignment and pyDeleteDocumentPg
Resolved in Pega Version 7.1.8
In an application in which a page-level message was to be output if a certain field was left blank, sometimes the page-level message did not display when the condition was met. This problem was due to the random order in which pyDeleteDocumentPg and FinishAssignment were issued by the Browser. Both are issued simultaneously to within the same 1000th of a second (according to Fiddler), but sometimes one is issued first, sometimes the other is issued first. Whether or not the function succeeded depended on whether or not pyDeleteDocumentPg was processed first by the server. In order to ensure the proper behavior, the submit and harnessOnBeforeUnload methods defined in pega.u.d object have been modified to send the finishAssignment request after processing the pzDeleteDocumentPg request.
SR-119297 · Issue 183495
Dynamic container enhanced for harness sections
Resolved in Pega Version 7.1.8
In some situations, tab visibility conditions were not functioning as expected. For example, in a portal with a harness that has 2 sections, the click of an enable/disable button in the top section was configured to refresh the bottom section as well as call an activity. The bottom section had a tab layout containing harness rules with conditions specified for the tab visibility based on the above "Enable/Disable" button. For the above features, the data model got created when the Dynamic Container was being rendered for the portal's harness, and the data model was updated with the dynamic tabs' meta data. However, the data model was not being created while rendering the harness, and the lower section did not confirm to expectations. To resolve this, the code has been updated to handle the section refresh which has a Dynamic Container.