Standard Order
This is the normal flow of events through standard order fulfillment with no exceptions. The sequence is shown in the following diagram:
Standard Order Fulfillment–Successful Completion Sequence
- The order is submitted from Order Entry through the Orchestrator Submit Order HTTP protocol. Note that this might use intermediate service layers.
- The orchestrator sends a request to cache to store the order. The order now has pending status.
- Cache saves the order and returns a response to the orchestrator.
- The orchestrator sends a request to Automated Order Plan Development to analyze the order and design an execution plan.
- Automated Order Plan Development sends a response back to Orchestrator with the execution plan definition. The orchestrator then generates a plan based on this definition. The order now has execution status.
- The orchestrator sends a request to cache to store the plan.
- Cache saves the plan and returns a response to the orchestrator. The plan now has pending status.
- The orchestrator changes the plan status to execution and begins invoking process components in the correct sequence. This is repeated for each plan item.
- The process component returns a response to the orchestrator for each invocation.
- Once all plan items have been completed, the plan is set to complete status. The orchestrator sends a request to the cache to change the order status to complete for archiving. The order status then goes to Complete in Orchestrator.