Forms

Learn how to use Forms in DBSync Cloud Workflow

Introduction

DBSync Forms streamline data capture and connect it to backend operations seamlessly. These Forms can be customized with various fields (for example, text boxes, variables, and tables) to suit the specific data collection needs of your organization. These Forms can be used to build workflows, integrate with other systems (like Salesforce, QuickBooks, or databases), and automate processes such as creating records, updating fields, or generating reports.

Purpose

The forms simplify the process of changing the object for synchronization. Without the form, a user would have to go inside the flow, into the query configuration, and write an entire query for the new object. If a form is present, changing from a customer to an account on the form is reflected in the query.

Customize Forms

To access Forms, follow the steps given below;

1. In the Automated task page, click Configure next to an automated task.

2. Once the Flow screen is open, navigate to Forms.

3. Click + Form in the top right to create a form if there are no forms created.

   
4. Add a suitable name for the form.

5. Click More (...) in the Actions column and select Edit Action.

6. The Setup Designer window opens for you to customize the Forms.

The Setup Designer consists of two perspective views namely, the Developer View and the Customer View.

When creating forms, there are two distinct views that cater to different user roles and perspectives: Developer View and Customer View. Here's a description of each:

Developer View

This view is designed for the technical users, like developers or administrators, who build, configure, and maintain forms within the workflow. This window presents a canvas to create questionnaires or forms with the help of a tool panel that can be used to obtain relevant information regarding the specifics of the integration. The information that is obtained serves as a tool to customize a template for the end user to use to integrate any two applications.

Depending on the requirement, drag and drop the components (Text, Variable, and Table) and configure them.

The configuration process involves selecting the application (for example, monday.com) and choosing the object (for example, customer ID customer).

• Text: Click the pencil icon to enter the required header text and to edit it.

• Variable: Click the dropped variable to open the Variable configuration panel on the right side and enter the required details for the variable.

• Table: Click the dropped table to open the Table configuration panel on the right side and enter the required details for the variable.

Features

• Access advanced settings to configure the form's behavior, logic, and data flow.

• Define field types, validation rules, and business logic for integration of CRM applications or databases (if required).

• Build forms using the tool panel that has Text, Variable, and Table.

• Set permissions, visibility, and conditions for the form based on business rules.

• Key Users: Developers, IT administrators, and advanced users familiar with the technical side of DBSync workflows.

Customer View

The Customer view provides a simplified, user-friendly interface that illustrates how end-users or customers will interact with the form.

Users can access the forms by clicking Setup for each Automated task in the Automation tab. Each Automated task will have its own forms attached to it.

Forms in Templates and Customer Use:

For customers using a predefined template, the customer view is often already filled out during the implementation time.

• Pre-built templates include all standard flows, not necessarily specific to a customer's needs.

• Customers can use the forms to easily disable specific flows (for example, opting not to sync customers but only transactions). To disable a specific flow, choose No in the corresponding drop-down, without manually turning off the flow or writing a rule.

Features

• Easy to use, with minimal technical details.

• Clean and intuitive interface that only displays relevant fields and options based on user roles and form logic.

• Simple validation messages and user inputs for smoother form submission.

• Hidden technical aspects such as data flow or complex logic.

• Customizable: Meets the specific needs of the customer and end-user without exposing unnecessary details.

• Key Users: Customers, employees, or any non-technical users interacting with the form.

In essence, the Developer View provides full control over the form's design and functionality, while the Customer View ensures a streamlined and intuitive experience for end-users.