GETTING GROOVY WITH THE ORCHESTRATOR

Groovy, Orchestrator, and JD Edwards

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, and that can run on any platform. (Learn more about Groovy here)

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

Get in touch if you’d like our help getting Groovy within Orchestrator, with a project, or training for your staff.

Use Case #1: Reading Equipment Data from a Database
Use Case #1: Reading Equipment Data from a Database
Use Case #1: Reading Equipment Data from a Database -part2
Use Case #1: Reading Equipment Data from a Database, Continued
Use Case # 2 Manipulating Orchestrator Output
Use Case # 2 (image 1) Manipulating Orchestrator Output
Use Case # 2 (image 2) Manipulating Orchestrator Output
Use Case # 3 Update Advanced Pricing
Use Case # 3 Update Advanced Pricing (Image 1)
Use Case # 3 Update Advanced Pricing
Use Case # 3 Update Advanced Pricing (Image 2) Note: No QBE On Screen

ADDITIONAL JD EDWARDS 9.2 RESOURCES

Manage payment times reporting from JD Edwards
12/01/2021

Managing Your Payment Times Reporting Scheme Obligations From JD Edwards

Quest JDE Dive Deep Conference 2021
11/03/2021

Deep Dive on Dive Deep – 4 Part Special

JD Edwards Release 22 - Applications Update Quest Conference 2021
11/03/2021

JD Edwards Release 22 – Applications Update