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-B51449 · Issue 308503
Property Record localization added for Pega Marketing
Resolved in Pega Version 7.3.1
Localization has been added for Property Record Configuration text in the Pega Marketing application.
SR-B51450 · Issue 308504
Property Record localization added for Pega Marketing
Resolved in Pega Version 7.3.1
Localization has been added for Property Record Configuration text in the Pega Marketing application.
SR-B51450 · Issue 313658
Property Record localization added for Pega Marketing
Resolved in Pega Version 7.3.1
Localization has been added for Property Record Configuration text in the Pega Marketing application.
SR-B51450 · Issue 313738
Property Record localization added for Pega Marketing
Resolved in Pega Version 7.3.1
Localization has been added for Property Record Configuration text in the Pega Marketing application.
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-B43400 · Issue 307258
Localization added for field value used in 'Enter a Short Description' validation message
Resolved in Pega Version 7.3.1
Localization was failing for the 'Enter a Short Description' validation message when using a Field Value due to the message rule containing spaces. To fix this, a new message rule has been created without spaces in the same ruleset so that it is available for override use in the ruleset.