SR-D45251 · Issue 523815
Harness context will be stored to handle on click executed outside of the Ajax Container
Resolved in Pega Version 8.1.8
An exception was generated in the interaction portal on execution of a post-value action for the on-change event on a text-box in the service case: "Failed to find instance Work-Interaction-Research.EmailBodyRTE of type Rule-HTML-Section". This was traced to a condition where clicking outside of the Ajax Container context to trigger the change caused the Events code to execute the event in the active context when the active context had already been changed by clicking outside of the AC. To avoid this, the system will store the harness context in the event object using pega.ctxmgr.getContextByTarget(target) API. Additional changes were also made to handle the context switching in case of post value when the blur triggers a change in context.
SR-D45848 · Issue 515525
Added toggle to hold radio button value during multiple service case creation
Resolved in Pega Version 8.1.8
When a field was implemented with a radio button control in the service case screen, starting two cases of the same or different case type (with the same property and control) resulted in the selected value not sticking in the first case when selections were made for the second case. This was traced to multiple radio buttons with the same name in the dom for different AJAX containers: as per radio buttons behavior, only one could be selected if they have the same name. To correct this issue, updates have been made to change the name on radio buttons which are inside the hidden AJAX container and toggle the changes when the buttons should be shown.
SR-D46451 · Issue 511711
Resolved signature capture transaction error
Resolved in Pega Version 8.1.8
After configuring a launch modal in flow to capture a signature, trying the submit the flow after capture was resulting in the error "This action is not allowed as it is outside the current transaction." This was traced to the flow in the modal HTML which contained a hidden input for transaction ID, and this ID was not being updated. As this was part of a legacy area, the hidden input transactionID element in pzFlowDetails has been removed.
SR-D47344 · Issue 519892
Single quotes escaped in rich-text editor title field value
Resolved in Pega Version 8.1.8
A JSON parse error was caused by single quotes not being escaped in the rich-text editor title field value. This has been corrected.
SR-D47689 · Issue 520828
EvaluateConditions properly sets context for refresh section
Resolved in Pega Version 8.1.8
Rule Not Found and Unresolved Assembly Errors were seen in production logs after upgrade. Investigation showed that the method context used by pzpega_ui_changetracker.js in "evaluateConditionsOnXThread" was not reset correctly, causing the refresh section response for the Recents List to not be properly updated. This has been resolved by updating the evaluateConditionsOnXThread method to set the proper context after evaluateClientConditions is run.
SR-D49305 · Issue 519365
Tab layout group handling improved
Resolved in Pega Version 8.1.8
A difference in scrolling speeds between left and right arrows and an issue with the cursor correctly being redirected to mandatory fields were traced to errors in the tab layout group handling. The right scrolling issue was due to the calculation for right tab movement being incorrect in certain resolutions with relatively positioned elements, and has been corrected. The cursor redirect was caused by an error in the layoutgroup focus when used inside a screen flow where the first focus goes to the screenflow navigation on load, and has been resolved by adding a try catch for an invalid selector in case of a div error.
SR-D50469 · Issue 519924
Helper text fetches field value fr dropdown
Resolved in Pega Version 8.1.8
A dropdown control configured with a helper text with a field value was not fetching the field value in runtime, but instead displayed the Field Value Name. This was traced to an issue with case sensitivity in getLocalizedValuecall in DLCellTemplate, adn has been resolved by updating pyToolTip to pyTooltip.
SR-D51555 · Issue 516494
Resolved system hang after changing input field value post note
Resolved in Pega Version 8.1.8
After upgrade, a session was hanging in a Non-Member Search Phone interaction after navigating back from "Add or edit attachments" window. The same code worked as expected in the Member Search Phone interaction. Investigation showed that changed values (transaction ID, pzFromFrame) were being sent to the client twice, once in the popup window after attaching the note and again to the parent window. When the changed values were consumed and used in next actions, a mismatch resulted in pzFromFrame. To resolve this, the system has been updated so the Client will not consume the pxThread.pxClientExchange value if pxThread.pxClientFrame is different from what the current tracker is using.
SR-D51601 · Issue 516703
Hover logic updated
Resolved in Pega Version 8.1.8
When using a dropdown in a grid layout configured with a smartInfo to be displayed on Hover, the smart tip was sometimes not displayed when the hover moved from the top to point to the dropdown. If the hover was done quickly, it was displayed. Previously, the hover was calculated only by cursor x, y positions and elements boundaries: to resolve this issue, the logic has been updated to also consider cases where the element is still hovered without meeting these conditions.
SR-D52144 · Issue 515671
When no active document is available on login, first document will be marked active
Resolved in Pega Version 8.1.8
After logging into the user portal, attempting to perform operations like (opening a case/work object, opening reports etc.) caused the browser request to spin or freeze. The only way to recover was to close and re-launch the browser window/session and re-login. This issue occurred when there was an active reportdefinition document before the browser/node crash in the tabless dynamic container(DC) portal. After recovery, the dynamic container did not recreate the report definition document but instead tried to activate the first document in the portal, which in this case was the default harness configured in the Dynamic Container. As it was not yet loaded, exceptions were thrown. To resolve this, when no active document is available, the first document will be marked as the active document.