placeholder Step

Use this step as place holder to let other steps pass through.

Last published at: October 21st, 2024

Description:

This step is used as a placeholder and lets other steps pass through. Especially when logic is used before a synchronized step, the placeholder step can ensure the paths go through the synchronized step.

 

Inputs

  • None
 

 

Returns

  • None
 

 

Usage:

 

 

Example:

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

  • Create a new definition called “placeholderDef” 
  • Select the definition and click the “design” button
  • Drag the above steps and connect them
  • Click the "placeHolder" step to configure its "Settings" properties. Provide a name to the step. 

 

  • Click the "decision" step to configure its "Settings" properties. Provide a name to the step. Provide a condition to evaluate. 

 

  • Click the "Wait" step to configure its "Settings" properties. Give the step a name and set the time duration to wait.  

 

  • As you notice, if the decision step’s paths come to the synchronize step, given the behavior of the synchronization step, the workflow will never pass through the synchronize step.  However, with the placeholder step, it is possible to satisfy these conditions. 
  • Save the process definition, create a new process instance, and execute. Render the process instance. The placeholder step lets other steps pass through.

 

 

Definition Sample:

You may download the sample definition(s) from the link here and later import it (drag-drop) to your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.

NOTE: Please verify and complete the process steps for any missing configurations, such as file path references and database connections after import. Then, save the definition to confirm the changes.

Click here to download the sample file.