Products

BP Workflows

BP workflows package a business process into implementations, templates, parameters, and execution flows that can be launched consistently.

When To Use BP Workflows

Use BP workflows when the user wants to run a named business process rather than maintain a generic test case. Workflows can expose parameters, reuse templates, and be launched from chat or the BP workspace.

BP Workflows page with implementations
BP Workflow group showing implementations and templates.
1

Create or open a BP group from the Dashboard.

2

Add an implementation for the specific process variant.

3

Define required parameters and default values.

4

Attach steps or convert existing case logic into the workflow.

5

Run a preview with safe sample data before executing against real records.

Templates And Parameters

Templates make repeatable BP runs safer by capturing approved parameter sets. Parameters should represent business intent, not fragile UI details.

Practical Tips

  • Prefer parameters such as employee, effective date, organization, reason, and amount.
  • Avoid exposing selectors or implementation details to end users.
  • Use clear required-field descriptions so chat can ask useful follow-up questions.

Converting Test Logic Into A Workflow

A test case can prove a process works, but a BP workflow should expose a cleaner business interface. During conversion, remove internal assumptions, name parameters clearly, and decide which values should be locked by a template.

1

Identify the case steps that represent the business process.

2

Replace hard-coded values with parameters.

3

Create one safe template for smoke testing.

4

Run the workflow against a low-risk sandbox record.

5

Document required approvals or tenant prerequisites in the BP description.

Operational Guardrails

BP workflows can change real Workday state, so the launch experience should make target records, effective dates, and selected environment obvious before execution.

Practical Tips

  • Keep a sandbox-only validation template for every workflow.
  • Use chat to find and configure workflows, but keep final execution explicit.
  • Record the business reason in run notes or commit messages when a workflow is governance-sensitive.
Do not run a BP workflow in Production until the selected environment, target worker or object, effective date, and input template have been reviewed.