Description:

The Placeholder step is a Logic-category workflow step that provides a position in a workflow for other steps to pass through.

Unlike workflow steps that perform a specific operation, the Placeholder step has no properties, inputs, or property types defined in its XML configuration. You can use it as a lightweight workflow-design element when a process needs an intermediate step or placeholder in its flow.

The step supports:

• Providing a placeholder in a workflow.
• Allowing workflow flow to pass through the step.
• Creating an intermediate position for workflow design.
• Simplifying workflow structure where no processing configuration is required.
• Providing a location that can be retained as part of the process flow.

Usage:

You can insert the Placeholder step into a workflow when a process needs an intermediate position but no specific processing operation at that point.

A typical workflow pattern is:

Activity A → Placeholder → Activity B

This can be useful when designing, organizing, or maintaining process definitions where a logical position needs to remain in the workflow even though no specific operation is associated with it.

Because the XML defines no properties or returns, don't document the step as performing data transformation, database processing, file processing, or another specific business operation. Its defined purpose is simply to allow other steps to pass through.

Typical Workflow Suggestions:

Provide an Intermediate Workflow Position

Use the Placeholder step to provide a visible intermediate position between two workflow activities.

Example:

Start → Place Holder → Process Request

This makes the intended workflow structure easier to establish while you design the surrounding activities.

Reserve a Position for Future Workflow Development

Use a placeholder when a workflow has a known position where you may add additional processing later.

Example:

Receive Request → Place Holder → Complete Request

The placeholder provides an identifiable position in the process without introducing configuration requirements.

Note: The XML only establishes the step as a placeholder and does not state that it is intended specifically for future replacement. This is a practical workflow-design suggestion rather than a documented implementation requirement.

Simplify a Workflow Flow

Use the step where a workflow requires an intermediate process element, but no step-specific configuration is needed.

Example:

Validate Request → Place Holder → Continue Processing

This can provide a simple visual separation between workflow sections.

Organize Workflow Sections

You can position a Placeholder between logical portions of a process.

Example:

Collect Information → Place Holder → Process Information

This can help establish a recognizable boundary within a larger workflow.

Maintain a Consistent Process Structure

Use the Placeholder when a process design benefits from an intermediate workflow node, even though there is no operation to configure.

Example:

Prepare Data → Place Holder → Generate Output

The step requires no property configuration, making it lightweight compared with processing steps that require inputs or mappings.

Use as a Pass-Through Workflow Element

The defining description specifically identifies the step as one that lets other steps pass through.

Example:

Step A → Place Holder → Step B

This is the most direct use of the step and represents its core documented purpose.

Support Workflow Prototyping

During workflow design, a Placeholder can occupy a position in the process while you develop the surrounding workflow.

Example:

Start → Place Holder → End

Because the step has no properties to configure, you can add it without defining data values or mappings.

Provide a Neutral Process Node

Use the step when a process needs a neutral workflow node rather than a step that performs a business operation.

Example:

Receive → Place Holder → Review

The Placeholder does not introduce a defined business operation between the activities.

Example:

Let’s build and execute the “placeholderDef” example.          

• Create a new process definition called “placeholderDef” and open it in Designer mode.
• Drag the “placeholder, decision, synchronize, and wait” steps to the canvas.
• Connect the dots between the “Start” and other steps, as shown above.
• Select the line between the steps to configure the “Connection Properties”. The default property values are “None, True, False, Error, and Evaluate”. Depending on the step’s purpose, you can configure additional values.
• Click the "placeholder" step to configure its "Required" properties. Name the step, then click Save. Note: The placeHolder steps should have unique names. Click the "AI Predict" button to have Copilot add new process steps that match your process description. 

• Click the "decision" step to configure its "Required" properties. Provide a name for the step and a condition to evaluate. Then click the Save button. Note: Click the "AI Predict" button to have Copilot add new process steps that match your process description. 

• Click the "Wait" step to configure its "Required" properties. Name the step and set the wait time. Then click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• As you can see, given the behavior of the synchronization phase, the workflow will never go through the synchronize step if the pathways from the decision step reach it. Nonetheless, you can meet these requirements using the Placeholder step.
• Save the process definition, create a new instance, and execute it. Render the process instance and click the Placeholder step to view its properties. When the workflow reaches the Placeholder step, the step provides its defined pass-through position in the workflow. The XML does not define any configurable operation, output property, or explicit return value for the step.

Tips:

• Use the Placeholder when a workflow requires a simple pass-through position.
• Give surrounding workflow activities meaningful names so the placeholder's purpose is clear.
• Keep in mind that the Placeholder has no configurable properties.
• Do not expect the step to process or transform data.
• Do not add configuration instructions for inputs the step does not define.
• Use the step to maintain a clear workflow structure where an intermediate node is useful.
• When using a placeholder in workflow design, document its intended purpose if the node's reason is not obvious.
• Avoid treating the Placeholder as a substitute for a processing step unless its pass-through behavior is all that is required.
• Verify the connections entering and leaving the Placeholder to maintain the intended workflow path.
• Test the complete workflow after adding or repositioning a Placeholder.
• If a specific business operation is eventually required at that position, use an appropriate processing step rather than assuming the Placeholder performs that operation.
• The XML does not define explicit return values, so avoid assigning specific True/False execution semantics to the Placeholder.

Notes:

• Category: Logic
• Internal Name: placeholder
• Label: Placeholder step that lets other steps pass through
• Display Name: Place Holder
• Namespace: FlowWright.Workflow.ClsPlaceHolder
• DLL: FlowWright.Workflow.dll
• Step Definition Type: Process
• Incoming Connections: 2
• Outgoing Connections: 2

Definition Sample:

A sample Place Holder definition can demonstrate how the step occupies an intermediate position in a process flow.

For example:

Start → Place Holder → Process Request → Complete

Before using a definition sample, verify:

• The Place Holder is positioned where a pass-through node is appropriate.
• The incoming connection is connected to the intended preceding activity.
• The outgoing connection is connected to the intended next activity.
• No step-specific properties are expected, because the step defines none.
• The workflow continues through the intended process path.
• Any downstream activity is independently configured with its required properties.

Save the process definition before creating and executing a workflow instance.

Click here to download the sample file.