Skip to content

Martini Workflows Map Node

Overview

Map Nodes are essential components in Martini workflows for setting and managing property values. They provide a streamlined approach to declare new properties and assign values using either map lines or set expressions within your workflow automation.

Map Nodes in workflows function similarly to Map Steps in services, allowing you to transform and manipulate data as it flows through your workflow automation sequence.

When to Use This

Use Map Nodes when you need to:

  • Assign received values to new properties within the workflow
  • Transform data between workflow steps
  • Set static values or calculated results
  • Combine multiple inputs into a single output
  • Format data before sending it to external services

Prerequisites

Adding Map Nodes to Workflows

Getting Started

To add a Map Node to your workflow:

  1. Navigate to your Martini Package and open your workflow
  2. Click the Add Node button in the toolbar on the top left of the editor
  3. Select Map from the available node types
  4. Drag the Map Node to your desired position in the workflow
  5. Connect it to other nodes using workflow edges

Expected result: A Map Node appears in your workflow where you can configure property mappings and transformations.

Properties

Map Nodes work with the same property concepts described in Understanding Properties In Data Mapping.

Properties are the fundamental building blocks that let you:

  • Store information temporarily as it moves through your workflow
  • Pass data between different workflow steps
  • Transform information from one format to another
  • Reference data by name throughout your automation

For complete details on property concepts, types, and usage, see the Properties section in the Data Mapping Guide.

Map Panel

The Map Panel uses Martini's standard Data Mapper Panel with the Simple Mapper Layout to transform data within your workflow.

Getting Started

  1. Click the expand icon on your Map Node to open the Map Panel
  2. The panel appears in the lower half of the Workflow Designer

Expected result: The Data Mapper Panel opens showing your current workflow properties with a simple input-to-output layout.

Data Mapper Panel Layout for Map Nodes

Map Nodes use the Simple Mapper Layout as described in the Data Mapping Guide:

  • Input Panel (left): Shows workflow properties available as data sources
  • Output Panel (right): Shows workflow properties where you can send transformed data
1
2
3
4
5
6
                 /*** Map Panel Layout ***/              
|   Input Panel      | Mapping Lines |   Output Panel     |
|--------------------|---------------|--------------------|
| [workflowInput1]   |   ------->    | [workflowOutput1]  |
| [workflowInput2]   |   ------->    | [workflowOutput2]  |
| [previousNodeOut]  |   ------->    | [newProperty1]     |

This streamlined layout makes Map Nodes perfect for straightforward data transformation within workflows.

For complete details on using the Data Mapper Panel, including creating map lines, set expressions, and property management, see the Data Mapping Guide.

Map Lines

Map lines work exactly as described in the Data Mapping Guide. For Map Nodes specifically:

  1. Open the Data Mapper Panel on your Map Node
  2. Create map lines between input and output properties

For complete map line creation methods, including drag-and-drop and right-click shortcuts, see Working with Map Lines.

Execution Order and Priorities (Map Nodes Only)

While Map Lines execute in the order you created the properties by default, Map Nodes support custom execution order using priorities to ensure correct execution, especially in workflows with more than 10 mapping lines:

  • Lower numbers run first (priority 1 executes before priority 2)
  • Setting priorities: Select a map line, then modify the priority in the Configuration view on the right

Why priorities matter: In workflows with many mappings (10+), execution order issues can go unnoticed during development but cause runtime errors in production.

Example: E-commerce shipping calculation where each map line depends on values calculated by previous map lines: 

1
2
3
Priority 1: baseShippingRate = itemWeight * zoneMultiplier
Priority 2: tierDiscount = baseShippingRate * discountPercentage  (depends on Priority 1 result)
Priority 3: finalShippingCost = baseShippingRate - tierDiscount   (depends on Priority 1 & 2 results)

Without priorities: Calculations might execute randomly, causing tierDiscount to use null/incorrect baseShippingRate values.

With priorities: Each calculation ensures it uses properly computed values from previous steps, preventing silent calculation errors in complex workflows.

This is critical for financial calculations, data validation workflows, and report generation where incorrect execution order leads to wrong results.

Set Expressions

Map Nodes support the full range of set expressions described in Assigning Dynamic Values to Properties with Set Expressions. This allows you to:

  • Transform workflow data with custom calculations
  • Set static configuration values
  • Format data for subsequent workflow nodes

For complete details on creating and using set expressions, including examples and best practices, see the Set Expressions section in the Data Mapping Guide.

Troubleshooting

Problem Detection Cause Fix Affected Versions
Map line not working Property not updated in workflow Type mismatch between properties Verify source and target property types match All versions
Set expression error Runtime exception during execution Syntax error in code Check expression syntax and property references All versions
Property not available Missing in Map Panel view Property not declared or out of scope Declare property or check workflow scope All versions
Priority conflicts Unexpected execution order Multiple items with same priority Assign unique priorities or verify execution sequence All versions

Helpful Resources