Workflow vs Business Process

Overview

timveroOS uses two distinct but complementary systems for automation. Understanding the difference is crucial for proper configuration.

Workflow Engine Workflows

What They Are

• Automated evaluation and decision-making logic

• Created using the visual Workflow Designer

• Execute at specific points to assess data and make decisions

What They Do

• Retrieve data from external sources

• Calculate scores and metrics

• Apply business rules

• Generate decisions (approve/decline/review)

Example

A credit scoring workflow that:

1. Loads credit bureau data

2. Calculates credit score

3. Applies minimum score rules

4. Creates approval or Warning Fact

Business Process Flows

What They Are

• The complete journey of an entity through the system

• Defined stages from creation to completion

• Powered by SDK actions and events

What They Do

• Define application lifecycle stages

• Control state transitions

• Orchestrate when workflows execute

• Manage the overall process flow

Example

A loan application process:

1. Application Created (state)

2. → Triggers credit check workflow

3. Underwriting Review (state)

4. → Triggers income verification workflow

5. Approved (state)

6. → Triggers document generation

7. Funded (state)

How They Work Together

Business Process Flow (SDK):
[Application] → [Underwriting] → [Approved] → [Documented] → [Funded]
                     ↓                              
                  Workflow         
                  Executes         

Product-Participant-Workflow Relationship

1. Product Configuration defines required participants and assets

2. Participant/Asset Creation triggers their associated business processes

3. Business Processes orchestrate when workflows execute

4. Workflows evaluate data and make decisions about participants/assets

Products don't directly trigger workflows - they define the entity composition that drives the process.

Configuration Responsibility

Component	Configured By	Tool Used
Workflow Engine Workflows	Admin Users	Visual Designer
Business Process Flows	Developers	SDK Code
Form Builder Forms	Admin Users	Form Builder
SDK Forms	Developers	SDK Code
Entity Checkers	Developers	SDK Code

Best Practices

1. Don't Confuse Scope

• Workflows evaluate and decide

• Processes orchestrate stages

2. Use Appropriate Tools

• Visual designer for decision logic

• SDK for process flow changes

3. Coordinate Changes

• Workflow changes may require process updates

• Process changes may require new workflows

Common Misunderstandings

Misunderstanding 1: "Workflows Control the Application Flow"

Reality: Workflows make decisions at specific points. The business process (SDK) controls the application flow.

Misunderstanding 2: "I Can Change Process Stages in the Workflow Designer"

Reality: The Workflow Designer only creates decision logic. Changing process stages requires SDK development.

Misunderstanding 3: "Form Builder Forms Can Be Used Anywhere"

Reality: Form Builder forms are exclusively for workflow warnings. General forms require SDK development.

When to Contact Development Team

Contact your development team when you need to:

• Add or modify business process stages

• Create forms for general use (not workflow warnings)

• Implement Entity Checkers

• Change state transitions or process flow

Next Steps

• Workflow Fundamentals - Learn about Workflow Engine configuration

• Form Builder - Configure forms for workflow warnings

• Consult SDK documentation for business process changes

---

For additional clarification on workflows vs business processes, consult your implementation team.