> ## Documentation Index > Fetch the complete documentation index at: https://docs.germainux.com/llms.txt > Use this file to discover all available pages before exploring further. # Configure a Business Process or Workflow > Use the Business Process Wizard to define the workflow GermainUX should monitor, including steps, correlation, timeouts, SLAs, and automated actions. Service `Analytics` Availability 2014.1 or later > [card] [Use the Business Process Wizard](#use-the-business-process-wizard) > > Define steps, SLAs and actions > [card] [Define the Business Process](#1-step-1-define-the-business-process) > > Set general process behavior > [card] [Configure Process-Level SLAs and Actions](#step-3-configure-process-level-slas-and-actions) > > Step delays versus overall time > [card] [Update an Existing Business Process](#update-an-existing-business-process) > > Get help from GermainUX ## Use the **Business Process Wizard** Use the **Business Process Wizard** to define the workflow GermainUX should monitor, including its steps, correlation criteria, timeouts, SLAs, automated actions, and dashboard visualization. ## Create a Business Process You can start the configuration in either of the following ways: | Option | Action | | - | - | | Via Settings | Go to **Germain Workspace > Settings > Wizards > Business Process**. | | Via Analytics | Go to **Germain Workspace > Analytics > Business Processes** and select the **Add** icon. | Select the appropriate process type: * **Traditional Business Process** * **Collaborative Business Process** The wizard then guides you through four configuration steps. ## 1 Step 1: Define the Business Process Configure the general behavior of the process. | Field | Description | | - | - | | **Name** | Unique name identifying the business process. The name is also used when generating its KPI. | | **KPIs** | KPIs containing the data that GermainUX should evaluate for this process. | | **Key Expression** | Property used to correlate events belonging to the same process instance, typically `sessionId`, `correlationId`, or another business identifier. | | **Long-Lived BP** | Enable when the process may require more than a few days to complete. | | **Data Latency** | Expected delay, in seconds, before process data is received. Default: `3600`. | | **BP Timeout** | Maximum time, in seconds, that a process can remain open. When exceeded, its status becomes `TIMED_OUT`. Default: `7200`. | | **Record Outside Steps** | Records matching events that occur outside the defined process steps. | | **Record Timeout** | Retains a process instance when it times out. When disabled, timed-out instances are discarded. | | **Record Timeout Threshold** | Minimum completion percentage required to retain a timed-out process instance. | | **Record Reset** | Retains a process instance when it is reset. When disabled, reset instances are discarded. | | **Record Reset Threshold** | Minimum completion percentage required to retain a reset process instance. | | **Outside Filters** | Filter criteria applied to events recorded as outside steps. When empty, all matching events outside the defined steps are collected. | ## 2 Step 2: Define the Process Steps Add each step that GermainUX should identify and track within the workflow. | Field | Description | | - | - | | **Name** | Unique name for the step within this business process. The name is also used when generating the step KPI. | | **Recurring Step** | Enable when the step can occur more than once in a single process instance. | | **Optional Step** | Enable when the process can be completed without this step. | | **Filters** | Criteria used to identify the step. Each key references an attribute in the GermainUX , and each value defines the data to match. | | **SLA Threshold Value** | SLA threshold applied to the step. | | **SLA Color** | Color assigned when the step does not meet its SLA. | | **SLA Actions** | Alerts or automated actions triggered when the step does not meet its SLA. | | **Label Generator** | MVEL expression used to generate a contextual step label. Default: `name`. For example: `"Click on " + hierarchy.level1`. | Repeat this configuration for every step in the workflow. ## Step 3: Configure Process-Level SLAs and Actions Define the SLA for the complete business process. | Field | Description | | - | - | | **SLA Threshold Value** | SLA threshold applied to the entire process. | | **SLA Color** | Color assigned when the process does not meet its SLA. | | **SLA Actions** | Alerts or automated actions triggered when the process does not meet its SLA. | Step-level SLAs identify delays within individual workflow stages, while the process-level SLA evaluates the overall completion time. ## Step 4: Create the Portlet Optionally add a portlet so the new business process can be monitored immediately from a dashboard. | Field | Description | | - | - | | **Dashboard** | Dashboard on which the business-process portlet will be added. | | **Portlet** | Portlet type and visualization settings. | Select **Finish** to create the business process. ## Update an Existing Business Process **1. Go to Germain Workspace > Analytics > Business Processes** **2. Select the business-process definition you want to modify** **3. Update its process, step, SLA, action, or visualization settings** **4. Save the changes** If you need assistance defining or configuring a workflow, [contact GermainUX](https://docs.germainux.com/main/support.md). ## Additional Resources > [card] [Troubleshoot GermainUX](https://docs.germainux.com/main/germain-enterprise-troubleshooting.md) > > Read more > [card] [Management](https://docs.germainux.com/main/management.md) > > More Management Features ## Get Help > [card] [Contact GermainUX Support](https://docs.germainux.com/main/support.md) > > The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes. > [card] Can't find what you need? > > Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing. The content of this document is proprietary to GERMAIN SOFTWARE. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.