Ways to Start a Process

1.Starting a Process From Another Process

These are the methods you can use inside a process model to start another process:

A smart service node that launches another process.
Works asynchronously (continues current flow) or synchronously (waits for results).
Can dynamically choose which model to start.
Recommended in most cases.
Compatible with autoscaling.

A BPMN activity that starts another process as a subprocess.
Creates a parent–child relationship between the two processes.
Allows passing variables by reference.
Useful for reporting, chaining into a user task, or preserving security context.
Not compatible with autoscale.

Use Send Message Event or End Event to trigger another process model that listens for messages.
Useful for event-based or loosely coupled process triggers.
Generally less capable than Start Process Smart Service and has more limitations.

You can kick off a process directly from UI interfaces in these ways:

Configure a record type to allow record-based actions that start processes (like “Create” or “Update”).
Can also be embedded in interfaces using a record action component.

These methods allow external systems or events to launch Appian processes:

You can have Appian start processes on a schedule or at specific times without manual or external triggers.

For end-users accessing Appian through Tempo or Sites:

Expose process models as actions in the Actions tab in Tempo or as Site pages.
Good for user-initiated flows.
Only for processes without autoscale.