JDE orchestration enhancements, since 9.2.3.3

Would you like to know all of the orchestration enhancements and which tools release they have been put in over the last few years.  Here is a list that you are going to love.  

Orchestration needs to be less bound to the tools release in my humble opinion.  If the architects in Denver could find us a nice way of keeping orchestration up to date with all the pain of a traditional tools release.

I know it goes hand in hand with the JAS, I understand it's relationship with the pathcode, but if I could upgrade the orchestration layer easier - I would do it more often.  If the tools supported multiple orchestration layers, this would be good too...  It's such a let down when you read this list of enhancements and realise the amount of work that you need to complete to perform "work arounds" with orchestration - as opposed to the effort of putting in a new tools release.

9.2.4.4	The JD Edwards EnterpriseOne Orchestrator print functionality enables you to capture your orchestrations on a standard letter page or as a PDF file. The printed 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.
	When an orchestration is included as a step within another orchestration, you can click the Expand icon to expand the included orchestrations inline.This enables you to see what the sub-orchestrations accomplish without navigating away from the parent orchestration.
	You can double-click the collapsed orchestration step or double-click the white space within the bounding box of an expanded orchestration to edit the child orchestration.
	If you have inputs defined for an orchestration, you can see the Orchestration Inputs section in the Orchestration Output window. This functionality enables you to include any input value in the final output of an orchestration.
	Starting with Tools Release 9.2.4.4, the Number of Threads option is displayed when you enable the Fire and Forget toggle. This option enables you to select the number of threads for an iterated step.
	You can click the Raw Output button in the Last Step tab of the Debug Orchestration panel to view the complete response of the step in the JSON format.
	You can specify how you want to process an orchestration: in a single-threaded queue, in a fire-and-forget multithreaded queue, or in the default queue. Using this feature, you can have more control over the runtime processing of orchestrations.
	You can designate one or more columns individually as a Header Field when you import the CSV file as an array through an FTP connector. You can designate columns of data within the CSV files as indicators of grouped data, thereby giving the flat CSV data a certain amount of structure.
	Starting with Tools release 9.2.4.4, you can override the queues while testing the orchestrations.
	You can pass the exception message to the called orchestration or notification. For example, you can choose to receive a notification email that includes the exception message from the failed step.
9.2.4.3	Embed orchestrations without a connector
	The JD Edwards EnterpriseOne Orchestrator provides a way to debug your orchestrations. A Debug button on the Run Orchestrations page enables an interactive tool that you can use to determine the state of your orchestration at any point during execution. The Debug tool provides a view into an orchestration, enabling the designer to run an orchestration step-by-step and ensure that the data is correct at each step until the final orchestration output.
	The JD Edwards EnterpriseOne Orchestrator enables you to invoke a business function from an orchestration. In addition to “Groovy” and “Java” you can select “Business Function” as a Custom Request type. You can pass inputs into the business function and receive outputs.
9.2.4.2	Tools Release 9.2.4.2 provides the following enhancements for the Orchestrator Studio 9.2.4: • You can create and assign categories to orchestrations, notifications, and their subcomponents. Categories enable you to group and manage components that have a common purpose or attribute. For example, you might assign the category “Demo” to the orchestrations and subcomponents that you use for demonstrations. Orchestration designers can create new categories, and optionally share them with others, from within the Orchestrator Studio. Shared categories are saved to an EnterpriseOne table; they can be added, modified, and deleted using the Category Manager application (P980058).
	You can export multiple orchestrations and notifications belonging to a specific Orchestrator category as a single file. For example, if you have a set of three orchestrations and two notifications with the category “Demo,” you can export all the five components as a single zip file. By default, the Orchestrator also exports all the subcomponents (service requests, rules, and so on) of the orchestrations and notifications, even if those subcomponents are not assigned the same category. In this way, you can easily export and import the entire working sets of orchestrations and notifications.
9.2.4	Orchestrator Studio 9.2.4 includes an intuitive and easy-to-use interface for managing and monitoring your scheduled orchestrations and notifications. The Scheduler user interface enables you to start, stop, and monitor the scheduled jobs. The options to search, sort, and filter the jobs simplify the process of managing your scheduled notifications and orchestrations.
	Starting with Tools 9.2.4.0, the Orchestrator Studio is deployed as a component of the Application Interface Services (AIS) server. The standard Server Manager process is used to deploy an AIS server, and the Orchestrator Studio is immediately available through a URL endpoint to that server. The requirement to install and maintain a discrete WebLogic Server or ADF environment is eliminated. Security administrators can control access to Orchestrator Studio users and roles by granting access to the Orchestrator Studio application (P98I0000). The Orchestrator Studio application enables you to determine the different levels of security for the Orchestrator Studio, the Admin service, and Scheduler that includes access to the Scheduler services and the Scheduler user interface. You no longer have to enter a list of users into the AIS White List in Server Manager.
	The Orchestrator Studio is redesigned to provide an intuitive and easy-to-use graphical interface. Orchestrator Studio 9.2.4 simplifies the process of creating orchestrations for nontechnical users, while giving technical users a powerful pallet of capabilities for more complex orchestrations. Starting with Tools Release 9.2.4.0, the Orchestrator Studio is deployed as a component of the Application Interface Services (AIS) server. The standard Server Manager process is used to deploy an AIS server, and the Orchestrator Studio is available through a URL endpoint to that server. The requirement to install and maintain a discrete WebLogic Server or ADF environment is eliminated.
	The form extensibility framework enables users to associate orchestrations with events on an EnterpriseOne form. This capability has been further enhanced to enable users to map the orchestration outputs to the grid columns. Additionally, if the data mapped to an orchestration belongs to a grid column, when the orchestration or notification is executed, the data will be retrieved for all the selected grid rows. Other enhancements include: * Ability to search for an orchestration or notification while selecting an orchestration or notification in the Associate Orchestrations wizard * Disabling a form if there is an error when an orchestration or notification is executed
9.2.3.4	The form extensibility framework is being enhanced to enable citizen developers to map the orchestration output parameters to the form context. This feature allows form controls to be updated based on the response of the orchestration that is called from an interactive application using the form extensibility framework.
	The JD Edwards EnterpriseOne Orchestrator Studio can be used for JD Edwards System Administration.This will enable the system administrators to call the Server Manager REST services from the Orchestrator Studio to automate the administrative tasks.