Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-B65922 · Issue 314665

Corrected Property type validation in Complex Question

Resolved in Pega Version 7.3.1

While creating a Complex Question with Property type Value list and referring an embedded property of type text in the Value list field, the validation message was not shown and system allowed the Complex Question to be saved successfully. Referring a top level property of type text (.ResponseText) showed the validation message (.ResponseText is not a valid Value List), but referring an embedded property type of text (.SurveyResponses(CEP).ResponseText) did not show the validation message. This was caused by missing handling, and has been corrected by modifying the ValidateSurveyEmbedPropertyMapping activity to check the last property mode for valuelist type.

SR-B74689 · Issue 323378

Marketing data flow run made more robust

Resolved in Pega Version 7.3.1

After upgrade, it was observed that Pega Marketing Campaigns were failing if there were no customers in the Audience configured on the Campaign, generating the error message "The run failed, because it exceeds the maximum number of failed records, which is currently set to 0". The cause of this was executing a distributed data flow with a database as primary source on an empty table, leading the run to fail as a table without any partition was considered in the handling. The database dataset has now been updated to differentiate the case when there's no partition available from the case when there's a single partition for every record, ensuring the DB data set now returns 'all' records when there is no partition key defined, and the data flow handles the no values for partitions in a more robust way.

SR-B65908 · Issue 314482

Serialization fixed for multi-node pre-activity dataflow

Resolved in Pega Version 7.3.1

Attempting to trigger a dataflow run with pre-activity configured to run on every node was failing with a serialization exception. This was caused by the task being distributed across the cluster having a member variable that was not serializable; this has been fixed.

SR-B56530 · Issue 312902

Reworked destination assumptions for child dataflows

Resolved in Pega Version 7.3.1

When activating a Real time data flow run containing a Stream dataset as input which was then output to two child dataflows containing different event strategies, an IllegalArgumentException error appeared. This was traced to the pzDataFlowContainsEventStrategy activity assuming that the last shape had "Destination" in the ID. This has been fixed by properly setting the KVS type: the DataFlowRunConfig.getKeyValueStoreType() will not return NONE but will default instead, and the pzDataFlowContainsEventStrategy now Iterates through all subflows and fixed secondary destination name.

SR-B41880 · Issue 300996

Broken-Process SLA update API changed

Resolved in Pega Version 7.3.1

When an SLA update on a work object occurred and the current SLA was in Broken-Process Status, the action failed with the error "The Flow Action post-processing activity ActionChangeAssignmentSLAProps failed: Instance of class Queue not found". This was an issue where dequeuing the SLA entry item to update it with new time caused a status conflict with the blob. To avoid this, the activity ActionChangeAssignmentSLAProps has been updated to use the API updateDeferred(page,repairBroken) which accepts a Boolean if it has to repair a broken item. Setting the repairBroken flag to 'true' will bypass the call to dequeue.

SR-B50202 · Issue 308172

Pre- and Post-processing modified to support customized circumstanced FA

Resolved in Pega Version 7.3.1

A customized out-of-the-box Flow Action called "CheckIn" was created by modifying a circumstanced version with property .pxObjClass = Rule-Admin-Product. For any Product rule, attempting checkin called this customized Flow Action as expected. However, the pre-processing activity and post-processing activity added in the circumstanced Flow Action "CheckIn" were not invoked at all; instead, the pre-processing activity and post-processing activity in the base Flow Action "CheckIn" were triggered. This was due to circumstancing not working when used with the doAction() method because it does not reset the primary page when it invokes a rule. It passes a step page for use by the rule. In order to support this customization, the function will call to tools.doActivity() with the same arguments instead of doAction(), which will force the engine to push myWorkPage as the new primary page for the duration of the call (and then pop it after the call completes). This should provide the correct context for the circumstancing to call the circumstanced purpose code.

SR-B63171 · Issue 315061

Pre- and Post-processing modified to support customized circumstanced FA

Resolved in Pega Version 7.3.1

A customized out-of-the-box Flow Action called "CheckIn" was created by modifying a circumstanced version with property .pxObjClass = Rule-Admin-Product. For any Product rule, attempting checkin called this customized Flow Action as expected. However, the pre-processing activity and post-processing activity added in the circumstanced Flow Action "CheckIn" were not invoked at all; instead, the pre-processing activity and post-processing activity in the base Flow Action "CheckIn" were triggered. This was due to circumstancing not working when used with the doAction() method because it does not reset the primary page when it invokes a rule. It passes a step page for use by the rule. In order to support this customization, the function will call to tools.doActivity() with the same arguments instead of doAction(), which will force the engine to push myWorkPage as the new primary page for the duration of the call (and then pop it after the call completes). This should provide the correct context for the circumstancing to call the circumstanced purpose code.

SR-B65755 · Issue 314416

Broken-Process SLA update API changed

Resolved in Pega Version 7.3.1

When an SLA update on a work object occurred and the current SLA was in Broken-Process Status, the action failed with the error "The Flow Action post-processing activity ActionChangeAssignmentSLAProps failed: Instance of class Queue not found". This was an issue where dequeuing the SLA entry item to update it with new time caused a status conflict with the blob. To avoid this, the activity ActionChangeAssignmentSLAProps has been updated to use the API updateDeferred(page,repairBroken) which accepts a Boolean if it has to repair a broken item. Setting the repairBroken flag to 'true' will bypass the call to dequeue.

SR-B47122 · Issue 308714

Fixed null-pointer exception for adding file to social media

Resolved in Pega Version 7.3.1

An null-pointer exception caused failure when adding a file to social media. This was traced to a missing null check in the function isRegisteredOnBeforeSubmit in the pzpega_social.js file, and has bene fixed.

SR-B53145 · Issue 317256

Back button on Survey screen works with validation

Resolved in Pega Version 7.3.1

If a Survey screen that validates a question failed that validation, the proper error was generated when the criteria did not match. However, clicking the 'Back' button on the screen caused the validation message to disappear while remaining on the current screen and not returning to the previous screen. This was due to a faulty IF condition in the setValue in SurveyAccessMethodBodyQuestion function, and has been fixed.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us