Understanding the Capabilities of Orchestrator

Orchestrator for Quest

Hello JDE users and experts. I recently presented a detailed review of Orchestrator for Quest and the feedback was so positive, I decided to create a summary for anyone who may have missed the session.

TL; DR: The only downside of Orchestrator is that you can do so many different things with it, it can be a challenge to keep it all straight.

To help put some perspective on Orchestrator, I defined the following four categories of use cases:

Notifications: Orchestrator can send single notifications, notifications based on a watchlist, and notifications associated with an orchestration. Through the subscription setup process, you can send a notification using email, browser pop ups, the work center, or even SMS text.

Notifications can be setup on a schedule or put on a form through form extensions. Some examples:

•Time entry must be completed in 15 minutes (simple on scheduler).

•15 unprocessed credit approvals require attention (based on a watchlist).

•Oracle Sales Cloud quote 3234 changed to WON, Sales Order 12546 created (associated with an orchestration).

Internal Facilitations: This is just my invented name for orchestrations used in JDE to execute JDE. This is a newer capability, at least relative to the original integration uses cases, and it is REALLY EXCITING!! You can build orchestrations to execute a lot of things within JDE, and you have even more ways to trigger those orchestrations:

•Setup up your orchestration on scheduler,

•Setup your orchestration to execute based on a button added through forms extensions. You can pull the data from your current screen and have the orchestration go execute the next two screens for you!

•Direct call to B98ORCH. You can now execute Orchestrator directly out of a UBE or interactive program based on select conditions. Just call the B98ORCH function and identify your orchestration and parameters.

More examples:

•Put a customer on hold with the click of a button from the credit review screen then send a notification to sales.

•Set an equipment status as down and create an open work order for repair.

•Process an asset decommissioning with one click – Orchestrator executes all steps and any UBEs that are needed.

Inbound Calls: This is the most common introduction to orchestrator. Inbound calls are more about the direction of the call versus the direction of the data. These inbound calls might be:

-An IOT device collects data and calls an Orchestrator REST service to update a meter reading.

-A web store calls a service to get current inventory availability.

These calls are externally initiated but the data could really be going back to the caller or just inserting data into JDE by way of JDE. The called orchestration is capable of executing almost any JDE function plus direct data activities.

Outbound Calls: Outbound calls are orchestrations with JDE that initiate a call to an external API or data structure. It can be on a scheduler or on a button or within any JDE process that can call the B98ORCH function.

We built a series of outbound orchestrations for a customer that were triggered on a button. The button would call a set of 3rd party APIs to create a beginning configuration order. We could call different APIs, through B98ORCH, based on different data needs. Once created, the orchestration would then open that configurator website so the user could configure the product. We then used inbound orchestrations (services waiting to be called) to bring the data back into JDE.

Thanks for the read and let us know if we can help you start using the vast capabilities of Orchestrator!