Using the Process Simulator with a Server Component
You cannot use the Process Simulator to test a long-running Workflow Process or a Workflow Process that invokes an asynchronous server component, such as, one of the following: Workflow Process Manager, Server Request Broker, Assignment Manager, or Communications Server.
Server components that execute in-line with the current Workflow Process can be invoked. For example, let's say you want to use the Outbound Communications Manager Business Service to send an email.
-
If you set the Process Mode method argument to "Local", it will send the email in the same context as the Workflow Process and will work fine.
-
However, if you set the Process Mode argument to "Remote", then it sends a request to the Server Request Manager to call the Outbound Communications Manager as a background job (in another process). This cannot be simulated.
Therefore, the technique for testing via Simulation is to set the Process Mode argument to "Local" and after you are sure that it works, you can change it to "Remote" if that is what you actually want.
The same applies to any similar processing scenario, where there is almost always a synchronous and an asynchronous request. The exception is Server Request Broker, where typically the server does something asynchronously.