Your search did not match any results.
We suggest you try the following to help find what you're looking for:
The Orchestrator transforms how you use your entire JD Edwards system. Orchestrator automates the collection, processing, and exchange of data. There are many patterns for Orchestrator including automation, integration, notifications, and capturing data from IoT or other sources, all of which lead to automation. For more information about Orchestrator features, click the Tools Release below to access the Net Change guide or click on a specific topic to view the supporting content.
This feature allows the orchestration designer to specify, in other words to "assert," the values that are expected to be produced by an orchestration.
This feature provides the system administrator with more control over configuring the associations between EnterpriseOne enterprise servers and AIS servers.
This feature enables the orchestration designer to use variables in the definition of the REST connector when uploading files.
This feature allows the system administrator to configure user sessions to not initialize an AIS session unless they are needed, thus conserving system resources.
When hosting external content within the EnterpriseOne user interface, this feature improves the user experience by enabling EnterpriseOne and third-party applications to share certain data, such as session information.
This feature provides performance optimizations for Orchestrator to be able to retrieve very large data sets from EnterpriseOne tables. The orchestration designer may also choose to have the output written to disk and to exclude it from the orchestration response.
This feature improves the performance of implementations that request and receive very large data sets from the AIS server. For example, it is possible to compress the output of an orchestration that uses a data request to return a very large data set, possibly thousands of rows and thousands of bytes of data. Using the built-in capabilities of the HTTP server to compress this data, the size of the payload that is actually transmitted over the network can be greatly reduced, thus resulting in better performance.
Extending the capabilities of the EnterpriseOne Orchestrator to securely integrate with third-party systems and cloud services, authentication to an external REST service has now been made possible through X.509 public key certificates. This enhancement broadens the range of third-party REST services that orchestrations can securely invoke.
The Application Interface Services (AIS) server is a powerful tool for automating inbound and outbound transactions of EnterpriseOne, and when implemented at a large scale, that automation is even more valuable. For some implementations, orchestration designers require control over the order in which those transactions are executed, for example, they might want to ensure a first-in, first-out (FIFO) processing. This enhancement enables the orchestration designer to specify whether an orchestration is processed in a single-threaded queue, a fire-and-forget multithreaded queue, or a default queue. In this way the orchestration designer has more control over the runtime processing of orchestrations.
Orchestrations can be configured to accept input from the CSV files stored on an FTP server. This enhancement enables the orchestration designer to designate columns of data within those CSV files as indicators of grouped data, thereby giving the ordinarily flat CSV data a certain amount of structure. With this new feature, orchestration designers can use the ordinarily flat structure of a CSV file to create more hierarchical inputs for orchestrations.
In some use cases, it is useful to echo the orchestration inputs in the output (the REST response). For example, an orchestration that retrieves a list of open sales orders for a customer might take the Customer Number as an input, and the orchestration designer might want to include that Customer Number in the output. With this feature, the orchestration inputs will be shown on the Outputs page, and the orchestration designer can easily select to include them in the output.
This feature enables you to capture a record of your orchestrations as a printed document or as a PDF file. The document will include a summary page with the graphical representation of the orchestration flow and supplemental pages with details regarding orchestration inputs, variables, outputs, scheduling, and so on. The supplemental pages also provide details on each orchestration element, including information about transformations and error handling.
Orchestration steps will now be expandable and collapsible, enabling the orchestration designer to review and edit the child orchestration. When an orchestration is included as a connector or a notification, the notification or connector can first be expanded, and then the orchestration within can be further expanded if required. The system also handles multiple levels of orchestration nesting, including nesting associated with recursive scenarios. Furthermore, the system offers an expand-all functionality, as well as a collapse-all functionality.