MacroHealth Internal

Merge Documents

Merges all documents into one. Decrements the commit count for the transaction by #document +1.

Widget
Merge_Documents.png
Configuration
Merge_Documents_Config.png

  1. Fill in the following fields:

    • Description: Allows changing the name that appears on the widget. This may be useful to quickly find a particular widget or distinguishing it from other similar shovel operation widgets when building large flows.

      Description.png

    • Shovel Operation: The name of the Shovel Operation.. Pre-configured to MergeDocuments.

    • batchSize: Indicates the maximum number of elements a batch can have.  If no batching is required, this needs to be defined with a value of 0. The termination of the merge process will be determined by what’s defined in the fragment.count runtime attribute.

    • documentName: The name of the document in the incoming runtime context used to merge into the batch. The other documents in the incoming context will be dropped.

    • resultDocumentName: The name of the document in the runtime context where the merged doc will be added, e.i. the name of the new document that will recreated when entities will be merged. This is an arbitrary String value.

  2. If necessary, click the Notes tab and enter any relevant information.

    NotesTab.jpg

  3. Click Save.

    MergeDocsSave.png

  4. The widget will be marked with a green check.

    MergeDocsGC.png
In this section:

A Shovel Operation is the simplest building block that can be used to build flows. Shovel Operations define configuration, inputs and outputs and are combined together in order to build more complex flows.

Single json representation of a document in standard runtime. Documents are contained within a document context. Document also defines a type and associated metadata for the documents.

Single json representation of a document in standard runtime. Documents are contained within a document context. Document also defines a type and associated metadata for the documents.