Getting Groovy With The Orchestrator

85%-95% of Orchestrations are no-code, however the rest require a low-code solution – Groovy fills this gap:

The following insight, including the screen shots, is the short version of an excellent presentation delivered by Larry Furino of ACBM Solutions, at the recent Quest JDE week .

Groovy is a programming language that is often used by Java developers, that can run on any platform.

So how can Groovy be used in Orchestrator?

  1. In the orchestration output (to grab and format output)
  2. In connectors (database and REST connectors) to manipulate output from connector
  3. Custom requests
Use Case #1: Groovy Data Requests JDE Orchestrator
Use Case #1: Reading Equipment Data from a Database

We can help train your staff on how to use JD Edwards Orchestrator. Learn more

Use Case #1: JD Edwards Orchestrator use Groovy Data Requests part2
Use Case #1: Reading Equipment Data from a Database, Continued
Use Case # 2 Define Inputs and Outputs JD Edwards Orchestrator
Use Case # 2 (image 1) Manipulating Orchestrator Output
Use Case#2: Define Inputs and Outputs JD Edwards Orchestrator - part 2
Use Case # 2 (image 2) Manipulating Orchestrator Output
Use Case # 3 Update JD Edwards Orchestrator Advanced Pricing
Use Case # 3 Update Advanced Pricing (Image 1)
Use Case # 3 Update JD Edwards Orchestrator Advanced Pricing
Use Case # 3 Update Advanced Pricing (Image 2) Note: No QBE On Screen

Talk To Us About JD Edwards Orchestrator Training 

email ndevr@ndevr.com.au or call +61 (3) 9865 1400