The fulfillment flow has two distinct responsibilities: the technician must enter installation or equipment data, and the downstream activation system must receive that data automatically. A Manual Task with an OmniScript handles the guided human interaction, while a Callout orchestration item sends the completed information to the external system once the task is finished. The key is to represent the requirement in the same layer where Salesforce evaluates that business state. A Milestone does not invoke the downstream platform, and a Push Event is intended for externally initiated completion rather than guided technician entry. Keeping human and automated work as separate orchestration items gives clear ownership and error handling. This avoids mixing customer-facing product logic with downstream technical state or using integration code as a substitute for catalog and orchestration design. When the model is aligned correctly, the platform can validate the request, retain the required lifecycle information, and generate the appropriate downstream action without redundant processing. That improves auditability and makes later changes easier because administrators can adjust the relevant metadata rather than reworking multiple custom components.

Study Guide Reference:Manual Tasks; OmniScript; Callout orchestration; technician workflow; activation integration.