This feature enhances Orchestrator Studio by enabling you to choose available system data, such as environment, user ID, and orchestration name, to include in the orchestration output.

This feature enhances the Orchestrator Rule step to be able to accept lists of criteria values as variables.

This feature enhances the EnterpriseOne extensibility framework with the ability to launch orchestrations, notifications, and logic extensions from form and row exits, which you can add as form extensions.

Oracle now provides an example for automating object life-cycle deployment. This feature enables administrators to run the package deployment process and application through the JD Edwards Orchestrations. Additionally, this feature provides a sample automatic deployment orchestration that administrators can use or alter to their requirements.

When you create a URL attachment using the AIS REST API or Orchestrator Attachment step, this feature enables you to assign a name to a URL attachment that is different than the path to the URL resource itself. For example, for a URL attachment to "https://mycompany.employee-portal.com," you might want the user to see it named as "Employee Portal."

This feature simplifies the user interface in the Run Orchestrations page in Orchestrator Studio by automatically setting the Accept Type to "application/octet-stream" when the orchestration is configured to return a file.

This feature enhances the Orchestrator FTP connector with the ability to read the names of files in a given directory in an FTP site. In this way, orchestrations can automatically read and iterate over a list of files in a directory even if the file names change or are unknown at the time the orchestration runs.

This feature enhances Orchestrator messages and notifications with the ability to pass in a data set (array) and automatically format that data as a table in the message.

This feature provides a framework for persisting the state of orchestrations---a snapshot of all relevant data at a given point---thereby enabling orchestrations to tolerate time gaps in processing, pauses for external systems to respond, starting and stopping between steps, and other asynchronous behaviors.

This feature enables the orchestration designer to reorder orchestration inputs, thus enabling orchestrations to more easily integrate to user interfaces or third-party systems that may be sensitive to the order of inputs.

This feature enhances the Maximum Records option in Orchestrator form requests and data requests to be able to accept a variable number of rows to be returned. For example, an orchestration designer can create an orchestration to return a list of all sales orders at a certain status, and also provide an input variable for the number of rows to be returned. An application that invokes the orchestration, such as a mobile application, can then enable the user to specify the number of rows to return.

This feature enhances the exception response from an error on a form service request to include the field name, data item alias, and table where the data is stored. For grid errors, the exception response also includes the row number on which the error occurred. This additional information simplifies the process of identifying and correcting errors that occur on form service requests.

This feature enhances the Orchestrator Connector step to allow files to be sent to external REST APIs either as a multipart request or as a single part request (without multipart boundaries in the request body).

This feature makes launching of orchestrations from EnterpriseOne pages and form extensions more user-friendly by enabling the designer to override the input names. For example, a designer can rename an orchestration input called "GridIn_1_2" to "Item List."

This feature enables the job queue to be passed into an orchestration report step as a variable. The specified job queue may be supplied by the third-party system or client as an orchestration input, or it may be derived from some other orchestration step. This feature further enhances the power and flexibility when EnterpriseOne reports are called from orchestrations.

The Workflow Monitor provides a modernized update to the traditional EnterpriseOne Workflow Process Monitor application.

This feature enables users to set due dates for tasks that are assigned to recipients through orchestration and notification messages.

The Notification Reminders feature enhances EnterpriseOne notifications by enabling users to easily set reminders for important tasks or assignments.

This feature enables the Orchestrator Report step to generate Output Stream Access (OSA) output.

This feature enables users to specify a separator character other than a comma when outputting data to a CSV file in an orchestration.

This feature simplifies the process of creating new workflows by providing a set of prebuilt data structures that are suitable for a wide variety of workflows.

This feature provides enhanced control over which orchestrations and notifications are logged for success and failure, additional logged data, and visualization in Orchestrator Monitor.

This feature enables you to create orchestrations that accept CSV files as input objects and easily map the columns of the CSV files to orchestration variables.

This feature provides a built-in framework for saving a set of inputs and a set of expected outputs (called assertions) to validate a logic extension.

This enhancement enables logging and monitoring of AIS REST API requests similar to the logging and monitoring of orchestrations and notifications in Orchestrator Monitor.

This feature enhances Orchestrator Studio with an editor for adding rich formatting to text attachments. The body of the text attachment can contain rich-formatted text interspersed with variables, images, and tables, essentially providing a template for creating text attachments with rich formatting. Optionally, the designer can choose to create the text attachment as plain text.

This feature enables you to create logic extensions that call other logic extensions, thus enabling a common pattern in programming in which code snippets are designed as reusable objects.

This feature enhances form extensions by giving you the ability to enable or disable fields on a form. For example, you might modify an application form to disable certain input fields because you intend to replace manual user input with input that is automated by an orchestration or logic extension.

This enhancement enables the designer to map the application version as input into an orchestration or a logic extension when it is launched from a form extension, thereby enabling alternative processing depending on the runtime value of the version.

This feature enhances the capabilities of form extensions to provide a file selector so that the end user can supply file inputs to orchestrations that are launched from form extensions. If the orchestration returns a file as output, this feature also enables the end user to download that file to the browser's download location.

This feature enhances logic extensions with the ability to act on the properties of controls on the form, such as to show, hide, enable, disable, or change the color of a field. For example, with form control extensions you could determine the value a user has entered into a field, and based on that value conditionally enable, disable, or highlight a different control.

This feature enables you to mark orchestrations as "private", thus excluding them from the discoverable list of available orchestrations in the OpenAPI 2.0 and Swagger documents.

Orchestrations can be configured with default inputs; however, sometimes the inputs that are appropriate for a scheduled orchestration are different. This enhancement allows you to define a set of inputs that are associated with the scheduled runs of an orchestration.

Orchestrator automatically generates the OpenAPI document from the internal specifications of orchestration objects; however, from time to time customers find it necessary to edit that OpenAPI document to reflect modifications they have made. This feature provides an editing window that allows a user to manually modify the automatically generated OpenAPI document.

EnterpriseOne Workflow has traditionally enabled a level of process automation by offering capabilities such as sending messages with action links, running reports, and executing business functions. This enhancement expands the power of workflows by adding the ability to invoke orchestrations and notifications. In this way, workflow processes now inherit all the automation power of orchestrations, while still maintaining their ability to suspend processing to wait for human activities, such as approvals.

This enhancement enables you to launch a logic extension directly from a form extension without having to include it in an orchestration, thus simplifying the process of associating the logic extension to a form and eliminating the unnecessary orchestration.

This feature enhances the capabilities of logic extensions with the ability to aggregate data that is read from EnterpriseOne tables. Designers can leverage built-in data analytics capabilities within the EnterpriseOne system, simplify cases in which data needs to be summed, averaged, or otherwise aggregated, and accomplish a level of data analysis and manipulation without programming skills.

This feature enhances the capabilities of logic extensions with the ability to accept arrays as inputs and return arrays as outputs for efficient iterative processing of multiple rows of data within the logic extension.

This feature provides a built-in, preconfigured, read-only Orchestrator connection to the EnterpriseOne database. Using this connection, users with SQL programming skills can create orchestrations that perform more advanced queries to the EnterpriseOne database, such as table joins and complex SQL queries.

This enhancement broadens the list of APIs that can be invoked through e1pagehelper.js to include essentially all AIS APIs, thus expanding the services you can use to build your custom JavaScript pages.

This feature enhances the capabilities of composed pages to provide a file selector so that the end user can easily supply file inputs to orchestrations that are launched from composed pages.

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.