Configuring the Workflow Engine in a Different Domain
You have the option of configuring a system in the workflow domain as theWorkflow Engine. Even if you link multiple domains with domain links, the transport workflows are still processed in the Workflow Engine of the local domain. This means that you cannot access transport proposals created in a different domain. If you want to be able to administrate the transport proposals of multiple linked domains in a single Workflow Engine, then you can define the Workflow Engine of a different domain to be the Engine of your own domain as well.
When you do this, all workflows processed in the selected Workflow Engine can be accessed from all systems, regardless of whether the Engine is configured in the local domain, or whether the domain is only linked to the local domain.
You have alreadyconfigured a Workflow Engine in a domain, and want to be able to use it from other domains.
All the functions of the transport workflow are processed locally in the Workflow Engine. All tasks are processed here and then sent to the logon systems of the users.
Therefore, for anyone who uses the transport workflow, you must create a user with the
To configure the Workflow Engine of a different domain, proceed as follows:
The transport workflow is active in your transport domain. You must now assign the relevanttransport administration authorizations.
See also:Deleting the Configuration of the Transport Workflow
For more information on transport domain administration, seeTransport Workflow (Administration).
For more information for the development team, seeTransport Workflow (Development).