Have you ever had the feeling that you are missing out on something with Orchestrator?
You see its full potential, but you feel like you’re just “scratching the surface.” You would love to have time to read all the documentation and learn about those “new” features that your JDE version brings, but the day-to-day work consumes your time.
It is frustrating to intuit that you could solve much more complex problems, but not knowing exactly how to take it to the next level. Does this sound familiar?
That feeling is precisely what we addressed last week in an advanced Orchestrator training session. And I have to confess: every time I teach one, I reaffirm my passion for this. Not only for the pleasure of seeing the “light bulb go on” in the faces of the attendees when they discover a new capability (“So, it WAS possible to do THAT!”), but because I also continue to learn. Every question, every use case, pushes me to deepen my knowledge more and more.
For me, teaching is the best way to learn.
As I mentioned to you in the past few days, this past Monday, October 20th, we participated in the JDE Talks event, where we presented several practical examples focused on Orchestrator’s Workflows and Widgets.
Just as I promised, I have prepared a complete summary with all the technical details and use cases that we covered. It is perfect:
Here it is.
Use Case 1: Accelerating Project Approval (Say Goodbye to Emails!)
Does the endless waiting and stack of emails required to get approval and move a development project to Production (PD) sound familiar? This process, vital for quality control, often becomes a tedious bottleneck that delays the deployment of solutions. Communication is scattered, and manual approvals generate friction and oversights.
We transform this manual task into an automated, direct, and transparent workflow. We use Orchestrator to create an instant and traceable approval system that eliminates reliance on email. This not only speeds up the move to PD but ensures the approval is made by the right person at the right time.
How We Achieve It:
Use Case 2: The Inventory Guardian: Automated and Reactive Purchase Approval ️
Allowing inventory to dip below safety stock is a costly mistake. Constant manual verification and reactive creation of purchase orders are slow processes that risk the supply chain. We need a system that proactively monitors levels and instantly launches the replenishment process, minimizing human intervention.
We have created a fully automated and scheduled “Inventory Guardian.” This Orchestrator runs periodically, identifies stock shortages, and intelligently initiates a purchase approval workflow, ensuring quick and authorized replenishment without the need for manual paperwork.
How We Achieve It:
Use Case 3: The Power of Widgets ⚡
In today’s business environment, time is the scarcest asset. Users spend valuable minutes navigating menus and running reports to answer basic questions like: “How are today’s sales looking?” or “How many purchases were made?”. Critical information is often trapped deep within the system.
Transform the JD Edwards login screen from a static list of menus into a Dynamic Operational Command Center. Using Orchestrator as the data engine, we create Widgets that offer an instant, big-picture view (the “what and why”) of key business operations.
To feed this high-impact dashboard, we design simple yet powerful Orchestrators that extract key intelligence without running a single report:
The creation of Widgets using the results of these Orchestrators, available since Tool Release 9.2.9.4, is so simple and intuitive that the true revelation is the final result. Imagine seeing, right upon logging in, a dashboard that tells you in 3 seconds what’s selling most, how many purchase orders were created today, and where you should focus your attention. Without running a single report!

I hope this summary is as useful to you as it was for me to prepare and share this session.
Now I’d love to hear from you: What did you think of these use cases? Is there a challenge in your company where you think something like this could apply? ¿Have any technical questions arisen?
Simply reply to this email or contact me directly. I would love to read your impressions and talk about it!
Best regards,
Mario Garcia