Workflows

Create a workflow

A workflow is a versioned automation built by connecting nodes on a canvas. New workflows begin as drafts and do not respond to live events until they are published.

Path: Settings > Modules > Workflows

1. Select Add Workflow.
2. Enter a Name and optional Description.
3. Select a scope: Policy, Claims, or Billing.
4. Optionally, enable Only apply to specific policy type versions to restrict the workflow to selected products.
5. Leave Enable on save off while building and testing the workflow.
6. Select Create workflow.

BriteCore opens the workflow canvas with an unconfigured Trigger node.

Tip: Draft workflows display an issue count when nodes are incomplete or incorrectly configured. Resolve these issues before publishing.

Build a Workflow on the Canvas

Add nodes to the canvas, connect them in the order they run, and configure each one in the right-hand panel.

• Add a node: Drag a tile from the Node palette onto the canvas, or select + on an existing node to add a node after it.
• Connect nodes: Drag from one node's connection point to the next node. [confirm: exact connect gesture]
• Configure a node: Select the node and complete its settings in the right-hand panel. A node shows Not yet configured until its required values are set.
• Move nodes: Drag a node to a new position on the canvas. [confirm: positions are saved with the workflow]
• Select several nodes: Hold Shift and select each node, or hold Shift and drag across them.
• Delete a node: Select the node, and then select Delete node or press Delete. You cannot delete the Trigger node.
• Delete a connection: Select the connection, and then select Delete edge.

Workflow building blocks

Workflows are built using the following nodes:

Configure a trigger

The Trigger defines what starts the workflow. It also determines which data is available for downstream conditions.

Select the Trigger node and choose a Trigger event. You can also add an optional note to make the workflow easier to understand on the canvas.

Available events depend on the workflow’s scope.

Policy and billing events: Policy Issued, Policy Endorsed, Policy Cancelled, Policy Renewal Approaching, Referred to Underwriting, STP Analysis Executed, Subjectivity Created, File Attached, NSF Payment, and Payment Failed.

Claims events: Claim Submitted, Claim Party Added, and Days Since Claim Date.

Task events: Task Created, Task Completed, and Task Due-date Passed.

Trigger data and conditions

Each event exposes fields that downstream Gateways can evaluate.

For example, File Attached provides fields such as file category, file group, file name, and policy ID. This allows a workflow to respond differently based on the type of document attached.

STP Analysis Executed provides information such as whether the submission cleared STP without referral and which STP rules were flagged.

Route work with Gateways

Gateways create conditional branches in a workflow.

For example, a File Attached workflow can continue only when the attached document is a Wind Mitigation document.

To configure a Gateway:

1. Add a Gateway after another node.
2. Choose whether all conditions or any condition must match.
3. Add the field, operator, and value for each condition.
4. Connect the Yes path for matching conditions.
5. Connect the No path for conditions that do not match.

Example:
File Attached → File Category = Wind Mitigation → Yes → Create Wind Mit Review Task

Configuration dependency: Document-based routing depends on the appropriate file category or other metadata being populated when the document is uploaded.

Chain tasks with Wait nodes

Many workflows require one task to finish before the next action occurs. A Wait node allows the workflow to pause until a task changes state, a deadline passes, or either happens first.

Available Wait modes include:

• Time elapsed
• Task state change
• Task state or timeout

For a task-based wait, select the task the workflow should monitor and, where applicable, configure the timeout.

You can then use a Gateway to determine what happens based on the result.

Example:

Required Documents task → Wait up to 7 days → Documents completed → Continue process

Required Documents task → Wait up to 7 days → Timeout → Close task → Create Underwriting Review task

Timer behavior: Wait timers resume during BriteCore's daily background process. Sub-day durations therefore resume on the next daily run rather than at an exact hour.

Send alerts and notifications

Alert nodes notify someone when an event occurs without creating additional work that must be completed.

For example, an Alert can notify the policy underwriter when required documentation has not been received by its due date.

Recipients can include role-based users such as the policy underwriter or agent, along with additional configured recipients.

Alert vs. Task

Use an Alert when someone only needs to know that something happened.

Use a Task when someone needs to take an action and that work should remain visible and tracked until completion.

Publish and Monitor Workflows

Draft workflows never respond to live events. Once a workflow is complete and its configuration issues are resolved, select Publish to make it active.

Publishing creates a version of the workflow, allowing the configuration to evolve while maintaining a history of published versions.

Workflow management tools include:

The Workflows directory also summarizes workflow activity, including active and draft workflows, active steps, recent firings, and last activity.

Tip: Build and review new automation as a draft before publishing it. Draft workflows are safe to configure and inspect because they do not fire against live events.