MacroHealth Internal

Stage For Bucket

Stages a bucket trigger. Should contain a file identifier.

Widget
Stage_For_Bucket.png
Configuration
Stage_For_Bucket_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 StageForBucket.

    • bucket-id: The ID of the bucket to add to the Context Document. This is an arbitrary String value.

    • document-names: A comma separated list of Context Document names to add to the bucket. These are arbitrary String values. (E.g., myDoc1,myDoc2,myDoc3)

      Note

      When multiple documents are added to a bucket they will be sourced from the bucket in the same context.

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

    NotesTab.jpg

  3. Click Save.

    StageForBucketSave.png

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

    StageForBucketGC.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.

A mechanism for transferring runtime documents from exactly one producer to a consumer in another transaction

A field in json a document that contains all the information the is saved while the file is moving through the flow and that serves to make decisions at certain stages of that flow.

A field in json a document that contains all the information the is saved while the file is moving through the flow and that serves to make decisions at certain stages of that flow.

A mechanism for transferring runtime documents from exactly one producer to a consumer in another transaction