Workday education materials prefer Orchestrate for many new integrations and reserve Studio for complex logic/Java. Extend belongs when workers need in-tenant pages or custom business objects.
Evidence pack every AI recommendation must include
| Question | Keep Studio | Move Orchestrate | Rebuild Extend |
|---|---|---|---|
| QuestionLarge batch / streaming transform? | Keep StudioOften | Move OrchestrateOften no per education comparison | Rebuild ExtendRarely |
| QuestionEvent-driven API sync? | Keep StudioMaybe | Move OrchestratePreferred | Rebuild ExtendIf UI/BO needed |
| QuestionCustom Java beans? | Keep StudioYes | Move OrchestrateLimited | Rebuild ExtendDifferent model |
| QuestionWorker-facing pages / custom BOs? | Keep StudioNo | Move OrchestrateNo | Rebuild ExtendYes |
Attach measured volumes and failure history. An assistant memo without that table is opinion.