This page provides an overview of orchestration-related APIs.
The View Orchestrator provides data flow orchestration through on-premises function-as-a-service (FaaS). View Orchestrator runs independent pieces of code (steps) in an ordered manner within a user-defined sequence (dataflow), invoked by a request being received on matching a user definition (trigger).
- Step an independent piece of code mapping to a
dotnetbinary orpythonscript file - DataFlow an ordered sequence of steps outlining the entry step, and which steps to run based on the return condition of success, failure, or exception
- DataFlow Map a decision tree outlining each step and subsequent steps based on the result provided of the previous step
- Trigger a match condition such as an HTTP method and URL to which a data flow is mapped indicating what event should cause the execution of a dataflow map