SR-D42243 · Issue 525773
Added handling for offline mobile attachments using PRFiles and Repositories
Resolved in Pega Version 8.4
Attaching a file on mobile and then immediately clicking on it to open it either did not open the attachment or the attachment opened and then the app stopped working with a "Sync Failed" error. Attachments were not synchronized on the server, and when synchronization was re-tried the attachment was duplicated on attachment list. This was traced to the system being configured to use PRFile API for synchronizing attachments along with Repositories to store attachments; when the processing "commitAttachment" action was processed, it called the Work-.AttachFile activity to finalize attachment upload, but the activity was called without the mandatory attachment InputStream required when using PRFile + Repositories. This has been resolved by ensuring there is a call to Work-.AttachFile with InputStream in cases where PRFiles and Repositories are enabled.
INC-190130 · Issue 678541
Help information updated for using Elastic Search with Report Definition
Resolved in Pega Version 8.7
The support article "Configuring a report definition to run against an Elasticsearch index" has been updated to clarify that the search can pass multiple values with a space in pySearchString as it does OR operation on all the fields, and that filters in the report definition will be used when executing the report directly or when calling the report in the pxRetrieveSearchData activity. https://community.pega.com/knowledgebase/articles/system-administration/85/configuring-report-definition-run-against-elasticsearch-index
SR-D39264 · Issue 518841
Multiple files uploaded using "select file" will be handled asynchronously
Resolved in Pega Version 8.4
In order to resolve an intermittent error when uploading multiple files using the "select file" button, each file will be uploaded asynchronously to avoid overloading the browser threshold.
INC-193485 · Issue 695841
REST authentication settings use fully qualified name for resolution
Resolved in Pega Version 8.8
The application setting used in REST connectors for authentication was resolving to similarly-named rules instead of matching the exact name of the rule. This has been resolved by enhancing pzGetSettingID to use both parts of the fully qualified name (name and category) provided by the pzSettingsORA control when determining which setting from the report to return.
INC-207996 · Issue 709665
Check added for parent case dependency if deferred-save is used
Resolved in Pega Version 8.8
After updating the status of a parent case to "Pending-ChildCaseDependency", the wait shape for the child case that should have been triggered by the status did not work and the child case remained on hold. This was a missed use case for the pxCheckFlowDependencies activity where defer-save operations on Index-AssignDeps class was not considered, and may happen when the Queue Processor is evaluating the dependencies while instances to Index-AssignDeps are not committed yet. To resolve this, code has been added to check the entry of the parent case dependency in deferred-save if its not present in Index-AssignmentDeps table.
SR-D42159 · Issue 508941
Large report pagination should use "Previous and Next only"
Resolved in Pega Version 8.4
Some Report Definitions were getting timed out or facing gateway exceptions, primarily due to high time consumed by the database Queries. Investigation showed the total result count process appeared to stop at the configured pyMaxRecords value as long as it was nonzero. This indicated the issue was related to changes made to fix the inaccurate behavior of the "Last" button in the responsive paginator which included removing logic that set pyMaxRecords to anything other than zero. To resolve this issue, those pagination changes have been reverted. The "Last" button should not be used when the paging mode is set to Numeric: in the case of large reports, the paging option should be set to "Previous and Next only".
SR-D37737 · Issue 509375
Export to Excel can run in the background when called from the filelistener
Resolved in Pega Version 8.4
When calling the pzRDExportWrapper activity from a filelistener and passing reportRunMode as “background” with a given fileLocation parameter, a popup appeared to save the file in the local directory instead of the expected behavior of saving it to the provided location in the background. Investigation showed that ReportExportHandler.java was not checking for the reportRunMode parameter and instead always exporting to the browser for download and then immediately deleting the file. This has been corrected.
SR-D50057 · Issue 521980
Added null check when updating OperatorID activity after passivation
Resolved in Pega Version 8.4
An issue with operators being able to see work outside of their own authorization was traced to an underlying issue with how the sessions were passivated after either inactivity for a long time or closing the browser directly without logging off. Investigation showed the conditions resulted in a null pointer for the operatorpage in the basic flow, and this has been resolved by adding a null check prior to copying the primary page data to the operator ID page as part of updating the operatorID activity.
SR-D52144 · Issue 515673
When no active document is available on login, first document will be marked active
Resolved in Pega Version 8.4
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 524804
Corrected grey area seen when dragging tabbed layout Smartinfo scroll
Resolved in Pega Version 8.4
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.