JDE Orchestration Workbench
Row in, row out: bulk-execute JDE Orchestrations from a familiar spreadsheet-style grid — without writing client code.
JD Edwards Orchestrations are an excellent foundation for automation: typed inputs, predictable outputs, and curated access to JDE. But the standard Orchestrator Studio is built for designing and testing one orchestration at a time. The moment you need to call the same orchestration over a thousand rows of input — a mass price update, a batch lookup, a bulk status change — you are writing client code.
JDE Orchestration Workbench fills that gap. Open the workbench, pick an orchestration, paste or load your input rows into the grid, and run. Each row gets its own status, its own response, its own retry. No client code. No infrastructure. No tickets.
- Spreadsheet-style grid, familiar to anyone who's used Excel.
- Per-row status, success/failure, response payload.
- Reusable templates for repeating workloads.
- Easy retry of failed rows without re-running successful ones.
- Uses your existing JDE Orchestrations — no JDE changes.
What the workbench gives you
- A real grid. Type, paste from Excel, load from CSV, or pull from clipboard. Columns map to orchestration inputs by name.
- Per-row execution. Each row is one orchestration call. Per-row status (pending, running, success, failure) and per-row response are displayed inline.
- Retry — the bits that need it. Failed rows can be retried without re-running the successful ones. Useful when an upstream service blips, or when you fix a data error in one row.
- Templates. Save the column layout, input mappings, and any defaults for a workload, and reuse it next month. No re-typing.
- Direct AIS. The workbench is a straightforward AIS client — no proxy, no middleware. The orchestrations execute under the JDE user who logged into the workbench, with full JDE auditability.
Typical workflow
- Sign in to the workbench with your JDE credentials.
- Pick an orchestration from the list the workbench discovers.
- Paste your input rows into the grid (or load from a saved template).
- Click Run. Watch the status column update as each row executes.
- Inspect per-row results. Retry any failures. Export the result table.
The whole loop is what a power user would build for themselves — if they had time to write the client. They don't, and they shouldn't have to.
For CNC & security
- The workbench is a normal AIS client. There is no escalation, no separate service account, no shared connection pool. Every call is made under the signed-in JDE user.
- Orchestration security applies: if the JDE user can't call an orchestration in Studio, they can't call it in the workbench either.
- Audit trail is exactly what AIS produces — the same audit the rest of your JDE landscape uses.
- No new infrastructure to certify. The workbench runs on a normal Windows workstation.
System requirements
- OS
- MS Windows (x64)
- JDE releases
- JD Edwards EnterpriseOne 9.1, 9.2 (any TR with AIS)
- AIS server
- Reachable from the workstation
- Orchestrations
- Standard or custom, including those built in Orchestrator Studio
Licensing
Perpetual per user + computer licence — no time limit. Order, or see the pricing page for current pricing.
Common JDE Orchestration execution questions
These pages explain the specific use cases where Orchestrations are already built but users need a practical way to run them repeatedly, safely and visibly.