Conversational JDE Orchestrations
Let users invoke approved JD Edwards Orchestrations conversationally instead of building a new UI for every task.
The orchestration-first interface
Orchestrations are already the right unit of controlled JDE automation. BrainStorm makes them reachable through conversation, so the business can ask for outcomes instead of yet another screen.
The model can discover what is available, inspect the required inputs, ask clarifying questions and call the orchestration with a structured payload.
- Same AIS surface.
- Same JDE user identity.
- Same orchestration security.
- No direct database bypass.
Fewer small applications to build
Instead of building a custom mini-application for every small workflow, you can expose the workflow as an Orchestration and let BrainStorm become the interaction layer.
One of four ways to package a capability
Orchestrations you have already built join the same governed catalogue as the other Skills — and for many everyday needs, one of the other kinds is quicker to create. Reading a name from the Address Book for a given AB# can be an Orchestration, in maybe just under two hundred clicks; a SQL Composition expresses it in one readable line. BSFN Compositions run JD Edwards’ own business logic, and Motif Compositions complete whole transactions — all published, group by group, through Composer, and all reachable in the same conversation.
See where this fits in the product.
This supporting page explains one search intent in detail. The main BrainStorm page gives the full product overview, related use cases, licensing and enquiry path.
Back to BrainStorm