Platform › Business Flows
Test Scenarios
Augmented data for a flow, made by calling the same routes the screens call rather than by inserting rows behind the application’s back.
Where to find it
- Module: Platform
- Group: Automation
- Section: Business Flows
- Screen: Test Scenarios
Address in the console: /platform/scenarios
List · 7 columns · 8 fields on its form · 3 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 |
| Flow Code | Code | flow_code |
| Step Count | Number | step_count |
| Volume | Number | volume |
| Seed | Number | seed |
| 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 |
|---|---|---|---|
| Flow required | Choice | Looked up from existing records | |
| Code required | Text | ||
| Name required | Text | ||
| Description | Long text | ||
| Times through | Number | ||
| Seed | Number | ||
| Stop on failure | Yes or no | ||
| Active | Yes or no |
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.