Skip to main content
Version: 1

Create Log File

  • Category​

    • Logging

    • Debug

  • Flow Icon​

Overview​

The Create Log File component in Plinqx is tailored for creating structured log entries within your Salesforce flows. These log entries, crucial for debugging and transaction tracking, are stored as records within Salesforce and are associated with specific transactions. Accessible through the Logs tab in the Plinqx Application, these logs play a vital role in monitoring and analyzing flow execution, with all entries created as type 'Debug'.

Inputs​

  1. Add to Transaction:

    Boolean value determining whether to add the log entry to a transaction. Set this to true especially if logging actions occur before call-outs in a flow, preventing 'uncommitted work pending' errors.

  2. Category:

    A classification for the log entry, useful for categorization and reporting purposes.

  3. Log Body:

    The content of the log entry, typically a string detailing the information to be logged.

  4. Name:

    A descriptive name for the log entry, aiding in identification and categorization.

  5. Unique Id:

    A unique identifier for the log entry, ensuring traceability and distinctiveness.

Outputs​

  1. Success:

    A boolean indicating whether the log file was created successfully (True/False).

Example Scenario - Order Processing Flow​

Scenario Overview:

A Salesforce org has an automated flow for processing customer orders. To enhance troubleshooting and monitoring, the team decides to integrate detailed logging at key steps of the order processing flow.

Implementation with Create Log File Component:

  1. Flow Setup:

    The existing order processing flow is reviewed, identifying critical stages where logging would be beneficial, such as order validation, payment processing, and order completion.

  2. Adding Create Log File Component:

    Integrate the Create Log File component at each identified stage within the flow.

  3. Configuring Inputs:

    • 'Add to Transaction' is set to true for logs preceding any external system call-outs.

    • 'Category' is defined based on the stage of the flow, like 'Validation', 'Payment', or 'Completion'.

    • 'Log Body' contains detailed information about the flow's execution status at that point, including any relevant data points or values.

    • 'Name' and 'Unique Id' are assigned for easy identification and correlation with specific order transactions.

  4. Log Creation and Monitoring:

    As the flow executes, log entries are created at each stage, capturing detailed information about the processing steps.

  5. Reviewing Logs for Insights:

    The logs can be accessed from the Plinqx Logs tab, providing insights into the flow's execution, highlighting any anomalies or issues that occurred during order processing.

Results:

By implementing the Create Log File component, the team gains valuable visibility into the order processing flow. The logs provide a detailed audit trail, assisting in debugging and offering insights for process optimization, thereby enhancing the reliability and efficiency of the order management system.