Description:

The Log Info workflow step logs an information message to the System log. It allows the workflow to specify the source of the information, provide a detailed message, and optionally select a logging priority.

The step supports:

• Specifying the source of an information message.
• Providing a detailed information message.
• Logging multiline information.
• Assigning an optional logging priority.
• Recording workflow information in the System log.
• Returning a True or False result for workflow routing.

Usage:

The Log Info step is typically placed after an important workflow activity when the workflow needs to record operational or informational details in the System log.

A typical workflow pattern is:

Workflow Activity → Log Info → Continue Processing

For example:

Start
  ↓
Process Request
  ↓
Log Info
  ↓
Continue Processing

Typical Workflow Suggestions:

Log Workflow Processing Information

Use the Log Info step to record information about an important workflow operation.

Example:

Start
  ↓
Process Request
  ↓
Log Info
  ↓
Continue Process

Process: Order Processing
Instance: {{InstanceID}}
Operation: Process Order
Status: Started

Log Integration Activity

Use Log Info after an external integration step to record information about the integration operation.

Example:

Prepare Request
      ↓
REST/API Call
      ↓
Log Info
      ↓
Continue Processing

Integration: Customer API
Operation: Retrieve Customer
Request ID: {{RequestID}}
Status: Completed

Log Status Changes

Use the step when a workflow reaches an important processing state.

Example:

Start
  ↓
Validate Request
  ↓
Log Info
  ↓
Approve Request
  ↓
Log Info
  ↓
Complete

Request validation completed successfully.

Request ID: {{RequestID}}
Status: Ready for approval

Log Detailed Multi-Line Information

Because Information message to log uses the multilineTextBox data type, the step can be used to record structured information containing multiple lines.

Example:

Document Processing Status

Document: {{DocumentName}}
Document ID: {{DocumentID}}
Process Instance: {{InstanceID}}
Operation: Document Validation
Status: Completed

Record Information Before or After a Major Operation

Use Log Info around significant workflow activities to record processing milestones.

Example:

Start
  ↓
Log Info
  ↓
Document Processing
  ↓
Log Info
  ↓
Complete

Example:

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

• Create a new process definition named “clsLogInfoDef” and open it in designer mode. 
• Drag a "clsLogInfo" step to the canvas.
• Connect the dots between the “Start” and "clsLogInfo" 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 "clsLogInfo" step to configure its “Required” properties. Provide a name for the step, the source of the information message, and the text 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 "clsLogInfo" step to configure its “Optional” properties. Select a priority from the dropdown list (Low, Medium, or High). 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 a new instance, and execute it. As configured, the process step should log the information message to the System log. Navigate to the Status—System log page and select the log by type and information.

Tips:

• Provide a meaningful Information Source so that the origin of the logged information can be identified easily.
• Include enough context in the information message to make the log entry useful.
• Use the multiline message field to organize detailed information into readable sections.
• Include relevant workflow context such as process instance information, record identifiers, or operation details where appropriate.
• Use consistent information-source names across workflows.
• Configure Priority when the workflow requires a specific logging priority.
• Avoid logging passwords, authentication tokens, secrets, or other sensitive credentials.
• Avoid unnecessarily logging confidential or sensitive business information.
• Use Workflow Variables where appropriate to include runtime information in the message.
• Test the message configuration before deploying the workflow.
• Verify the System log after execution to confirm that the expected information was recorded.
• Connect the False path to appropriate error-handling logic.
• Test both successful and unsuccessful logging scenarios.
• Use consistent message formatting when multiple workflows write similar types of information.
• Keep informational messages specific rather than using generic messages such as Processing completed.
• Include the operation or workflow activity associated with the information where useful.
• Use Log Info for informational events rather than treating routine processing messages as errors.
• Verify the available logging-priority options in the FlowWright environment before documenting specific priority names.

Definition Sample:

You may download the sample definition and later import it into your FlowWright Process Definition (XML file) or Form Definition (HTML file).

Note: Verify and complete any missing configuration after importing the sample, including:

• Information Source.
• Information message to log.
• Priority.
• Workflow Variable references.
• Environment-specific logging configuration.
• Downstream True and False workflow paths.
• Any error-handling or notification activities.

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.