In a recent article for the Quest Oracle Community website, Shelby Klingerman explores the variety of enhancements that Oracle JD Edwards has made to the Orchestrator tool within the last year.
Following Oracle’s move to a Continuous Delivery model in 2017, we’ve seen a host of new product features and developments. According to the annual Quest Community survey, 57% of JDE E1 users claim their company has plans to begin using Orchestrator in the near future. So, what can they expect?
Containing a host of live demonstrations and insight, Klingerman’s article highlights some key developments:
Expanded Orchestrator Inputs and Outputs
Orchestrator is now capable of taking input directly from comma-separated value (CSV) files. This allows users to easily input large volumes of data stored in a spreadsheet as the input source for an orchestration. This update also allows for inputs to also be provided as JSON or XML (with some limitations still to be expected in accepting XML beyond single level structures).
Orchestrator Messages and Notifications
Multiple action links can now be inserted to various applications. Designers can now put pre-text and post-text around those links to not only make the link available but also provide more user-friendly context around those links. Additionally, release 9.2.3.3 brings the ability to attach JD Edwards reports to these messages and is compatible with the JD Edwards container on iPad, providing further convenience for JDE E1 users.
Launching Orchestrations from EnterpriseOne Applications and Business Functions
Users can now launch orchestrations from EnterpriseOne applications by creating a JD Edwards form extension. This addresses the need to customize, with the form extensions acting as alternatives to traditional customizations. Similar functionality has also been made available as a business function for launching orchestrations and notifications; allowing users to launch an orchestration or notification based on any detailed event anywhere in the JD Edwards system.
Multiple Output Steps for Application Stack
Traditionally, the returning of data has been limited to the last form in an application stack. Enhancements now allow for data to be returned from any and all forms along the application stack, supported by use of the Process Recorder.
The last twelve months have demonstrated the JDE strategy of continuous evolution can deliver genuine value to the installed base. Further developments for the Orchestrator tool are planned for the coming year, adding further features and integrations.
Related resources:
JD Edwards EnterpriseOne Testing Innovation Best Practice Guide
