What happens when we run as whoever started the process and run as whoever designed this process model?
What happens when we run as whoever started the process and run as whoever designed this process model?
Answer
Unattended activities in Appian, such as automated smart services, can run under different users’ security contexts. The Assignment tab gives you two options:
- Run as whoever started the process (process initiator)
- Run as whoever designed the process model (process designer)
The option you pick decides whose security permissions Appian uses when it executes the node.
1. Run as whoever started the process (process initiator)
With this option, the smart service runs with the permissions of the user who started the process. The node works inside the initiator’s security context, so the initiator needs access to every object or resource the node uses. If any of those permissions are missing, the node can fail.
For example, John, a loan officer, starts a Loan Application process. One of its smart services accesses a secured document. If the node is set to Run as whoever started the process, Appian checks that operation against John’s permissions. If John doesn’t have access to the document, the operation may fail.
2. Run as whoever designed the process model (process designer)
With this option, the smart service runs with the permissions of the process model’s designer.
In Appian, the designer is the user who last saved or published the process model. That may not be the developer who first built it.
The node runs in the designer’s security context, so the designer needs whatever permissions the operation requires. This option is useful for background activities that need access ordinary initiators don’t have.
For example, John starts a Loan Application process that includes a smart service needing a restricted document. If the node is set to Run as whoever designed the process model, Appian checks the operation against the designer’s permissions instead of John’s. If the designer has access, the operation can succeed even though John doesn’t.
3. Example: Hotel Booking Application
Take an Event Booking Application where an Event Manager creates an event and requests hotel rooms. The business flow looks like this:
- The Event Manager creates an event.
- The Hotel Booking process starts.
- The process runs a Send E-Mail smart service.
- The service emails the Hotel Staff group to ask about room availability.
On the security side, the Event Manager can start the Hotel Booking process but can’t see the restricted Hotel Staff group. The process designer does have access to that group.
Scenario 1: Run as whoever started the process
The Event Manager starts the Hotel Booking process, and the Send E-Mail smart service is set to run as the process initiator.
Result: the email node may fail, because the Event Manager doesn’t have the permissions needed to resolve the restricted Hotel Staff group as recipients.
Scenario 2: Run as whoever designed the process model
This time the same Send E-Mail smart service is set to run as the process designer.
Result: the email node can run successfully, since the designer has access to the Hotel Staff group.Changing the execution context doesn’t guarantee success on its own. Whichever user you select still needs the permissions the smart service requires.
4. Key differences
Feature | Process initiator | Process designer |
|---|---|---|
Executes as | User who started the process | User who last saved or published the process model |
Permissions used | Initiator’s permissions | Designer’s permissions |
Security access | Limited to the initiator’s access | Limited to the designer’s access |
Typical use | Operations the user is authorized to perform | Controlled background operations |
Possible failure | Initiator lacks the required permissions | Designer lacks the required permissions |
5. How to configure the Run As option
- Open the process model in Appian Process Modeler.
- Double-click the smart service node you want to configure.
- Go to the Assignment tab.
- Select Unattended execution.
- Choose either Run as whoever started the process or Run as whoever designed the process model.
- Save and publish the process model.
6. Important considerations
- The setting controls the execution context of the configured unattended activity only, not the whole process model.
- Choosing the process designer doesn’t give the node administrator access.
- The process designer can change whenever another account saves, publishes, or deploys the process model.
- Use the process initiator when the operation should respect the starting user’s permissions. Use the process designer only when the business requirement justifies a different security context and the designer has the permissions it needs.
References
Check yourself
Question 1 of 3, on what the answer above covers.
- 1.In an Event Booking Application, an Event Manager starts a process that sends an email to the Hotel Staff group. The Send E-Mail smart service is set to "Run as whoever started this process". The Event Manager cannot access the Hotel Staff group, but the process designer has the required permissions, and the email node fails due to insufficient permissions. What is a possible solution?
- 2.John builds a process model with an unattended smart service set to "Run as whoever designed this process model". The model is later deployed to Production by a deployment service account, which becomes the process model's designer in that environment. Whose permissions does the smart service use in Production?
- 3.In a Loan Management Application, a Loan Officer starts a process to update loan information. The business requirement says the update should succeed only if the Loan Officer has the required permissions. The process designer has broader permissions than the Loan Officer. Which setting fits the unattended smart service best?