Advance & Settings

Form Builder

The Form Builder tab, located within the home menu, provides users with a powerful tool to create custom forms directly within the Designer. This feature is designed to streamline the process of building interactive forms for automation workflows. If the Form Builder is not yet installed in your environment, clicking on this tab will automatically begin the installation process. During installation, the required components are downloaded and set up, ensuring that the feature is available for use.

Once the installation is complete, the tab will refresh, and you can easily click on it again to launch the Form Builder interface. This opens a dedicated window where users can design and configure their forms, specifying fields, actions, and conditions for a seamless user experience in automation processes.

The Form Builder tool allows users to create complex forms with ease, leveraging a wide range of customization options, including field types, validation rules, and interactive elements. Whether you need to collect data from users, enable inputs for automation, or create customized workflows, the Form Builder offers all the necessary features for efficient form creation.

Logs

The Logs option in the Home menu offers two essential features: Open Logs and Log Settings, designed to help users monitor and troubleshoot workflows effectively.

Open Logs

The Open Logs feature provides direct access to the log files stored in the system. By clicking this option, users can view detailed logs related to workflow execution. These logs capture important information about the system’s activities, including timestamps, error messages, warnings, and other critical data. Accessing these logs is crucial for troubleshooting, identifying system performance issues, or simply reviewing the outcomes of automated processes. Users can filter and analyze log data to gain insights into how their workflows are performing, making it easier to detect errors or optimize workflows for improved efficiency.

Log Settings

The Log Settings feature allows users to customize the log level for their workflow execution. By adjusting the log settings, users can control how much information is captured and displayed during the execution process. This feature provides five different log levels, each suited for specific use cases. Here’s a detailed breakdown of each:

1. Trace

Purpose: The Trace log level is the most detailed level of logging. It captures fine-grained information about the execution of specific portions of the code. This level is primarily used for tracing function calls, variable states, and other minute details that are helpful for diagnosing subtle or complex issues.
When to Use: Trace logs are typically used during development or debugging phases to understand the flow of the automation process at a very granular level. It’s particularly helpful for developers who need to trace the execution step-by-step to pinpoint the cause of problems.

2. Debug

Purpose: The Debug log level is used to record messages specifically related to the debugging process. This log level helps developers by capturing information that provides insight into how code is executing, without overwhelming them with excessive details.
When to Use: Use this level during development to capture useful debug messages. It’s ideal when you’re testing new workflows or troubleshooting development-stage issues and want to monitor the workflow’s behavior in real-time.

3. Info

Purpose: The Info log level records general informational messages that don’t indicate errors. These messages provide context about the workflow’s execution, such as progress updates, completion confirmations, or routine status updates.
When to Use: Info logs are best for capturing events that represent normal operation, such as successfully completing tasks or reaching checkpoints. This level allows users to understand the general flow of the workflow without being distracted by unnecessary details.

4. Error

Purpose: The Error log level is designed to capture serious issues that impact the workflow’s functionality. This level logs critical errors that may prevent the process from continuing or result in workflow failure.
When to Use: Error logs are essential when a workflow encounters a fault that stops its execution. It’s particularly important to monitor this level during production or mission-critical workflows, as it helps identify and address major issues promptly.

5. Warn

Purpose: The Warn log level captures warnings related to potential issues or deviations from the expected behavior that do not necessarily stop the workflow from running. These warnings are meant to alert users to conditions that could become problems in the future, such as slow performance or minor exceptions.
When to Use: Use Warn logs when you suspect there might be an issue that doesn’t require immediate action but should be monitored. For example, a workflow might be running slower than expected, or a deprecated feature might be used—Warn logs help catch such conditions before they escalate.