Your Orchestrations are already the beginning of an agentic execution layer.
Turn existing JD Edwards Orchestrations into bounded, discoverable tools that agentic AI can call under existing security and governance.
Orchestrations are a strong bridge into agentic AI because they already have named inputs, named outputs and an intentional business purpose. The difficult work is often not creating a new AI action; it is publishing the right existing operation to the right user and agent.
From orchestration to capability
Composer can package one or more system actions into a reusable governed capability. BrainStorm can discover and invoke those capabilities conversationally. MCP can expose them to other agents.
Keep the permission model
The agent should not receive broader JDE authority than the signed-in user. The best upgrade preserves the rights and audit model already understood by CNC and security teams.
Good first examples
- purchase-order inquiry or approval
- supplier AP position and aging
- document-status investigation
- controlled master-data lookup or update
From capability design to execution
Composer packages bounded business capabilities, BrainStorm gives users the agentic interface, and JDE Citizen Developer covers the design pattern in more depth.