JD Edwards · Excel · Orchestrations · AI

The spreadsheet is already the interface. Make it safe.

JDE Citizen Developer is a practical resource for JD Edwards teams who want business users to move faster without letting automation outrun governance. Excel can call Orchestrations. AI can call tools. Users can build workflows. The question is whether identity, audit and control come along for the ride.

Start with Excel + JDE What is this?
1
trusted identity
3
safe boundaries: Excel, Orchestrations, AI
0
shared macro passwords
Excel
workbooks
JDE
Orchestrations
SSO +
MFA
AI
agents
ControlledAutomation
The argument

Citizen development is not the absence of IT. It is the presence of better boundaries.

The winning model is not to stop users from using the tools they already understand. The winning model is to give those tools a governed path: identity at the door, Orchestrations at the boundary, audit behind the action, and AI only where the work is sanctioned.

1

Keep the familiar front end.

Excel, VBA and business-user tools are not going away. Make them safer instead of pretending they do not exist.

2

Use JDE-approved services.

Orchestrations are the natural boundary: typed inputs, real JDE users, predictable actions and existing audit semantics.

3

Add modern identity.

SSO, MFA and tokens turn workbook automation from a convenient shortcut into an accountable enterprise process.

Guides

Read the playbook

A growing library of practical guides, one theme: give business users speed without giving up control — and, increasingly, give AI the same treatment.

Governed AI Capabilities

Why AI projects stall at approval — and why the answer is to give an AI capabilities the business chose, not access it has to be trusted with.

Read guide

Who decides what AI can do?

In most organisations the honest answer is nobody, quite. Approval, audience and withdrawal — giving the boundary an owner.

Read guide

AI across multiple business systems

The question a user has is almost never confined to one system. The tools they were given always were.

Read guide

What is a JDE Citizen Developer?

A practical definition for JD Edwards sites: business-led automation, governed by IT, executed through approved JDE services.

Read guide

Excel and JDE Orchestrations

Why Excel is the unavoidable JDE front end — and how to turn it from a workaround into a controlled orchestration client.

Read guide

JDE Orchestration Governance

Rules, rights, templates and audit trails for keeping Orchestrations powerful without making them dangerous.

Read guide

AI Agents and JDE Orchestrations

The safest boundary for AI in JD Edwards is not raw database access. It is the Orchestrations you already approve.

Read guide

MCP for JDE

How Model Context Protocol servers expose JDE work to AI agents as small, named, auditable tools.

Read guide

Identity for Excel Automation

When a spreadsheet can call real business services, authentication becomes part of the transaction itself.

Read guide

From Spreadsheet to Controlled Automation

A maturity path from ad-hoc workbooks to secure, repeatable, auditable enterprise workflows.

Read guide

MRO Data Hygiene in JD Edwards

Duplicate parts, inconsistent descriptions and ageing stock are the slow, expensive failure mode of MRO catalogues. They are also the most solvable.

Read guide

Modernising Authentication for Legacy Windows Applications

VB6, PowerBuilder, Delphi and older .NET pre-date modern identity. The gap between their authentication and current security policy is real, growing and inspected.

Read guide

JDE Data Access Patterns

ODBC, Orchestrations and AIS — three different patterns, three different sweet spots. Choosing the right one is half the battle.

Read guide

Bulk JDE Updates Without Direct SQL

When 500 records need updating, the temptation is to bypass JDE and let SQL do the work in seconds. It nearly always costs more than it saves.

Read guide
Product fit

The resource site explains the problem. The Beanstalk product family solves it.

Beanstalk supplies identity. JDE Orchestration Workbench supplies bulk execution. AI MCP Servers supply agent tools. BrainStorm supplies the full conversational front end. Composer supplies the governed capability layer that decides what AI is allowed to do at all. Together they form a practical bridge from spreadsheet habit to governed automation.

View product family
Related products

Tools for the controlled-automation stack

Composer

A governed capability layer for agentic AI: create reusable business capabilities, control who may use them, publish them deliberately.

Explore Composer

Beanstalk Authentication Broker

Modern SSO, MFA and token-based identity for Excel, VBA and other COM-capable Windows tools.

Explore Beanstalk

BrainStorm

The complete AI app for JD Edwards: chat, RAG, MCP and Orchestrations under the user’s own JDE identity.

Explore BrainStorm

AI MCP Servers

Small, focused MCP servers that expose JDE Orchestrations and safe file workflows to approved AI agents.

Explore AI MCP Servers

JDE Orchestration Workbench

Run Orchestrations in bulk from a spreadsheet-style grid: row in, row out, status and response per line.

Explore Workbench

ESI JDE ODBC Driver

JDE-aware ODBC access with credentials, table security, decimals, dates and UDC handling built in.

Explore ODBC Driver

MRO Storeroom & Search

Fast full-text search over JDE MRO items, locations, branch records and purchase orders.

Explore MRO Search