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:

🔹 Start Process Smart Service

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

🔹 Subprocess Activity

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

🔹 Process Messaging

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

2. Starting a Process from an Interface

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

🔹 a!startProcess()

1. Expression function used in a saveInto (e.g., button) to start a process.
2. Great for unattended operations and works with autoscale.

🔹 a!startProcessLink()

1. Launches a process and navigates the user into initial chained forms.
2. Shows start forms or chained user tasks.
3. Does not support autoscaled processes.

🔹 Record Actions

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

3. Starting a Process Outside Appian

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

🔹 Web API calling the Start Process Smart Service

1. External systems call a Web API, which in turn starts an Appian process.

🔹 Appian RPA

1. Use Appian Robotic Process Automation to start a process.

🔹 Email

1. Sending an email can trigger a process (only for non-autoscaled processes).

🔹 Exposed as a Web Service

1. Make a process model callable as a web service to start from another system.

4. Automatically Start a Process

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

1. Schedule start events in a process model (e.g., daily job or periodic sync).
2. Useful for batch jobs and automated workflows

5. Starting from Tempo or Sites

For end-users accessing Appian through Tempo or Sites:

🔹 Record Actions

1. Exposed record actions allow users to start processes contextual to data.

🔹 Application Actions

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