Description:

This step logs errors to the FlowWright System Log.

Usage:

Example:

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

• Create a new process definition named “clsLogErrorDef” and open it in designer mode. 
• Drag a "clsLogError" step to the canvas.
• Connect the dots between the “Start” and "clsLogError" steps, as shown above. 
• Click the "clsLogError" step to configure its “Required” properties. Provide a name for the step, the source of the error message, and the message to log. 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 "clsLogError" step to configure its “Optional” properties. Select a priority from the dropdown list (Low, Medium, High). Then click the Save button. 

• 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 an instance, and execute it. As configured, the process step should log the error message to the System log. Navigate to the Status—System log page and select the log by type and error.

Note: If the error log table exceeds a predefined size, it is automatically trimmed (records are deleted). This scheduled job is defined on the server and is triggered when the table size grows. 

Definition Sample:

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

Click here to download the sample file.