What is the use of ProcessSuppressions DataFlow?

General
, , , , ,
1

We have recently upgraded our CDH version from PEGA 8.6 to PEGA 8.8. Can someone help me with the below Queries?

  1. I couldn’t see any proper reference for “ProcessSuppressions” dataflow but the data flow is available in “PegaMKT-Engine:08-08-01” & “PegaMKT-Engine:08-06-02”. Could someone help me with the use case or where it is referred in the application code base? I am posting this query as “ProcessSuppressions” & “ProcessInteractionHistory - Generated After saving the context dictionary” dataflows remains identical.
  2. In PEGA 8.8, The ID value is “ProcessSuppressions” & label value is “Process Interaction History”. Is this a human error while updating the DataFlow OR label value is referred in internal code base/Engine API call?

Attached the screenshot document for Reference (Document Name: Screenshot.docx)

Screenshot.docx (146 KB)

2

@mannp - Could you/someone from your team can help me with this Query?

3

@Neminath

  1. ProcessSuppressions(Label: Process Interaction History) is what we ship OOTB. During CDH update/ Context dictionary save, We regenerate it using the primary context key, with the name of ProcessInteractionHistory(Label: Process Interaction History) from CDH 8.7 onwards. “ProcessInteractionHistory(Label: Process Interaction History)” DF is being referred from DF_ProcessResponse and is responsible for writing an entry into Interaction History and Action Insights (which in turn is used for suppressing an offer) based on defined contact policy.
  2. As mentioned above, It’s not a human error. It’s by design.

Hope it helps.