Step Type: Call Procedure

The Call Procedure step triggers the execution of another procedure within the same project. This enables modular workflow design where common operations are defined once and reused across multiple procedures.

When to Use

• To reuse a common migration workflow from multiple parent procedures
• To break a complex migration into smaller, manageable procedures
• To conditionally execute a set of steps based on prior results
• To organize related migration logic into logical units

Configuration

Setting	Description
Target Procedure	The procedure to execute (must be in the same project)
Input Variables	Override the target procedure’s default input variable values
Output Variable	Variable to capture the result of the called procedure (optional)

How It Works

1. The step identifies the target procedure within the current project
2. If input variable overrides are configured, they replace the target procedure’s defaults
3. The target procedure executes all of its steps sequentially
4. Any result from the target procedure is stored in the configured output variable
5. Execution returns to the calling procedure and continues with the next step

Input Variable Overrides

When calling a procedure, you can override its default input variables:

Target procedure has: IncidentNumber = "INC0010001"
Override with:        IncidentNumber = "INC0010042"

This allows the same procedure to be called with different parameters for different contexts.

Example

A project might have:

• Procedure A: “Migrate Incidents” — handles incident record migration
• Procedure B: “Full Migration” — orchestrates the complete migration: 1. Assign Variables step (set up configuration) 2. Call Procedure → “Migrate Incidents” (with specific input variables) 3. Additional steps for journal entries, attachments, etc.