MacroHealth Internal

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.

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

type: The only value available at this time is ShovelMappingSpec. When specified to ShovelMappingSpec, the mappings that will be defined by a Shovel Expression.

Mappings example:

[
  {
    "name": "Test",
    "mapping": {
      "loop": "DONT CARE",
      "path": "context.lookupFields.data.mh-lookup-isSubscriber",
      "value": "getElemAt(getElemAt(readField(<builtin:document/primary|builtin:key/data/segments|builtin:array_filter_by_key/2000|builtin:key/2000|builtin:array_filter_by_key/INS01|builtin:key/INS01/value>),0),0)",
      "element": "EMPTY",
      "segment": "EMPTY"
    }
  }
]

isolateExpressions: true/false to determine whether each mapping expression is isolated from the others, or if the output of A becomes the input of B, and so on, which yields a single copy with all the remaps applied. Defaults to true to preserve existing behaviour.

mappings: A list of mapping rules that contains shovel expressions to read/write values from/to the runtime context.

expressionResultsContext: String representing the output context key to store the result of the mapping operation in. This has always existed under the hood as a hardcoded value, but now can be set to avoid collisions. Note that when isolateExpressions is true, this will not appear in the output context, but it should still be set to a unique value for each instance of the remap operation in a given flow, otherwise there is a risk of removing data that’s intended for later use.

inputContectPath: String representing the input context path (e.g., foo.bar) to treat as the “root” for the purposes of this remap operation. An empty string means we will use the whole context, which was the original behaviour. This combines with expressionResultsContext to allow us to have multiple remap operations that can use each other’s output as their input, similar to how isolateExpressions = false does within a single operation.