INC-127804 · Issue 566400
DASS switch added for use with older Connect Rest passing encoded inputs
Resolved in Pega Version 8.4.2
As of Pega 8.2, an EmbedURL configuration in the REST connector was made available to provide flexibility to choose URL-encoding on an as-needed basis. In order to support connectors created prior to Pega 8.2, a configuration has been added to support usecases that pass encoded inputs to the connector execution. This is available by way of a connect/DisablePathDecoding DASS switch in the REST connector resource path parameters handling.
INC-128213 · Issue 563896
AWS S3 client SDK upgraded
Resolved in Pega Version 8.4.2
The com.amazonaws group has been updated to version 1.11.740 .
INC-129171 · Issue 566577
Field added to configure jFrog artifactory context root
Resolved in Pega Version 8.4.2
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-129400 · Issue 567403
Data page form displaying activity parameters from 'when' rules
Resolved in Pega Version 8.4.2
While displaying the parameters list for source activity in data page rule form, an icon was displayed. This was traced to the visibility condition being an expression but mentioned as a 'when' rule, causing the parameter dialog to not load. This has been resolved by updating the pzActivityParamList activity to change the visibility condition as expression from a 'when' rule.
INC-130176 · Issue 576485
Improved Pagelist size cache cleanup
Resolved in Pega Version 8.4.2
After converting the XML content returned from the end user into the clipboard page using the ParseXML rule and post conversion, it was not possible to remove all the records from the specific page list and then keep a single record in it. This was caused by the Pagelist size cache not being properly cleared on prDelete, which had the downstream effect of the parse XML rule not properly removing the pagelist. To resolve this, the code has been updated to ensure that when removing a pageList property, its size is removed from the size-specific cache as well.
INC-132531 · Issue 572826
Corrected REST resource parameter mapping
Resolved in Pega Version 8.4.2
After upgrading, the PUT rest service was not working correctly. This was traced to a handling issue in the value calculation for a new variable(offset) recently introduced to keep track of next resource parameter in order to replace it with the runtime token and collect resource parameters and their respective runtime values. This has been resolved by updating the system to recalculate the value of offset as soon as the design time resource parameter token is replaced with the runtime token.
INC-134171 · Issue 576432
Enhancements added to S3 repository implementation
Resolved in Pega Version 8.4.2
The following changes have been made to avoid redundant/unnecessary S3 SDK calls to look-up metadata for files/folders related to integrated S3 Repository API implementation:1) Provided storage/AWSSDK/enableSDKMetrics DASS to enable AWS SDK metrics for S3 repositories system-wide to troubleshoot performance issues 2) Added timers for Pega platform repository APIs. To see these timers in Pega application log, set log level to WARN for the log category pxIntegration.Repository.S3 and set log level to DEBUG for the logger com.amazonaws.latency 3) Optimized FileS3Adapter.getMetadata() by avoiding object-metadata lookup for directories and caching rootpath directory metadata for 5 mins 4) Handled exceptions while uploading file to S3 bucket and convey appropriate error message to RepositoryManager.createFile() API consumer 5) Refined DEBUG logging and introduced new loggers to emit stacktraces 6) Enhanced RepositoryManager.initCache() and FileStorageManager.registerStorageClasses() to maintain non-overridable repositories (that are initialized based on DASS/DNode settings on node start-up) and to prohibit overriding the same.
INC-96275 · Issue 553404
Attachment Migration tool updated for improved node crash handling
Resolved in Pega Version 8.4.2
During attachment migration from PegaDB to the S3 repository, a stream node crashed and left queue items in the queue. When the node restarted, these items were migrated successfully to S3. However, a manual restart of the attachment migration tool then ended up duplicating the items already successfully migrated. As part of handling the duplicate attachments, files with 0 bytes were created in S3 and the zero byte link was updated to the Data-WorkAttach-File instance. In order to handle this scenario, an enhancement has been added that will skip migrating attachments already migrated to repository or those having an empty attachment name.
SR-D36826 · Issue 550272
LastAccessTime returned for MDB listener
Resolved in Pega Version 8.4.2
The lastAccess time for the JMS listener was not being updated. Investigation showed that lastAccessTime was correctly updated whenever isStopping() was called, but isStopping() was not called for MDB listeners because the MDB listeners' state is managed by the app server. This caused accessTime to be empty. To resolve this, ListenerStateImpl has been modified to return mRequestTime as the lastAccessTime if the listener is of type MDB.
SR-D64558 · Issue 527678
AttachmentContent supports S3 storage
Resolved in Pega Version 8.4.2
Using a D_AttachmentContent data page to display the contents of an attachment by way of the pyGetAttachmentContent activity worked when using the Pega database for storage, but generated an error stating CMIS access was disabled after switching to S3 storage. This was traced to restrictions on Link-Attachment pages in Step 2, Line 64 of pyGetAttachmentContent to enable attachment stream retrieval from web storage and repositories by D_AttachmentContent, which has now been removed. In addition, pyGetAttachmentContent has been updated to behave the same whether a Link-Attachment page or Data-WorkAttach page is provided when populateAttachStream is set to false, and the rule documentation (description/usage) has been updated accordingly.