Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mileapp.dev/llms.txt

Use this file to discover all available pages before exploring further.

Workflows in MileApp let you define a sequence of Flows that should run together as a single multi-step process. Each Workflow is a reusable template — pick a Workflow when creating an Activity and MileApp creates one task per step in the order you defined, with optional field mappings to copy data from one step to the next.
Required permission:
  • View Workflow

​
What is a Workflow?

A Workflow is a named template that lists the Flows that make up a multi-step process. For example, a logistics process might combine a Pickup Flow followed by a Delivery Flow followed by a Confirmation Flow — each step using its own Flow form and optionally assigned to a different team member. Workflows themselves are not tasks. They become real tasks only when an Activity is created from them. Each Activity instantiates the Workflow into a parent task plus one child task per step, with field mappings carrying data forward through the chain. Use Cases:
  • Pickup → Delivery → Confirmation: different forms for the pickup runner, the delivery driver, and the recipient confirmation step
  • Order fulfilment: packing, dispatch, last-mile delivery, and proof-of-delivery as separate, trackable stages
  • Service workflows: appointment, on-site service, and follow-up data collection, each with their own form
  • Inspection or audit: opening checklist, field measurement, and reporting, completed by different roles
  • Multi-stage approval: submission, supervisor review, and final approval, with data carrying forward between stages
Use a regular Flow (not a Workflow) when the process fits in a single form, even if it has multiple pages. Use a Subflow when one Flow needs to embed a smaller subtask inside it. A Workflow is the right choice when each stage is independent enough to be its own task and its own form.

​
Workflow Building Blocks

A Workflow has the following parts:
  • Name — a unique name within your organization. Must be between 2 and 100 characters.
  • Steps — an ordered list of between 1 and 10 stages. Each step references one Flow and runs in order (step 1 → step 2 → step 3, and so on).
  • Flow per step — the Flow form the field worker fills in for that step. Every step in the same Workflow must use a different Flow.
  • Assignee per step — one or more users assigned by default to tasks created at that step. The assignee is optional — leave empty to assign manually when the Activity is created.
  • Status Mapping per step — the status that the step’s task moves into. The dropdown lists the Workflow’s default statuses (such as Done, In Progress, Pending) plus any custom statuses you add.
  • Field Mapping per step — for step 1, this is where you can set default values directly. For step 2 and later, you can also map values from any earlier step’s field into the current step’s field.
  • Custom Statuses — extra status labels defined per Workflow and used in Status Mapping. Each Workflow starts with a set of default statuses (such as Done, In Progress, Pending) that you can extend with your own. Each custom status name must be between 1 and 50 characters.

​
Accessing the Workflow Page

Open the Flow section from the main sidebar, then pick the Workflow tab at the top of the page. The Workflow page lists every Workflow in your organization and is the entry point for creating, editing, and deleting Workflows.

​
What’s Next