SR-D82695 · Issue 546540
Correct tenant ID set in execution of SLA Agent
Resolved in Pega Version 8.4.2
An incorrect tenant ID was set in the execution of service level agent, causing the SLA Queue item to fail with the error "You are not authorized to open instance SYSTEM-QUEUE-SERVICELEVEL." This was traced to an incorrect access group which was set in QueueProcessor for a processed item and not restored correctly, and has been resolved by populating the access group on the security tab of the relevant standard agent with the value “PRPC:Agents”.
SR-D85410 · Issue 549570
Improved queue processor tracing
Resolved in Pega Version 8.4.2
After starting to trace the queue processor, the message "waiting up to 1 minute for queue processor, <<Name>> to start processing an item" was displayed as expected, but if the tracer was closed and then there was another attempt to trace the queue processor, the message "Trace request with the current requestor is already registered. Multiple trace requests from same requestor are not allowed." appeared. Research showed that this was related to the implementation around canceling a background task, and has been resolved by adding code to handle the scenario of terminating an on-going trace request on window close and then beginning another trace request with the same requestor.
INC-112001 · Issue 556978
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-118926 · Issue 563808
ArtifactoryStorage URL construction with port updated
Resolved in Pega Version 8.4.2
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 tothe 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.
INC-119725 · Issue 561752
WSDL consumption via XSD corrected
Resolved in Pega Version 8.4.2
When trying to consume a WSDL from a given URL with XSD, the error "Rule evaluation failed : Canceling rule evaluation, Unrecognized type name 'Name'" was generated. The same WSDL was easily consumed in SOAP UI. This was due to a case mismatch. When processing schema files, RuleGeneratorXSD calls XSDUtils.getStringType to retrieve and validate the type of incoming attributes. To do so, XSDUtils compares the type provided against a static list of attribute types, XSDConstants.java. Because XSDConstants.java is hardcoded to match against the lowercase "name" instead of the standard uppercase "Name", the type was not recognized and the error was thrown. While there was a workaround of replacing "xs:Name" with "xs:string" in the local schema files, this has been resolved by updating XSD_TYPE_NAME to equal "Name" in XSDConstants.java.
INC-120223 · Issue 565749
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-121249 · Issue 570419
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-121359 · Issue 571027
Resolved sync error for offline workorder
Resolved in Pega Version 8.4.2
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.
INC-121394 · Issue 561514
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.
INC-121474 · Issue 561064
Handling added for SAP WSDL with names containing unexpected characters
Resolved in Pega Version 8.4.2
When running the Create SAP Integration Wizard and importing SAP WSDL, import failed with the error "The Flow Action post-processing activity pxGenerateRules failed: The reference ORDERS.ORDERS05._-GLB_-OGTORDERS05_04 is not valid. Reason: unexpected character". This was due to the operation name containing the "-" character, and handling has now been added to normalize operation names to match Pega standards.