SR-C79205 · Issue 416399
OnChange event only triggered on date field when value changes
Resolved in Pega Version 8.2
After configuring the onchange event for a date control field with some action, clicking on the Date picker option and selecting the same date triggered the onchange even when the value had not changed. This has been resolved by updating the code to store the previous value and check for a value change before firing the change event.
SR-C73994 · Issue 415479
OnChange event only triggered on date field when value changes
Resolved in Pega Version 8.2
After configuring the onchange event for a date control field with some action, clicking on the Date picker option and selecting the same date triggered the onchange even when the value had not changed. This has been resolved by updating the code to store the previous value and check for a value change before firing the change event.
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.
SR-D54785 · Issue 524802
Corrected grey area seen when dragging tabbed layout Smartinfo scroll
Resolved in Pega Version 8.1.8
When using Show Smartinfo in a tabbed layout group, a grey area was seen in the harness while scrolling. Scrolling up so that Smartinfo was out of view port caused another scroll bar to seen: one scrollbar was attached to the workarea div and the other to the body, and the gray area issue was only reproducible when explicitly dragging the (second) scrollbar attached to the body. To resolve this, if the popup is below the viewport using Smartinfo and the height calculated is negative, then the popup's height will be set to 0px.
SR-C50284 · Issue 390659
Top level activity steps are numbered correctly when child steps exist
Resolved in Pega Version 8.2
Top level activity steps were showing as being numbered incorrectly when child steps existed, but saving the rule or refreshing the rule corrected the numbering. This was caused by CSS that was added to the rule form harness to increment the step number; while expanding a top level node the reset happened and then the counter initialized the value. To address this, the code has been changed from CSS counter to CSS attr which will use the index attribute of the current row. Additional CSS cleanups were also done to remove IE9 and other browser-specific styling that is no longer needed.
SR-C65576 · Issue 405496
Data-WorkAttach-File made available for use of custom pxCreateSystemID
Resolved in Pega Version 8.2
An enhancement has been added to allow storing the pxCreateSystemID from pyWorkPage to Data-WorkAttach-File and Link-Attachment instances which were created on attaching a file. Previously, the Data-WorkAttach-.Default Data transform and Work-.AttachFile both set the pxCreateSystemID property to pxProcess.pxSystemName for Data-WorkAttach-File and Link-Attachment instances respectively. While Data-WorkAttach-.Default is ‘available’ and can be overwritten to set pxCreateSystemID as desired, the Work-.AttachFile was ‘Final’ and it was not possible to overwrite that to set a pxCreateSystemID manually. In order to support this use, extension points have been provided for the pyDefault data transform in the activities Work-.AttachFile and Work-.WorkURL which can be overridden.
SR-C68750 · Issue 402364
PEGA0066 alert sends data needed for MyAlerts use
Resolved in Pega Version 8.2
In order to facilitate the use of products like the MyAlerts application, the following data will be provided to PDC from PEGA0066 alerts to generate proper diagnostics information and propose solutions for issues with mobile client connections:pxClientErrorCode pxDeviceManufacturer pxDeviceModel pxOSName pxOSVersion pxHybridClientVersion pxInstallationId pxSynchronizationId pxSynchronizationTimestamp pxEnd The whitelisted parameters can be seen on the Alert Summary page in PDC.
SR-C68682 · Issue 409608
Layout Groups Accordion Styles modified to use refresh on change
Resolved in Pega Version 8.2
After updating Layout Groups Accordion styles in a skin rule and saving and checking in the rule, re-opening the skin rule showed that the changes had not been saved. Investigation revealed that in accordion format, the font section is being rendered for the "header" and "tabs" of the of layout group but the third tab was not visible to accordion format. To resolve this, pyComponentDetails of Embed-skin-component-layoutGroup has been modified to use on onchange refresh section instead of "Run visibility condition on client".
INC-211248 · Issue 713157
Survey navigation type set for use with complex CB refresh
Resolved in Pega Version 8.8
After upgrade from Pega 7.1 to Pega 8.5, creating a legacy survey used in pxSurveySection with a complex CB question page that contained a refresh option had collapsed tree navigation, the survey name was blank, and duplicate labels were found in picklist questions. To resolve this, an update has been added which will set the navigation type in parameters after a complex CB refresh and skip page copy while upgrading survey work objects.
INC-220893 · Issue 728488
Errors persisted for single case runs using a custom error handler
Resolved in Pega Version 8.8
Single case processing (SingleAccountData) had failed records when opening the SubscriptionData dataset, but it was not possible to see the failed record details for further investigation. Investigation showed that when running a single case run with a custom error handler, errors were persisted as part of the dataflow metrics, but not written to the database. To resolve this, an update has been made to ensure errors are persisted for single case runs configured using a custom error handler.