Basic enrichment of the original document

In basic enrichment, the values of primitive types, leaf elements, from the patch document are identified using path expressions. The place in input document, where each value should be inserted is also identified using path expression. The enriched document is then constructed and sent as output to the next step. Output document is enriched input document, that means that Input and Output documents must have the same schema.

BOD or JSON Conventional document types are supported in Basic enrichment. You can use different document types for Patch and Input (Output). For example Patch document BOD and Input (Output) document JSON Conventional.

All message headers from source document are persisted during the enrich process. Only new Message Id is created for the Output document.

  1. Click Connect > Data Flows.
    A list of existing data flows is displayed.
  2. Select the document flow where the filter must be added.
  3. Click Details to open the document flow modeler.
  4. Add a Merge activity to the flow.
  5. Ensure that you select a single document in the document selection for delivery from preceding activity.
  6. Add an activity or multiple activities to the Merge component.

    You can add one or more activities in the top branch. These activities can use API CP – Trigger, Mapper, Scripting, Merge.

    You cannot add any activities in the bottom branch.

    Document selection after merge activity is read only. The document is automatically populated based on the Merge configuration.

  7. Click the Properties tab.
  8. Specify an activity name.
  9. Optionally, specify an activity description.
  10. Select the Basic enrichment of the original document Merge type.