Microsoft uses the word action for several different things in processes – for a type of process and for steps within processes. We looked at action steps earlier in this chapter. In this section, we will focus on action processes.
Action processes are like workflows in their capabilities in terms of what can be performed with step; in other words, action processes can use conditions, and can create and update records.
Action processes differ from classic workflows in the following ways:
- Action processes cannot be triggered automatically.
- Action processes are invoked from other components.
- Action processes can have input and output arguments.
- Action processes are associated with a single entity or can be set as global (not associated with any entity).
- Action processes always run under the security context of the calling user.
- Action processes always run synchronously, in other words, in real time...