Move Data

This feature moves the data between the forms

Last published at: February 24th, 2025

moveFormData Step

Description:

This step is used to move the Form data between Form Instances. 

 

Inputs

  • sourceDefID– Source form definition name
  • sourceFormInstID -- Variable that holds source form instance ID
  • targetDefID – Target form definition name
  • targetFormInstID -- Variable that holds target instance ID
  • formFieldMappings – Mapping of values to form fields 
 

 

Returns

  • True – step executed successfully
  • False – step failed to execute 
 

 

Usage:

 

 

Example:

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

  • Create a new process definition called “moveFormDataDef” and open it in Designer mode. 
  • Drag the “routeForm, moveFormData” steps to the canvas.
  • Connect the dots between the “Start” step and other steps, as shown above.
  • Define a variable or a global to store the Form Instance IDs.
  • Click the “routeForm1” step to configure its “Required” properties.  Provide a name for the step. Select the Form Definitions from the drop-down list. Provide a variable or a global reference to store the Form Instance IDs. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description. 

 

  • Click the “routeForm2” step to configure its “Required” properties.  Provide a name for the step. Select the Form Definitions from the drop-down list. Provide a variable or a global reference to store the Form Instance IDs. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description. 

 

  • Click the “moveFormData” step to configure its “Required” properties.  Provide a name for the step. Select the source and target Form Definitions from the drop-down list. Provide a variable or a global reference to store the source and the target Form Instance IDs. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description. 

 

  • Click the button to map the Form fields as below. A pop-up window is displayed for configuration. Click the Add Row (+) button to insert an empty row. Using the drop-down controls, provide the source and target field names. Click the Save button. You may add multiple form field mappings using the Add Row button.  

 

  • The “Logging” setting configuration is necessary for documentation and also measures the workflow progress and the percent complete. This is achieved by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.

 

  • Save the process definition, create a new instance, and then execute it. Render the process instance. The source form instance is created and routed to the user for input. Upon completion, the target Form Instance is created, and the "move data" step transfers the data from the source to the target Form Instance, routing it to the following user. The Form is rendered with the moved data.  

 

Definition Sample:

You may download the sample definition(s) from the link here and later import them (drag-and-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.