Explain the difference between start process and Start process link in Appian?
Explain the difference between start process and Start process link in Appian?
Answer
Both functions start a process model from an interface. The difference is whether the user sees the process’s forms. a!startProcess() runs the process from a saveInto and keeps the user on the current screen. a!startProcessLink() is a link that takes the user into the process’s start form and any chained forms.
1. a!startProcess(): start a process without leaving the screen
You call a!startProcess() from a component’s saveInto. The process doesn’t show its start form or any chained user tasks, so the user stays where they are.
- It’s often used for background work, such as sending emails, updating records or calling integrations.
- It can run asynchronously or synchronously, so it isn’t limited to background work.
- It returns process information. When it runs synchronously, it also returns process outputs.
onSuccess,onErrorandonIncompletelet you handle the result yourself.
Example: in an invoice management app, a user looking at a submitted invoice clicks “Send Payment Reminder.” Appian starts a process that emails the customer, and the user stays on the invoice screen.
2. a!startProcessLink(): start a process the user works through
a!startProcessLink() creates a link. Clicking it starts the process and opens its start form or first chained user task. The user can enter information and move through several chained forms. When they finish that first chain, the original interface reloads.
- You can pass process parameters.
- It has no
onSuccessoronErrorcallbacks. - It doesn’t support process autoscaling.
Example: in the same app, a user clicks “Create New Invoice.” The process opens a form where they enter the invoice details, pick a service provider and submit.
Side-by-side comparison
Feature | a!startProcess() | a!startProcessLink() |
|---|---|---|
Shows the start form | No | Yes |
Shows activity-chained forms | No | Yes |
User stays on the current screen | Yes | No, leaves until the form chain is done |
Passes process parameters | Yes | Yes |
Custom success and error handling | Yes | No |
Synchronous execution | Yes | No equivalent setting |
Autoscaling | Yes | No |
Which one to use
Use a!startProcess() when the user triggers an action that needs no input, like sending a notification, updating a record or running an integration.
Use a!startProcessLink() when the user has to fill in a form to start the workflow, such as creating an invoice, submitting a request or entering application details.
Appian Documentation
Check yourself
Question 1 of 3, on what the answer above covers.
- 1.An Appian application displays a list of invoices. When a user clicks "Send Reminder", the application should trigger a process model to email the customer without navigating away from the current interface.Which approach should the developer use?
- 2.An employee clicks "Submit Leave Request" in an Appian application. The system must start a process model and immediately display a form where the employee enters leave dates and a reason.Which function is most appropriate?
- 3.A developer creates a "Generate Report" button in an Appian interface. When clicked, it starts a process model. After successful execution, the interface should display a confirmation message using a callback.Which implementation is most suitable?