Description:
This step converts the Word document to a text document and stores the file on the application server.
Inputs
- wordFilePath - provide the Word document input file path on the application server
- textVarGlobal - variable/global to store the output text file path
Returns
- True – step executed successfully
- False – step failed to execute
Usage:
Example:
Let’s build and execute the “WordToTextDef” example.
- Create a new process definition called “WordToTextDef” and open it in Designer mode.
- Drag a “WordToText” step to the canvas.
- Connect the “Start” step to the “wordToText” steps, as shown above.
- Define a variable or a global to store the file path.
- Click the "WordToText" step to configure its "Required" properties. Provide a name for the step. Provide the path to the Word document on the app server. Provide a variable or a global reference to store the output file path. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description.
- The “Logging” configuration is necessary for documentation and also measures workflow progress and 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 execute it. Render the process instance. Click the process step to view its properties. The “wordToText” step should convert the Word document and store the resulting text file in the output path.
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 the import. Then, save the definition to confirm the changes.