Disable an Orchestrator touchpoint to prevent processes from running on that Orchestrator touchpoint. Disabling an Orchestrator touchpoint does not affect the Orchestrator library. That is, designers can select an Orchestrator with a disabled touchpoint on the Library tab and can define automation objects.
You disable an Orchestrator touchpoint when affected external objects are unavailable. Consider the example of processes that deal with Service Desk or with an external database. At certain times, those components are down for maintenance. You can prevent the running of processes that interact with components that are temporarily unavailable. When the external components become available, you enable the Orchestrator touchpoint. Then, scheduled processes that use these external components can begin running again.
You can disable the Orchestrator touchpoint that you select on the Domain hierarchy.
Follow these steps:
|
Copyright © 2014 CA.
All rights reserved.
|
|