Request Input

Pause a Workflow and collect structured information from an assigned person before execution continues.

Request Input pauses a running Workflow to collect information that is required before the process can safely continue.

Use it for missing data, human verification, a structured correction, supporting information or other input that cannot be obtained reliably from the systems already available to the Workflow.

What happens in a live Workflow

When execution reaches Request Input, Lleverage:

1. evaluates the configured form and supporting context;

2. creates a Pending Request for the assigned user;

3. stores a resume snapshot for the Workflow;

4. pauses the run;

5. validates and records the submitted response;

6. resumes from the saved point with the submitted data available downstream.

The output includes the submitted values, provenance describing how form values were provided, and resolvedBy information for the person who completed the Request.

Configure only the information the process needs

Keep the form specific to the operational gap. A good Request Input tells the assignee:

• what information is missing;

• why it is needed;

• what evidence they should inspect;

• which fields are required;

• what will happen after submission.

The exact fields and form structure are defined by the Workflow. They are not a universal Request schema across Lleverage.

Assignment

Assignment is mandatory in a live Workflow. The current builder node exposes assignment to specific users, and only an authorised assignee can complete the Request.

Do not describe role-based assignment as a visible builder capability today, even though the underlying Request data model can represent role assignments.

Reopening input

A completed Request can be reopened in supported cases to replay execution from that handoff. Reopen the latest completed Request in the chain; earlier superseded Requests cannot be independently reopened.

Priority and SLA

Priority and an SLA deadline can be stored with the Request. The deadline does not currently trigger automatic escalation or at-risk/overdue transitions. Treat it as Request metadata unless your Workflow explicitly implements escalation behaviour.

Builder tests behave differently

In a builder test, the input form is handled inline and no real Request Inbox row is created. Assignment and Request authorisation are not enforced in test mode, and no Workflow Session is created for this Request flow.

That makes test mode useful for checking the form and downstream data path, but it does not prove that live assignment and Request handling are correct.

For the operator experience, see Run operations → Requests.