Workflow Channels
Introduction
By default, an input Workflow Profile clears, loads, and locks all of an entity's data for an Origin member as a single unit. Workflow Channels bind an input child profile to a subset of cells — grouped by Account (or one designated User-Defined dimension) — so those account groups can be cleared, loaded, and locked independently. This enables phased processing where, for example, revenue accounts can be loaded and locked separately from expense accounts.
What Channels Are
A Workflow Channel is an application-level tag (a name and description) that groups dimension members and is then bound to input child profiles. Each channel:
- Is associated with a set of Account members (or members of one designated User-Defined dimension) by tagging each member's Workflow Channel property
- Controls data clear / load / lock granularity for the accounts in that channel — they can be loaded and locked independently
- Is reflected in the workflow's Dependent Status view (it is not a user-facing "channel selector" in the task bar)
Channels do not create new profiles. They partition how an input profile clears, loads, and locks cube cells so that different account groups move independently.
When to Use Channels
Phased close — Revenue loaded and locked by Day 3, Expenses by Day 5, Adjustments by Day 7. Each channel can be locked down without waiting for the others.
Different data sources — Payroll from an HR system (Channel 1), Revenue from an ERP (Channel 2). Each channel can have its own import configuration and schedule.
Separate ownership — Different teams own different account groups within the same entity. Channel-level status lets each team track progress without stepping on the other.
Configuration
Setting up channels involves three steps:
- Create Workflow Channels at the application level (Manage Workflow Channels) — give each channel a name and description.
- Tag dimension members — set each Account member's (or designated UD member's) Workflow Channel property to the channel it belongs to (settable per Scenario Type).
- Bind channels to Input child profiles — tag each Import or Forms child profile with the Workflow Channel it should control, so its clear/load/lock applies only to that channel's cells.
The same entity can have different channels loaded and locked at different times.
Independent Load and Locking
Each channel's data is cleared, loaded, and locked independently:
- Loading is per-channel — loading (or replacing) data for the Revenue channel does not clear or overwrite the Expenses channel's cells.
- Locking follows channels — a locked Revenue channel still allows data entry into Expenses.
- Certification stays profile-level — certification is not per-channel; the input profile is confirmed and certified as a unit once its data is complete.
This granularity is what makes phased close processes practical. Teams working on earlier channels can lock down their data while later channels are still open for entry.
Channels vs. Separate Profiles
| Factor | Channels | Separate Profiles |
|---|---|---|
| Same entity, different account groups | Good fit | Overkill |
| Different entities entirely | Overkill | Good fit |
| Need independent security per group | Not supported — channels share profile security | Good fit |
| Need independent load/lock timeline | Supported | Supported |
| Complexity tolerance | Lower — single profile to manage | Higher — more profiles to manage |