SR-D84880 · Issue 546891
Null check added to resolve addmapcasetomap error
Resolved in Pega Version 8.5
Using a createcase flow shape to create child cases by looping on a page list on the parent case resulted in pzaddmapcasetomap throwing an exception related to the activity pzLoadCaseHierarchyWrapper in step 5. This was traced to a page being removed after the list of pages was received in findPageByHandle, and has been resolved by adding a null check.
SR-D78531 · Issue 542001
Encoding added for special characters in JFROG filenames
Resolved in Pega Version 8.5
A blank screen or the error "Unable to get the file from Repository" appeared when attempting to attach a file from JFROG Repository if the file name contained special characters. This has been resolved by modifying the artificatory URL generation to properly encode special characters during file download.
SR-D67142 · Issue 548642
Enhanced CMIS connector logging
Resolved in Pega Version 8.5
Additional diagnostic logging has been added to enhance investigating CMIS connector health.
INC-129171 · Issue 566576
Field added to configure jFrog artifactory context root
Resolved in Pega Version 8.5
After configuring a JFrog repository rule and successfully testing the connection (from the rule configuration page), attempting to browse the remote repository from the "File Storage" landing page did not work. Investigation showed that ArtifactoryStorage.java was automatically appending "/artifactory" to the host name of any artifactory repo instance, causing a mismatch with the configured URL. There was a workaround of configuring the hostname with a context root, but this issue has been resolved with an additional ruleform field to specify the context root. Leaving this field blank will create the url using strictly what is contained within the host name field, while populating it will construct the url as follows: url + contextRoot + "/artifactory" This field will default to "/artifactory" to help preserve backwards compatibility.
INC-118926 · Issue 563807
ArtifactoryStorage URL construction with port updated
Resolved in Pega Version 8.5
After configuring a repository as a JFROG artifactory with a ruleform that provided a URL / port number and repository name, test connectivity worked as expected, but deploying the codeset using pipeline or importing the codeset using the import functionality generated the error "Unable to construct artifactory url due to invalid file path". The root cause of the issue was traced to the ArtifactoryStorage java class, which did not accept the port number in the format provided due to changes in the API. If there was no portNumber in the URL, the issue did not occur. To resolve this, the constructor has been changed to properly build the URI per https://docs.oracle.com/javase/8/docs/api/java/net/URI.html.
SR-D81673 · Issue 546396
ClipboardToJSON Serializer enhanced
Resolved in Pega Version 8.5
After creating a JSON data transform with the top level structure set to Object and a step that mapped a Pagelist in clipboard to an Array of Objects in JSON, calling the data transform in Serialize mode resulted in a JSON mapping exception. This was a missed usecase for using the JSON serializer with nested pagelists in page, and has been resolved by adding pagegroup support for data transform serialization and skipping pagegroup serialization when automapped.
INC-121359 · Issue 571025
Resolved sync error for offline workorder
Resolved in Pega Version 8.5
After logging on to the mobile app and then switching to off-line mode before opening a workorder from the worklist and processing the full workorder from end to end in offline mode, reconnecting resulted in the work order being moved to the [email protected] work basket with “Sync-Failed” status. Investigation showed that this was a caused by the DateTime properties being an empty string or null despite being created with a valid string. This was traced to the datetime conversion handling, and has been resolved.
SR-D88376 · Issue 548335
SQL query handling added for case-sensitive databases
Resolved in Pega Version 8.5
An Email Listener in RUNNING state was not picking up the emails as expected. This was traced to the column names (pr_log_service_email) being defined in lower case for native SQL queries: since MS SQL server db is case sensitive, it was not able to detect these column names and therefore failed to save the message stub. This has been resolved by adding the necessary handling.
SR-D94019 · Issue 553784
Alerting features added for Listeners
Resolved in Pega Version 8.5
An enhancement has been added for Email Listener alerts. At the end of each listener's processing cycle, the system will determine the average processing time per message, the total processing time of the listener, the total unread messages count, and total number of messages processed. In each AESRemote agent run, this data will be published to the PDC, where it will be analyzed and any necessary alerts raised.
SR-D82490 · Issue 547365
Invoke Connect-SAP method of IDoc type repaired
Resolved in Pega Version 8.5
Attempting to implement SAP connection via IDoc type connector failed and an empty error message was shown. This has been resolved with modifications to the SAP Connector functionality.