Automate everyday tasks
Connect manual tasks into one workflow: receive data, check it, ask for a person’s decision and update the required system. Help your team follow the same rules and see what happens at each step.
Conditions · choice · context
A clear process for users and administrators
Branches driven by data and human decisions
Shared logic for forms, APIs and scheduled execution
Describe the process in business terms
Build the route around a real task, such as updating a forecast, preparing a request or passing information between departments. Blocks, connections, groups and notes explain each stage. Teams can discuss the rules more easily when they are visible rather than scattered across spreadsheets and conversations.
- Visible stages, block groups and canvas notes
- Conditional routes and alternative branches
- Separate continuation after successful writes or errors
Involve people when their input matters
A wizard can request parameters, a file or a choice, and show a data preview or message. Configure the steps that help the person complete the task. For example, a user selects a company and period, reviews the prepared dataset and continues processing with the appropriate context.
- Parameter forms with default and required values
- Data previews and explanations before the next step
- User choices that select a configured route
Define the outcome
Identify the trigger, participants, rules and changes required in business systems.
Build the scenario
Connect sources, conditions, interaction forms and data destinations.
Walk through it with a user
Check parameters, branches and messages in a simulation before publishing.
Connect forms to business data
Inside UBC Analytics, a flow can use the form record that launched it, enrich that record from reference forms and incorporate role and user context. This supports request validation, calculations and subsequent updates to a form or cube as part of a defined business process.
- Process the relevant business-form record
- Look up reference values and map fields
- Set statuses and notify people about the result
Grow the process without copying its rules
Move common processing into a reusable subflow and design routes for different entry points. A scenario can begin with a button, API or schedule when its steps support that launch method. Execution history helps the team understand where processing finished and what needs attention.
- Reusable subflows for calculations and checks
- Routes based on how execution was started
- Execution history, results and notifications
Conditions · choice · context
Your questions, answered.
How to connect your data, manage access and get started.
Does every run open a wizard?
No. Windows are needed only where the scenario requires interaction. Background flows can run without a person when all required values are available.
Can a workflow operate inside UBC Analytics?
Yes. That deployment provides forms, reference data, cubes and user and role context for configured workflows.
How does a user see the outcome?
Through configured messages, the launch button status, execution history, or email and Telegram notifications.
Let’s start with your task.
Tell us which data you need to connect. We will explain how it works and show you an example.
Bring your challenge. See a way forward.
Sources, rules and outcomes — let’s build the conversation around your workflow.