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-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-125136 · Issue 575999
Topic name prefix support added for Kafka
Resolved in Pega Version 8.4.2
An enhancement has been added to support the use of site-specific standards for the naming of queues. This can be used to add clarification between Kafka Topics created by Pega and those created for internal topics when using a shared Kafka Cluster. This is done using the new setting: <env name=”services/stream/name/pattern” value=”prefix{stream.name}postfix”/> .As an example, if tenant.name is resolved into "myco" and the environment into "prod1", value="{tenant.name}-{environment}-{stream.name}" will result in stream myco-prod1-{stream.name} By default, when stream.provider = EXTERNAL, the default will be “pega-{stream.name}” .
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.
SR-D74376 · Issue 552261
Check added for string vs boolean for pzscan JSON
Resolved in Pega Version 8.4.2
When calling the CloudRemoteMaintenance/Work-/pzscan API, the response JSON had boolean values in the form of String which caused the JSON parsing to fail. The system was using ClipboardProperty.toStringValue() while generating outbound JSON from the clipboard page, which did not correctly interpret a boolean value. To resolve this, a check has been added that will assess the value and invoke ClipboardPage.toBoolean() when needed so that the value is converted as per type before generating the JSON.
SR-D95511 · Issue 557292
Decision table testConsistency updated to include duplicate columns
Resolved in Pega Version 8.4.2
Show Conflicts incorrectly reported unreachable conditions for a decision table and there was a red severe warning ribbon on the top of the rule after saving when in actuality the conditions were unique and the execution was correct, with the runtime execution of each row in the table giving the correct results. This was traced to the use of a property as the column header for multiple columns: testConsistency marked the columns other than the first as duplicates and excluded them from the consistency check. As a result, when a decision table had 3+ rows with a value in the first row and empty values for the rest of the rows and used an operator such as >, all rows starting with the 3rd row became unreachable because the first row covered values > 1 and the second covered the rest, therefore the third was unreachable. To resolve this, the system has been updated to involve all duplicate columns in the consistency check.
SR-D95353 · Issue 557043
Null check and enhanced logging added to Update Existing Application
Resolved in Pega Version 8.4.2
While performing "Update Existing Application" step as part of post upgrade activities, errors were seen about hidden or circumstanced rules relating to "prprivate-exec.jar:?". Investigation indicated that rulesets were being iterated and compared, but it was not clear which ruleset might be causing the issue. The root cause was code that used an integer type in the comparison, leading to a null pointer error when it was null. To resolve this, a check has been added that will assign a value of 0 if the value is null in the comparison, and infoForced logging will be used to tell what caused the null.
INC-120356 · Issue 560225
Class Loader cache values wrapped with WeakReference for improved cleanup
Resolved in Pega Version 8.4.2
Out Of Memory exceptions due to Metaspace were observed on Web tier instances running with a max Metaspace size of 2GB. Investigation showed that in PRClassLoaderDB, mLoaderCache values were wrapped with a SoftReference. To resolve this, the Class Loader cache values will be wrapped with a WeakReference, allowing the cache to free memory when it is no longer needed. JVM options has also been added to switch types of References being used if there is a preference.
INC-131416 · Issue 575453
Class Loader cache values wrapped with WeakReference for improved cleanup
Resolved in Pega Version 8.4.2
Out Of Memory exceptions due to Metaspace were observed on Web tier instances running with a max Metaspace size of 2GB. Investigation showed that in PRClassLoaderDB, mLoaderCache values were wrapped with a SoftReference. To resolve this, the Class Loader cache values will be wrapped with a WeakReference, allowing the cache to free memory when it is no longer needed. JVM options has also been added to switch types of References being used if there is a preference.
SR-D83424 · Issue 552724
Class Loader cache values wrapped with WeakReference for improved cleanup
Resolved in Pega Version 8.4.2
Out Of Memory exceptions due to Metaspace were observed on Web tier instances running with a max Metaspace size of 2GB. Investigation showed that in PRClassLoaderDB, mLoaderCache values were wrapped with a SoftReference. To resolve this, the Class Loader cache values will be wrapped with a WeakReference, allowing the cache to free memory when it is no longer needed. JVM options has also been added to switch types of References being used if there is a preference.