Platform › Business Flows
Flow Definitions
The chains themselves. A template ships with the platform; a copy belongs to whoever made it.
Where to find it
- Module: Platform
- Group: Automation
- Section: Business Flows
- Screen: Flow Definitions
Address in the console: /platform/flows
List · 7 columns · 8 fields on its form · 2 of them required
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Code | Code | code |
| Name | Text | name |
| Family | Status | family |
| Modules | Text | modules |
| Step Count | Number | step_count |
| Edge Count | Number | edge_count |
| Is Active | Yes or no | is_active |
The form
What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.
| Field | Type | Choices | Notes |
|---|---|---|---|
| Code required | Text | ||
| Name required | Text | ||
| Family | Choice | scm, crm, mfg, hrms, slcm, ehr, ats, accounting | |
| Primary module | Text | ||
| Description | Long text | ||
| Template | Yes or no | ||
| Active | Yes or no | ||
| Order | Number |
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.
- Creating a record — required fields, where choices come from, and how the number is allocated.
- Importing a spreadsheet — this screen accepts one, and it runs through the same rules as typing.