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.
JD Edwards Extensibility Framework has been enhanced to enable users to start a workflow process from within a logic extension. This enhancement provides the designer more control over how workflow processes are started, integrates machine and human automation, and simplifies the process of developing and deploying workflows without the need for customizations
This feature expands the capabilities of the Orchestrator REST connector by adding the ability to send multipart requests that do not include file attachments.
Launching an orchestration from a Form Extension has been enhanced, allowing business analysts to provide inputs to an orchestration that are not on the form. This enhancement enables users to automate applications and business processes without deep technical knowledge. It also enables rapid development and deployment of automated solutions.
When launching orchestrations from the EnterpriseOne user interface, including composed pages or form extensions, this feature provides a simple tabular user interface for end users to provide inputs to the orchestration, including rows and columns of data.
JD Edwards EnterpriseOne Orchestrator Studio has been enhanced with the ability to export and save workflows as a zipped file, which can then be easily imported into a different EnterpriseOne system. For example, customers who are running multiple instances of EnterpriseOne might develop a workflow in one instance, export the workflow, and then import it into other instances.
This feature provides two enhancements to the Orchestrator cross-reference step. First, cross-references can now be bidirectional: inbound or outbound. Second, you can now use the Third Party App ID field to refine the cross-reference mapping between EnterpriseOne data and external systems.
JD Edwards customers can now easily create and delete workflows from Orchestrator Studio without having a Windows development client and developer skills. This capability empowers business analysts to accelerate the development of workflows entirely from a web browser, thereby saving time and effort in managing workflows.
The Orchestrator Studio has been improved to save the layout of workflows in a more precise way. This enhancement eliminates the time and effort of the workflow designer in realigning the individual components of workflows every time they are saved and reopened, thereby optimizing the workflow design process.
Orchestration designers and users may want the behavior of an orchestration to change depending on the environment in which it is executed. Environment properties allow the same orchestration to run differently based on records configured for each environment. For example, a database connector may connect to an external database with credentials that are different depending on whether the orchestration is running in a development, test, or production environment.
Logic extensions has been enhanced with the ability to call EnterpriseOne business functions. This capability enables business analysts to leverage the rules and logic from existing business functions within logic extensions. This new capability extends JD Edwards Extensibility Framework to meet new business requirements and opportunities without the technical burden associated with traditional customizations.
This enhancement enables orchestration designers to include formatted text in the body of orchestration and notification messages. The recipients then experience messages that are as visually appealing as they are effective. Messages can now carry a higher degree of branding through the use of rich formatting and images.
This enhancement provides orchestration designers the additional capability to specify "null" as a criteria. The designer can create orchestration rules that evaluate fields and perform a different orchestration path if the field is null.
Diagnostic tools for logic extensions aid the business analyst during the development and testing of logic extensions to ensure that they meet the defined business requirements. The diagnostic tools provide the business analyst visibility into the values of variables and the execution path of a logic extension in real time.
With the cumulative enhancements up to and including Release 22, Orchestrator has comprehensive capabilities for managing files. This enhancement extends those capabilities by enabling orchestrations to manage files that are generated by EnterpriseOne reports.
This feature provides the orchestration designer with an API to access files that are stored on the root temporary directory of the AIS Server. This capability gives the orchestration designer more control over data that is stored in files during the processing of an orchestration, particularly for files that persist after an orchestration session completes.
This feature enables the orchestration designer to define assertion criteria that is used to evaluate all rows returned from a step, even if the number of rows is unknown or variable.
This feature enables the orchestration designer to specify default values for orchestration inputs that are in an array.
This feature enables orchestrations to accept files from the response from external REST calls. Orchestrator is capable of making outbound calls to external REST APIs. Sometimes the response from those REST APIs contains file output. This enhancement provides the orchestration designer more control over saving and naming that file output for use in subsequent orchestration steps.
This feature provides a setting in Orchestrator Studio that enables the orchestration designer to ignore the summary row when processing a form request.
This enhancement extends enables orchestrations to be launched from other areas of the EnterpriseOne web client, such as composed pages. This new capability extends the power of orchestrations and notifications to even more areas where users will benefit from simplified and automated business processes within the context of their EnterpriseOne user interface.
This enhancement allows an orchestration designer to specify a response message that is displayed to the end user when an orchestration is launched from the EnterpriseOne user interface. It includes a custom message, indicating whether the orchestration completed successfully, with warnings, or with errors.
This enhancement extends the power of Orchestrator to automate EnterpriseOne transactions to include managing attachments (media objects).
This enhancement adds the EnterpriseOne runtime environment to the list of system values that are available to an orchestration.
This enhancement provides information on Orchestration processing status by displaying Orchestration errors and warnings. Additionally, users can see the custom message configured in Orchestrator Studio.
This enhancement expands the capabilities of Orchestrator by allowing files as orchestration input and output. Files can be provided directly as orchestration input by including them in a multi-part form data REST call from the system that is invoking the orchestration.
This enhancement provides a new Workflow Studio, accessible in Orchestrator Studio, which provides an easy-to-use, modern user interface for creating and editing workflows without the need for a development client.
This feature provides two REST APIs on the Application Interface Services (AIS) server: one API to retrieve lists of EnterpriseOne objects, such as programs, reports, and tables; and another API to list and optionally to execute EnterpriseOne business functions.
The logic extensions feature further expands the capabilities of the extensibility framework by allowing you to use the familiar syntax of the JD Edwards Event Rules language to create custom logic without the need for a development client and without the need to build and deploy a package.
This enhancement allows the security administrator to designate that a user can invoke an EnterpriseOne application functionality indirectly, for example through an orchestration, but cannot sign on to the EnterpriseOne user interface directly.
This enhancement allows the orchestration designer to retrieve the associated descriptions of data items easily from a data request, particularly when the data being returned is aggregated into groups and intended for graphing.
This feature enables the user to bypass warnings that application forms show while Process Recorder is used.
This feature allows the orchestration or notification designer to specify EnterpriseOne attachments (media objects) to include with orchestration and notification messages.
This enhancement extends the scripting framework to include other scripting languages. In addition to Java, Groovy, and EnterpriseOne business functions, you can now plug in other Java-compatible scripting frameworks, including JRuby or Jython, and use those scripting languages to create custom logic.
This enhancement enables the orchestration designer to craft custom messages for success, warning, and error conditions.
This enhancement enables secure authentication of a user to the EnterpriseOne web client and Orchestrator Studio through a JSON web token (JWT).
This enhancement enables the orchestration designer to control the processing on certain EnterpriseOne applications for steps that generate warnings that require a double acknowledgement for the step to proceed.
This enhancement enables an orchestration designer to create an orchestration for a single orchestration component simply by selecting the option Create Orchestration from a drop-down menu.
This feature expands the options for selecting and operating on grid rows in a form request.
This feature improves the integration to REST services that return information in the response header.
If an external REST service returns output in an array, this enhancement allows you to use the array as an orchestration variable for use by subsequent orchestration steps.
This enhancement gives the orchestration designer the choice of sending the OAuth 2.0 client ID and client secret in the request header or in the request body, as is required by some third-party systems.
This feature now allows the orchestration designer to pass a report version into the report step dynamically as a variable.
This enhancement improves the scalability and fault-tolerance of the EnterpriseOne architecture by allowing multiple AIS servers to share a load of session requests using the same authentication token.
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.