---
title: "Process Design Studio"
slug: "process-design-studio-impl"
updated: 2025-04-22T18:39:04Z
published: 2025-04-22T18:39:04Z
canonical: "docs.visualvault.com/process-design-studio-impl"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.visualvault.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Process Design Studio

## Process Design Studio

### **Feature Overview**

The Process Design Studio is a feature in VisualVault designed to streamline and manage business process automation (BPA). It serves as the administrative interface where users can design and oversee workflows without needing complex coding.

### **Feature Objective**

The Process Design Studio integrates machine learning and predictive analytics to optimize workflows and provide insights, helping organizations improve efficiency and make data-driven decisions.

### **Feature Description**

The Process Design Studio offers a graphical, drag-and-drop interface for creating workflows, with customizable event triggers to start processes based on specific criteria. It also includes data tools like Data Views for querying existing data and Data Warehouses for storing datasets used in reporting and analysis.

### **Quick Start Guide**

New to Process Design Studio? Use this guide to learn the basics.

![Business Process Stats Once you have opened the Process Design Studio, the first screen that will be displayed is the Business Process Stats page. The Business Process Stats Dashboard shows summary information on the different elements that form processes. It also holds a list of workflows currently “In Progress.” Processes A process is composed of Workflows, Events, Data Warehouses, Data Views, and/or Data Models. Each of these items can be organized and grouped in different processes as needed. Events Events are actions that can be configured based on a form or document, selecting the relevant fields that will trigger the event depending on the creation, modification and/or deletion of these items. Whenever the Event is triggered, it can, for instance, start a workflow or complete a data warehouse, depending on how it was set up. Data Data Views Data Views are queries that can join multiple data sources, used for Workflow rules and/or Analytics and Reporting. Data Warehouses Store Event Data for Analysis and Reporting Data Warehouse is a tool that allows setting information on database tables. Data can be created based on the information collected from Events, as well as uploaded via CSV files. Workflow A Workflow is a configurable course of actions that can be designed based on specific work procedures, with the objective of optimizing and automatizing, Analytics The objective of Analytics is to predict a certain aspect of an Event’s data, based on a machine learning tool that will use Data Warehouses as a source for analysis. The result of a Data Model will be used in the comparison that will initiate a Workflow. This is set up on the Rule Builder tab of the Workflow Event´s configuration. Data Models Create a machine learning model in order to predict a field of the form, giving the user the ability to expose an endpoint in order to use it later as a workflow trigger. Document Classifier The Document Classifier feature allows VisualVault users to create and train their own machine-learning models, which will be used to automatically classify documents through a specific action on Workflows. Creates a model from a folder directory or a CSV file](https://cdn.document360.io/10763bcf-f13e-488f-9c3e-d6737c42ab5e/Images/Documentation/Quick Start Guide_Process Design Studio.png)

#### Step-by-step instruction

#### **Section 1. Navigate to Process Design Studio**

1. Open **VisualVault** in your browser.
2. At the top, open the **Control Panel**.

**Note:** Must be a VaultAccess user.
3. Select **Enterprise Tools.**
4. Click on **Process Design Studio**.

[Learn more at the VisualVault Training Course, Process Design Studio - Introduction (350-VV-IMPL)](https://visualvault.talentlms.com/learner/courseinfo/id:226)

#### **Section 2. Configure Events**

1. Open **VisualVault** > **Process Design Studio** in your browser.
2. On the left, click **Events**.
3. On the top right, click **New Event Source**.
4. Enter a **Name** and **Description** for the event source.
5. Under the **Type** section, select either **Form Data** or **Document Data**.
6. In the **Form Types** section, select the name of the form template or document which you will use as your event source.
7. Select the **Fields** to include.

**Note**: These fields will later become your Workflow Variables.
8. Choose the **Additional Metadata Fields** to include.

**Note**: It is recommended to always include the FormID or DocID.
9. In the **Event types included in stream** section, select the actions (Created, Modified, and Deleted) that will trigger the process based on form or document submissions.
10. Click **Create** to finalize the Event Source setup.

[Learn more at the VisualVault Training Course, Process Design Studio - Introduction (350-VV-IMPL)](https://visualvault.talentlms.com/learner/courseinfo/id:226)

#### **Section 3. Design a Workflow**

**Part 1. Create a New Workflow**

1. Open **VisualVault** > **Process Design Studio** in your browser.
2. On the left, click **Workflow**.
3. On the top right, click **New Workflow**.
4. Enter a **Name** and **Description** for the workflow > **Save draft**.

**Part 2. Add an Event**

1. On the top right of the Workflow page, click the **Events** tab.
2. Click **Add new** **event**.
3. Enter an **Event Name** and **Description.**

**Note:** Adding information about the rules for filtering this event can be useful here.
4. Select an **Event Source**.

**Note:** Choose from a list of Event Sources which were previously set up in Section 2. Configure Events. The **Event Fields** and **Event Triggers** displayed on the right correspond to the configurations of the Event Source and specify the data that has entered the pipeline.
5. In the **Rule** section, click **New Row** to create a new rule.
6. Configure a rule that will trigger the workflow based on specific conditions. For example, you might want to initiate the workflow when a particular field is not empty, equals a certain value, or meets other criteria.

**Note:** Workflow rules can be simple, such as comparing a field to a static value, or more advanced, utilizing predictive analytics, data views, or dynamic event fields.
7. Add **Mapping Conditions** for each of the Event Fields.

**Note**: Mapping transforms event fields into workflow Variables. It is recommended to map each field to a variable with the same name.
8. Once you are satisfied with the event configurations, click **Create Event** at the bottom right.

**Part 3. Add and Configure Actions**

1. On the top right of the Workflow page, click on the **Designer** tab.
2. Drag and drop an **Action** onto the **+ icons** within the designer workspace.

**Note**: Every workflow must include at least one **Finish** action for each path in the workflow.
3. Click on the Action card to display its configuration details on the right-hand side of the designer.
4. In the **Step Name** and **Step Description** fields, enter relevant information. This is especially useful for complex workflows, as it helps provide context for each action at a glance. This description is displayed on the action card within the designer.
5. Click the **Configure** button on the Action card, to start set up.

**Note**: Changes in the Workflow Designer are *not* automatically saved. To avoid losing progress, it is recommended to click the **Save draft** button frequently as you make changes to the workflow.
6. Repeat steps 2 through 5 until you have designed the complete workflow for the business processes you need.
7. Once you've configured the Action details, click the **Save** button to apply your changes.

#### **Section 4. Publish and Test the Workflow**

**Part 1. Publish the Workflow**

1. Back in the **Designer** screen, click the **Publish** button to finalize and publish the workflow.

**Part 2. Test the Workflow**

1. On the top right of the Workflow page, click on the **Test** tab.
2. Click the **+ Create Test Data** button to initiate the creation of test data.
3. Type a name for the test data in the Test Data Name field.
4. Provide values for **Test Fields** > click **Save**
5. Check the box next to the test you just created.
6. Enter an **ObjectId**. This value allows you to easily identify your test run when you review the run details in the History tab. If you do not enter a value manually, a random GUID will be assigned when the test runs.
7. Click the **Run Test** button.
8. Click **OK** in the popup that appears.

**Part 3. Monitoring Workflow Progress**

1. On the top right of the Workflow page, click on the **History** tab.
2. Find the workflow instance that you just tested and click its View icon. By default, the most recent run of the workflow will be listed first. You can also identify which run to select by the Object ID you entered.
3. Click on the Action cards within the Workflow Execution History to view details about the Workflow Variables.

---

### FAQ

#### When did workflow variables not populate from the form fields I selected when I configured the event?

This API request requires an extended processing time during initialization. Please allow sufficient time for completion before attempting next steps.

### Glossary

| Term | Meaning |
| --- | --- |
| Analytics |  |
| Business Process Stats Dashboard | The Business Process Stats Dashboard shows summary information on the different elements that form processes. It also holds a list of workflows currently “In Progress” |
| Data Warehouse | A tool that allows setting information on database tables. Data can be created based on the information collected from Events, as well as uploaded via CSV files. |
| Data Models | Create and edit data models, to predict a certain aspect of an event's data based on a machine learning tool. |
| Data View | Queries that can join multiple data sources, used for Workflow rules and/or Analytics and Reporting. |
| Document Classifier | Create and train machine-learning models, which will be used to automatically classify documents through a specific action on Workflows. |
| Events | Events are actions that can be configured based on a form or document, selecting the relevant fields that will trigger the event depending on the creation, modification and/or deletion of these items. Whenever the Event is triggered, it can, for instance, start a workflow or complete a data warehouse, depending on how it was set up. |
| Event Source | Event Sources are pivotal triggers in the Process Design Studio that are activated by document or form actions. An event source is very simple. Event sources look for when an event type occurs and determine what data to include when the event occurs. When an event occurs, the event source sends the specified data into an "events pipeline". This data is then available to be interpreted by the configurations of workflows. |
| Processes | A Process is composed of Workflows, Events, Data Warehouses, Data Views, and/or Data Models. Each of these items can be organized and grouped in different processes as needed. |
| Workflow | A Workflow is a configurable course of actions that can be designed based on specific work procedures, with the objective of optimizing and automatizing, |