JDE Orchestrator: различия между версиями

Материал из JD Edwards E1
Перейти к навигации Перейти к поиску
м
 
(не показаны 34 промежуточные версии этого же участника)
Строка 1: Строка 1:
−
* Orchestrator Guide for Studio Version 9.2.4
+
* Orchestrator Studio Version 9.2.4
−
* Orchestrator Guide for Studio Version 8 and Prior
+
* Orchestrator Studio Version 8 and Prior
−
 
 
−
Orchestrator:
 
−
* Компоненты Orchestration (Orchestration components) [Release 9.2.1];
 
−
* Нотификация (Notifications) [Release 9.2.2];
 
−
* График (Schedules) [Release 9.2.2];
 
−
* Process Recorder [Release 9.2.2.4];
 
−
== JD Edwards EnterpriseOne Orchestrator Studio ==
 
 
{|  
 
{|  
 
|
 
|
 
{| class="wikitable" style="text-align: center;"
 
{| class="wikitable" style="text-align: center;"
 +
|+ Framework
 
  |- style="height:100px;"
 
  |- style="height:100px;"
−
  ! style="width:150px; color:orange" | Orchestrations </br> [[JDE_Orchestrator#Orchestrator Orchestrations | [docs] ]] [[JDE_Orchestrator#Orchestrator Orchestrations | [wiki] ]]
+
  ! style="width:150px; color:orange" | Orchestrations </br> [[JDE_Orchestrator#Orchestrator Orchestrations | [Overview]]] [[JDE_Orchestrator#Orchestrator Orchestrations | [wiki] ]]
 
  |- style="height:100px;"
 
  |- style="height:100px;"
−
  ! style="width:150px; color:red" | Notifications </br> [[JDE_Orchestrator#Orchestrator Notifications | [docs] ]] [[JDE_Orchestrator#Orchestrator Notifications| [wiki] ]]
+
  ! style="width:150px; color:red" | Notifications </br> [[JDE_Orchestrator#Orchestrator Notifications | [Overview] ]] [[JDE_Orchestrator#Orchestrator Notifications| [wiki] ]]
 
  |- style="height:100px;"
 
  |- style="height:100px;"
−
  ! style="width:150px; color:purple" | Workflows </br> [[JDE_Orchestrator#Orchestrator Workflows | [docs] ]] [[JDE_Orchestrator#Orchestrator Workflows | [wiki] ]]
+
  ! style="width:150px; color:purple" | Workflows </br> [[JDE_Orchestrator#Orchestrator Workflows | [Overview] ]] [[JDE_Orchestrator#Orchestrator Workflows | [wiki] ]]
 
  |}
 
  |}
 
|
 
|
 
  {| class="wikitable" style="text-align: center; color:green; "
 
  {| class="wikitable" style="text-align: center; color:green; "
 +
|+ Orchestrator Componets
 
  |- style="height:100px;"
 
  |- style="height:100px;"
−
  | style="width:110px;" | [[JDE_Orchestrator#Orchestrator Form Requests | Form Requests ]] || style="width:110px;" | [[JDE_Orchestrator#Orchestrator Data Requests | Data Requests ]] || style="width:110px;" | [[JDE_Orchestrator#Orchestrator Reports | Reports ]] || style="width:110px;" | [[JDE_Orchestrator#Orchestrator Watchlists | Watchlists ]] || style="width:110px;" | [[JDE_Orchestrator#Orchestrator Attachments | Attachments ]]  
+
  | style="width:110px;" | Form Requests </br> [[JDE_Orchestrator#Orchestrator Form Requests | [Overview] ]]  
 +
| style="width:110px;" | Data Requests </br>  [[JDE_Orchestrator#Orchestrator Data Requests | [Overview] ]]  
 +
| style="width:110px;" | Reports </br> [[JDE_Orchestrator#Orchestrator Reports | [Overview] ]]  
 +
| style="width:110px;" | Watchlists </br> [[JDE_Orchestrator#Orchestrator Watchlists | [Overview] ]]  
 +
| style="width:110px;" | Attachments </br> [[JDE_Orchestrator#Orchestrator Attachments | [Overview] ]]  
 
  |- style="height:100px;"
 
  |- style="height:100px;"
−
  | style="width:100px;" | Connectors || Logic Extensions || Custom Requests || Messages ||
+
  | Connectors </br> [[JDE_Orchestrator#Orchestrator Connectors | [Overview] ]]
 +
| Logic Extensions </br> [[JDE_Orchestrator#Orchestrator Logic Extensions | [Overview] ]]
 +
| Custom Requests </br> [[JDE_Orchestrator#Orchestrator Custom Requests | [Overview] ]]
 +
| Messages </br> [[JDE_Orchestrator#Orchestrator Messages | [Overview] ]]
 +
|
 
  |- style="height:100px;"
 
  |- style="height:100px;"
−
  | style="width:100px;" | Rules || Cross References || White Lists || Schedules ||  
+
  | Rules </br> [[JDE_Orchestrator#Orchestrator Rules | [Overview] ]]
 +
| Cross References </br> [[JDE_Orchestrator#Orchestrator Cross References | [Overview] ]]
 +
| White Lists </br> [[JDE_Orchestrator#Orchestrator White Lists | [Overview] ]]
 +
| Schedules </br> [[JDE_Orchestrator#Orchestrator Schedules | [Overview] ]]
 +
|  
 
  |}
 
  |}
 
|-
 
|-
 
| colspan = "2" |
 
| colspan = "2" |
 
  {| class="wikitable" style="text-align: center; color:blue;"
 
  {| class="wikitable" style="text-align: center; color:blue;"
 +
|+ Orchestrator Services
 
  |- style="height:100px;"
 
  |- style="height:100px;"
 
  | style="width:100px;" | Run </br>Orchestrations || style="width:100px;" | JD Edwards </br>EnterpriseOne || style="width:100px;" | Orchestrator </br>Monitor || style="width:100px;" | Workflow </br>Monitor || style="width:100px;" | Scheduler || style="width:100px;" | Import/Export || style="width:100px;" | Connections
 
  | style="width:100px;" | Run </br>Orchestrations || style="width:100px;" | JD Edwards </br>EnterpriseOne || style="width:100px;" | Orchestrator </br>Monitor || style="width:100px;" | Workflow </br>Monitor || style="width:100px;" | Scheduler || style="width:100px;" | Import/Export || style="width:100px;" | Connections
 +
|}
 +
|-
 +
| colspan = "2" |
 +
{| class="wikitable" style="text-align: center;"
 +
|+ JDE / Other
 +
|- style="height:100px;"
 +
| style="width:150px;" | Form Extension </br> [[JDE_Orchestrator#Orchestrator Form Extension | [Overview] ]]
 +
| style="width:150px;" | Process Recorder </br> [[JDE_Orchestrator#Orchestrator Process Recorder | [Overview] ]]
 +
| style="width:150px;" | B98ORCH </br> [[JDE_Orchestrator#Orchestrator B98ORCH | [Overview] ]]
 +
| style="width:150px;" | Security </br> [[JDE_Orchestrator#Orchestrator Security | [Overview] ]]
 +
| style="width:150px;" | OMW Promotion </br> [[JDE_Orchestrator#Orchestrator OMW Promotion | [Overview] ]]
 
  |}
 
  |}
 
|}
 
|}
  
−
== Ссылки ==
+
Компоненты Orchestration (Orchestration components) [Release 9.2.1];
 +
* Нотификация (Notifications) [Release 9.2.2];
 +
* График (Schedules) [Release 9.2.2];
 +
* Process Recorder [Release 9.2.2.4];
 +
 
 +
== Orchestrator Studio Version 9.2.4+ ==
  
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2026713.1 E1: ORCH: Installation of JD Edwards Orchestrator Components (Getting Started) (Doc ID 2026713.1)]
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2026713.1 E1: ORCH: Installation of JD Edwards Orchestrator Components (Getting Started) (Doc ID 2026713.1)]
Строка 83: Строка 107:
  
 
=== Orchestrator Notifications ===
 
=== Orchestrator Notifications ===
 +
With the JD Edwards EnterpriseOne Orchestrator Studio, you can devise processes called notifications that enable the transformation of data into actionable business processes in JD Edwards EnterpriseOne. For example, you can create notifications that enable EnterpriseOne to:
 +
* Alert users to a required activity.
 +
* Alert users when a Watchlist threshold has been surpassed.
 +
* Broadcast an informational message to users.
 +
 +
Notifications that you create in the Orchestrator Studio are saved to EnterpriseOne. The JD Edwards EnterpriseOne Orchestrator then processes the notifications based on how often you schedule them to run and sends notification messages to subscribers.
 +
 +
As an extension of the Orchestrator framework, notifications can assess your EnterpriseOne data, and also any REST-enabled external service, to detect conditions or events that need attention. Messages are then sent out to subscribers who need to know that an event has occurred that requires attention. The messages can contain action links to help the recipients act quickly with an appropriate response.
 +
 +
On the Home Page in Orchestrator Studio, select Notifications.
 +
 +
; Links
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2725461.2 E1: ORCH: Orchestrator Notifications Reference Center] (Doc ID 2725461.2)
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2725461.2 E1: ORCH: Orchestrator Notifications Reference Center] (Doc ID 2725461.2)
 
: Notifications How To and FAQ Documents
 
: Notifications How To and FAQ Documents
Строка 113: Строка 149:
  
 
=== Orchestrator Form Request ===  
 
=== Orchestrator Form Request ===  
 +
;Overview
 +
 +
A form request invokes one or more EnterpriseOne application forms. You use this type of request to automate EnterpriseOne applications. You can create a form request in the Orchestrator Studio, or you can use the Process Recorder to record your actions in EnterpriseOne and then edit the resulting form request in the Orchestrator Studio. Form requests can use EnterpriseOne applications to read data and also to write data back to EnterpriseOne tables just as a human user would.
 +
 +
; Links
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2834816.2 E1: ORCH: Orchestrator Form Request Reference Center] (Doc ID 2834816.2)
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2834816.2 E1: ORCH: Orchestrator Form Request Reference Center] (Doc ID 2834816.2)
 
Form Service Request How To and FAQ Documents
 
Form Service Request How To and FAQ Documents
Строка 124: Строка 165:
  
 
=== Orchestrator Data Requests ===  
 
=== Orchestrator Data Requests ===  
 +
; Overview
 +
Use a data request in an orchestration to query and retrieve values from an EnterpriseOne table or business view. You can also configure a data request to perform an aggregation on data to return aggregate amounts.
 +
 +
In the Orchestrator Studio, you can create a data service request to enable an orchestration to:
 +
* Query and return data from an EnterpriseOne table or business view.
 +
* Perform an aggregation of data from a table or a business view and return aggregate amounts.
 +
 +
In a standard data request that returns data directly from a table or business view, you can use define variables for one or more of the return fields. In a data request that performs an aggregation, you can use define variables for the "group by" fields and the returned aggregate amounts.
 +
 +
; Links
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2725398.2 E1: ORCH: Orchestrator Data Requests Reference Center] (Doc ID 2725398.2)
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2725398.2 E1: ORCH: Orchestrator Data Requests Reference Center] (Doc ID 2725398.2)
 
: Data Request How To and FAQ Documents
 
: Data Request How To and FAQ Documents
Строка 131: Строка 182:
  
 
=== Orchestrator Reports ===  
 
=== Orchestrator Reports ===  
 +
; Overview
 +
Use a report service request to invoke a batch version of an EnterpriseOne report from an orchestration. You can configure a report service request to use the settings that are defined for the report in the Batch Versions program. Alternatively, you can configure a report service request to override the processing options, data selection, and data sequencing of a report.
 +
 +
You can also create a report service request to invoke an embedded BI Publisher report, and configure report service request to use the default settings or override the settings.
 +
 +
A report service request can launch EnterpriseOne reports that are designed with report interconnects. Report interconnects are inputs that are added to a report at design time. These inputs enable a report to run automatically without user interaction. Typically, report interconnects are used to launch a report from a button or exit on an EnterpriseOne form.
 +
 +
In the Report design page, the Fire and Forget toggle enables the report to run asynchronously. When the Orchestrator executes the orchestration, this option enables the orchestration to continue to the next action or step without waiting for the report to complete.
 +
 +
At runtime, when the Orchestrator processes the report service request, it respects the EnterpriseOne authorization security for the report. The user initiating the orchestration must be authorized to run the batch version of the report as defined by an administrator in the Security Workbench. If the report service request includes data selection or processing option overrides, the user who is initiating the orchestration must be authorized in the Security Workbench to perform these overrides as well.
 +
 +
; Links
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2846181.2 E1: ORCH: Orchestrator Reports Reference Center] (Doc ID 2846181.2)
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2846181.2 E1: ORCH: Orchestrator Reports Reference Center] (Doc ID 2846181.2)
 
: Reports Request How To and FAQ Documents
 
: Reports Request How To and FAQ Documents
Строка 141: Строка 204:
  
 
=== Orchestrator Attachments ===  
 
=== Orchestrator Attachments ===  
 +
; Overview
 +
Attachments are used to automate EnterpriseOne transactions by including the options to manage text attachments, add URL attachments, and upload or download file attachments (media objects) in transactions.
 +
 +
Using Attachments, you can perform the following actions for a specified key:
 +
* List files, texts, and URLs.
 +
* Get the text in a sequence or get all the text attachments.
 +
* Add either a text or an URL type of attachment.
 +
* Update the text.
 +
* Upload a file from the temporary directory of your AIS Server.
 +
* Download a file.
 +
* Delete a file.
 +
 +
;Links
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2908321.2 E1: ORCH: Orchestrator Attachments Reference Center] (Doc ID 2908321.2)
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2908321.2 E1: ORCH: Orchestrator Attachments Reference Center] (Doc ID 2908321.2)
 
: Attachments How To and FAQ Documents
 
: Attachments How To and FAQ Documents
Строка 228: Строка 304:
  
 
=== Orchestrator Logic Extensions ===  
 
=== Orchestrator Logic Extensions ===  
 +
Creating Logic Extensions (Release 9.2.6)
 +
 +
Understanding Logic Extensions
 +
 +
The Orchestrator Studio provides a web-based user interface to create logic extensions. Using logic extensions, you can create business logic to perform operations such as string manipulation, arithmetic calculations, conditions, loops, and even table I/O. Using the logic extensibility framework, you can use the familiar syntax of the JD Edwards Named Event Rules language to create custom logic. The logic extensions component can be added as a step in the orchestration. Logic extensions are created and managed as user-defined objects (UDOs), and therefore they inherit all the lifecycle management and security capabilities of the UDO framework. Logic extensions are ready to run immediately as part of an orchestration.
 +
 +
Click here to view a recording of this feature.
 +
 +
Click here to view an OBE of this feature.
 +
 +
Navigating the Logic Extensions Page The Logic Extensions page displays a list of icons for creating logic extensions. Hover over each icon to view the associated description. The Data Structure tab is displayed by default when you start creating a new logic extension.
 +
 +
; Links
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2908653.2 E1: ORCH: Orchestrator Logic Extensions Reference Center] (Doc ID 2908653.2)
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2908653.2 E1: ORCH: Orchestrator Logic Extensions Reference Center] (Doc ID 2908653.2)
 
: Orchestrator Logic Extensions How To and FAQ Documents
 
: Orchestrator Logic Extensions How To and FAQ Documents
Строка 250: Строка 339:
  
 
=== Orchestrator Messages Request ===  
 
=== Orchestrator Messages Request ===  
 +
; Overview
 +
Messages are then sent out to subscribers who need to know that an event has occurred that requires attention. The messages can contain action links to help the recipients act quickly with an appropriate response.
 +
 +
Use a message request if you want an orchestration to send a message to an external email address (requires an SMTP server) or to EnterpriseOne users through the EnterpriseOne Work Center. A message request allows you to send an e-mail message to one or more recipients. You can create the subject and body of the message, including text substitution variables that are populated from previous orchestration steps. The message can include links to EnterpriseOne applications, links to external URLs, links that launch other orchestrations or notifications, and attachments.
 +
 +
You can add a message request to an orchestration to send emails to external email systems or the EnterpriseOne Work Center email system. The following features are supported in a message request:
 +
* Workflow distribution lists that can be used to send messages to a predefined group of EnterpriseOne users.
 +
* Message templates from the data dictionary that contain boilerplate text and values related to a particular business process.
 +
* Links to EnterpriseOne applications.
 +
* Links to EnterpriseOne reports and BI Publisher reports.
 +
* Links to URLs.
 +
* Links to notifications and orchestrations.
 +
 +
;Links
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2829064.2 E1: ORCH: Orchestrator Messages Request Reference Center] (Doc ID 2829064.2)
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2829064.2 E1: ORCH: Orchestrator Messages Request Reference Center] (Doc ID 2829064.2)
 
: Messages Request How To and FAQ Documents
 
: Messages Request How To and FAQ Documents

Текущая версия на 12:11, 2 октября 2024

  • Orchestrator Studio Version 9.2.4
  • Orchestrator Studio Version 8 and Prior
Framework
Orchestrations
[Overview] [wiki]
Notifications
[Overview] [wiki]
Workflows
[Overview] [wiki]
Orchestrator Componets
Form Requests
[Overview] 		Data Requests
[Overview] 		Reports
[Overview] 		Watchlists
[Overview] 		Attachments
[Overview]
Connectors
[Overview] 		Logic Extensions
[Overview] 		Custom Requests
[Overview] 		Messages
[Overview]
Rules
[Overview] 		Cross References
[Overview] 		White Lists
[Overview] 		Schedules
[Overview]
Orchestrator Services
Run
Orchestrations		 JD Edwards
EnterpriseOne		 Orchestrator
Monitor		 Workflow
Monitor		 Scheduler Import/Export Connections
JDE / Other
Form Extension
[Overview] 		Process Recorder
[Overview] 		B98ORCH
[Overview] 		Security
[Overview] 		OMW Promotion
[Overview]

Компоненты Orchestration (Orchestration components) [Release 9.2.1];

  • Нотификация (Notifications) [Release 9.2.2];
  • График (Schedules) [Release 9.2.2];
  • Process Recorder [Release 9.2.2.4];

Orchestrator Studio Version 9.2.4+

Orchestrator Orchestrations

An orchestration is the high-level object that includes any number of Orchestrator components as building blocks to complete a desired task. When you create and save an orchestration in Orchestrator Studio, it automatically becomes a published REST service with the following endpoint:

http://<AIS_server>:<port>/jderest/orchestrator/<orchestrationname>

Orchestrations are built within the framework of user-defined objects, not custom-developed objects that need to be built into packages, deployed, and retrofitted during upgrades. All orchestrations are subject to EnterpriseOne application, data, and user-defined object security.

The basic framework of orchestrations as REST services enables a wide variety of usage patterns that provide secure access to your EnterpriseOne business data and applications. For example:

  • Orchestrations enable customers to collect, filter, analyze, and act on real-time data as it is being transmitted by Internet of Things (IoT) devices.
  • Third-party systems and Cloud services can invoke orchestrations as REST-based services, allowing for easy and lightweight integrations.
  • Orchestrations can automate tedious tasks that end users perform to simplify a business process.
  • Orchestrations can be used for system administration using the Server Manager REST API

Orchestrations can be invoked a few different ways:

  • Within Orchestrator Studio
  • Form extensibility framework from an interactive application
  • The B98ORCH business function
  • Orchestrator Scheduler
  • REST call
Link
Orchestrator Orchestrations How To and FAQ Documents:

Orchestrator Notifications

With the JD Edwards EnterpriseOne Orchestrator Studio, you can devise processes called notifications that enable the transformation of data into actionable business processes in JD Edwards EnterpriseOne. For example, you can create notifications that enable EnterpriseOne to:

  • Alert users to a required activity.
  • Alert users when a Watchlist threshold has been surpassed.
  • Broadcast an informational message to users.

Notifications that you create in the Orchestrator Studio are saved to EnterpriseOne. The JD Edwards EnterpriseOne Orchestrator then processes the notifications based on how often you schedule them to run and sends notification messages to subscribers.

As an extension of the Orchestrator framework, notifications can assess your EnterpriseOne data, and also any REST-enabled external service, to detect conditions or events that need attention. Messages are then sent out to subscribers who need to know that an event has occurred that requires attention. The messages can contain action links to help the recipients act quickly with an appropriate response.

On the Home Page in Orchestrator Studio, select Notifications.

Links
Notifications How To and FAQ Documents

Orchestrator Workflows

Adding a Workflow (Release 9.2.6.4)

Starting with Tools Release 9.2.6.4, you can add workflows to your logic extensions. When you add a workflow to your logic extension, the Workflow panel is displayed at the right hand side of the design page that enables you to search for and add a workflow in the Workflow field. After you add the workflow in the Workflow field, the Key Data Structure and the Additional Data Structure sections are populated. You can click the Edit icon next to Key Data Structure and Additional Data Structure and map the parameters. Next to each required parameter the system displays the Incomplete Mapping (!) icon in red. You can click the Edit icon to open the Workflow Parameter Mapping window and complete the mappings for a required parameter. The Input fields are disabled for the required parameters.

To add a Workflow:

  • On the design page, hover over the location where you want to add the workflow and then click the + icon. Select Workflow from the Action menu. The system displays the Workflow panel on the right.
  • In the Workflow panel, enter the label and the description for the workflow.
  • In the Workflow field, click the Search icon to search for and select the required workflow from the Workflow List window. After you select the workflow, the Key Data Structure and Additional Data Structure sections are displayed to create the mappings. Next to each required parameter the system displays the Incomplete Mapping (!) icon in red.
  • Click the Edit icon next to Parameter Mapping and Additional Data Structure to open the Workflow Parameter Mapping window and complete the mappings as required.
  • Click the Close button.
  • Click Save. You can add the workflow parameters to the Data Structure tab and to the Variables tab from the Workflow Parameter Mapping window. Click the drop-down list next to the Name field and select the Add to Data Structure or Add to Variables or Add to Array (Release 9.2.7) option as required.
Links
Orchestrator Workflows How To and FAQ Documents

Orchestrator Form Request

Overview

A form request invokes one or more EnterpriseOne application forms. You use this type of request to automate EnterpriseOne applications. You can create a form request in the Orchestrator Studio, or you can use the Process Recorder to record your actions in EnterpriseOne and then edit the resulting form request in the Orchestrator Studio. Form requests can use EnterpriseOne applications to read data and also to write data back to EnterpriseOne tables just as a human user would.

Links

Form Service Request How To and FAQ Documents

Orchestrator Data Requests

Overview

Use a data request in an orchestration to query and retrieve values from an EnterpriseOne table or business view. You can also configure a data request to perform an aggregation on data to return aggregate amounts.

In the Orchestrator Studio, you can create a data service request to enable an orchestration to:

  • Query and return data from an EnterpriseOne table or business view.
  • Perform an aggregation of data from a table or a business view and return aggregate amounts.

In a standard data request that returns data directly from a table or business view, you can use define variables for one or more of the return fields. In a data request that performs an aggregation, you can use define variables for the "group by" fields and the returned aggregate amounts.

Links
Data Request How To and FAQ Documents

Orchestrator Reports

Overview

Use a report service request to invoke a batch version of an EnterpriseOne report from an orchestration. You can configure a report service request to use the settings that are defined for the report in the Batch Versions program. Alternatively, you can configure a report service request to override the processing options, data selection, and data sequencing of a report.

You can also create a report service request to invoke an embedded BI Publisher report, and configure report service request to use the default settings or override the settings.

A report service request can launch EnterpriseOne reports that are designed with report interconnects. Report interconnects are inputs that are added to a report at design time. These inputs enable a report to run automatically without user interaction. Typically, report interconnects are used to launch a report from a button or exit on an EnterpriseOne form.

In the Report design page, the Fire and Forget toggle enables the report to run asynchronously. When the Orchestrator executes the orchestration, this option enables the orchestration to continue to the next action or step without waiting for the report to complete.

At runtime, when the Orchestrator processes the report service request, it respects the EnterpriseOne authorization security for the report. The user initiating the orchestration must be authorized to run the batch version of the report as defined by an administrator in the Security Workbench. If the report service request includes data selection or processing option overrides, the user who is initiating the orchestration must be authorized in the Security Workbench to perform these overrides as well.

Links
Reports Request How To and FAQ Documents

Orchestrator Attachments

Overview

Attachments are used to automate EnterpriseOne transactions by including the options to manage text attachments, add URL attachments, and upload or download file attachments (media objects) in transactions.

Using Attachments, you can perform the following actions for a specified key:

  • List files, texts, and URLs.
  • Get the text in a sequence or get all the text attachments.
  • Add either a text or an URL type of attachment.
  • Update the text.
  • Upload a file from the temporary directory of your AIS Server.
  • Download a file.
  • Delete a file.
Links
Attachments How To and FAQ Documents

Orchestrator Connector

In the Orchestrator Studio, you can create a connector service request to enable an orchestration to:

  • Invoke another orchestration or a notification on an AIS Server on another EnterpriseOne system in a multisite operation.
  • Invoke a REST service. Referred to as a REST connector, this connector enables outbound REST calls to external systems through an orchestration step. For example, an orchestration could make a REST call to a Cloud service and use the data in the response in subsequent orchestration steps.
  • You can also configure a REST connector to invoke REST services from your local AIS server. By using the Local AIS Call connection, you can run a REST service on the current AIS server by using the existing session established to run the calling orchestration
  • Connect to a database. Referred to as a database connector, this connector enables orchestrations to read from and write to non-JD Edwards databases using standard SQL protocol. The database must support JDBC. A database connector enables external databases to be the source of input for orchestrations. It also enables data that is not appropriate for transaction tables to be stored for analysis, archiving, or integration.
  • Retrieve a file from or send a file to a known location using either the File Transfer Protocol (FTP) or the Secure File Transfer Protocol (SFTP). This connector is referred to as an FTP connector. You can also use an FTP connector to retrieve data from a CSV file.
  • Send a file to a known location using a REST protocol.
  • List all the REST services that can be performed on Server Manager using the Open API connector.
  • Invoke REST services from your local AIS server. The session that is already established to execute the orchestration is reused for the current AIS REST call.
Links
Open API Connector How To and FAQ Documents
  • E1: ORCH: Database Connector Sample With Oracle DB and TR 9.2.5.4 and Above - Groovy And Jython [Updated: 02/02/2024]
  • E1: ORCH: How to Assign (Parse) Nested JSON Output (Array Output) Values into Variables in the Connector Output [Updated: 05/01/2023]
  • E1: ORCH: How to use "AND/OR" Filter For Multiple Fields Using "/v2/dataservice/table/{tableName}" API From the Connector [Updated: 08/30/2022]
  • E1: ORCH: How to Pass Output Values from a Service Request (Form, Data, Report, etc) to Connector (External Rest) Body as an Input Variable [Updated: 03/11/2022]
  • E1: ORCH: AIS: How To Call a 3rd Party Web Service (WSDL) From Orchestration [Updated: 08/24/2021]
Orchestration Connector How To and FAQ Documents
  • E1: ORCH: Database Connector Sample With Oracle DB and TR 9.2.5.4 and Above - Groovy And Jython [Updated: 02/02/2024]
  • E1: ORCH: How to Assign (Parse) Nested JSON Output (Array Output) Values into Variables in the Connector Output [Updated: 05/01/2023]
  • E1: ORCH: How to use "AND/OR" Filter For Multiple Fields Using "/v2/dataservice/table/{tableName}" API From the Connector [Updated: 08/30/2022]
  • E1: ORCH: How to Pass Output Values from a Service Request (Form, Data, Report, etc) to Connector (External Rest) Body as an Input Variable [Updated: 03/11/2022]
  • E1: ORCH: AIS: How To Call a 3rd Party Web Service (WSDL) From Orchestration [Updated: 08/24/2021]
Database Connector How To and FAQ Documents
  • E1: ORCH: Database Connector Sample With Oracle DB and TR 9.2.5.4 and Above - Groovy And Jython [Updated: 02/02/2024]
  • E1: ORCH: How to Configure Database Connection Outputs to be used as Service Request Inputs [Updated: 08/07/2023]
  • E1: ORCH: How to Create a Connector for Selecting Data From a Table Using a Variable with the EnterpriseOne Database (Read-only) DAD Connection [Updated: 08/03/2023]
  • E1: ORCH: How to Assign (Parse) Nested JSON Output (Array Output) Values into Variables in the Connector Output [Updated: 05/01/2023]
  • E1: ORCH: Orchestrator and Database Connection / Connector [Updated: 05/01/2023]
  • E1: ORCH: Is it Possible to Create Dynamic Runtime Queries on E1 Tables Using Orchestrator REST API ? [Updated: 04/10/2023]
  • E1: ORCH: How To Configure The DAD (Data Access Driver) In Orchestrator/Connector (EnterpriseOne Database (Read-only) ) [Updated: 04/10/2023]
  • E1: ORCH: How to use "AND/OR" Filter For Multiple Fields Using "/v2/dataservice/table/{tableName}" API From the Connector [Updated: 08/30/2022]
  • E1: ORCH: How To Use the Database Connector To Point To the Correct DB Owner Based on The Login Environment Without Creating Multiple Groovy Script For Multiple Environments? [Updated: 06/14/2022]
  • E1: ORCH: How to Pass Output Values from a Service Request (Form, Data, Report, etc) to Connector (External Rest) Body as an Input Variable [Updated: 03/11/2022]
  • E1: ORCH: How To Call SQL Oracle Stored Procedure From Groovy Using Orchestrator [Updated: 03/09/2022]
  • E1: ORCH: How to Convert Date Format From yyyyMMdd to MM/dd/yyyy [Updated: 03/09/2022]
  • E1: ORCH: How To Output the SUM of Column Values Using Database Connector and Data Service Request (Aggregation) [Updated: 02/21/2022]
  • E1: ORCH: AIS: How To Call a 3rd Party Web Service (WSDL) From Orchestration [Updated: 08/24/2021]
  • E1: ORCH: How to Update a JDE Table with Orchestration ? [Updated: 03/02/2020]
REST Connector How To and FAQ Documents
  • E1: ORCH: How To Configure a Connector (REST) To Upload A File Using Data (Binary) Instead Of Using "multipart/form-data" [Updated: 05/02/2024]
  • E1: ORCH: Database Connector Sample With Oracle DB and TR 9.2.5.4 and Above - Groovy And Jython [Updated: 02/02/2024]
  • E1: ORCH Passing JSON Output to an External REST API via Connector Request - What is the Size Limit? - e.g. 200+ Grid Line Records With Multiple Input Parameter Fails. [Updated: 01/03/2024]
  • E1: ORCH: How to Call an External REST API from an Orchestration [Updated: 06/27/2023]
  • E1: ORCH: Is There Any Redirect URI Which Can Be Defined in External Rest Service for E1. [Updated: 05/25/2023]
  • E1: AIS: ORCH: What is the Significance of the MaxExternalResponseSize Parameter in the Rest.ini? [Updated: 05/16/2023]
  • E1: ORCH: How to Assign (Parse) Nested JSON Output (Array Output) Values into Variables in the Connector Output [Updated: 05/01/2023]
  • E1: ORCH How to Pass Array Payload In An Orchestration [Updated: 12/02/2022]
  • E1: ORCH: How to Add Parameters to Orchestrator Connector [Updated: 11/16/2022]
  • E1: ORCH: How to use "AND/OR" Filter For Multiple Fields Using "/v2/dataservice/table/{tableName}" API From the Connector [Updated: 08/30/2022]
  • E1: ORCH: How To Upload a File as an Attachment Which was Retrieved From a Previous Orchestrator Step (Release 22, 9.2.6.2)? [Updated: 03/21/2022]
  • E1: ORCH: How to Pass Output Values from a Service Request (Form, Data, Report, etc) to Connector (External Rest) Body as an Input Variable [Updated: 03/11/2022]
  • E1: ORCH: How to Create a Connector and then Test using Service Request and Orchestration? [Updated: 02/28/2022]
  • E1: ORCH: How to Send a Report (PDF) to a 3rd Party REST Service - Demonstrate This Using ExternalRest Connector with moAdd (/jderest/v2/file/upload) to Attach the Report as an Media Object [Updated: 02/04/2022]
  • E1: ORCH: AIS: How To Call a 3rd Party Web Service (WSDL) From Orchestration [Updated: 08/24/2021]
  • E1: ORCH: Using Connection for External REST - Post with JSON body [Updated: 01/02/2019]
FTP Connector How To and FAQ Documents
  • E1: ORCH: Database Connector Sample With Oracle DB and TR 9.2.5.4 and Above - Groovy And Jython [Updated: 02/02/2024]
  • E1: ORCH: How To Use Orchestrator To Import Data (Parse) From a JSON File Using FTP - Example/Sample Using JRuby And Jython (Tools Release 9.2.6.0 and Higher) [Updated: 02/02/2024]
  • E1: ORCH: How to Assign (Parse) Nested JSON Output (Array Output) Values into Variables in the Connector Output [Updated: 05/01/2023]
  • E1: ORCH: How To Configure The FTP Connection for SFTP (SSH) Protocol [Updated: 01/18/2023]
  • E1: ORCH How To Use Orchestrator To Import Data From a CSV File - Example/Sample [Updated: 11/15/2022]
  • E1: ORCH: How to use "AND/OR" Filter For Multiple Fields Using "/v2/dataservice/table/{tableName}" API From the Connector [Updated: 08/30/2022]
  • E1: ORCH: How to Pass Output Values from a Service Request (Form, Data, Report, etc) to Connector (External Rest) Body as an Input Variable [Updated: 03/11/2022]
  • E1: ORCH: AIS: How To Call a 3rd Party Web Service (WSDL) From Orchestration [Updated: 08/24/2021]
Softcoding Connector How To and FAQ Documents
  • E1: ORCH: Database Connector Sample With Oracle DB and TR 9.2.5.4 and Above - Groovy And Jython [Updated: 02/02/2024]
  • E1: ORCH: How to Assign (Parse) Nested JSON Output (Array Output) Values into Variables in the Connector Output [Updated: 05/01/2023]
  • E1: ORCH: How to use "AND/OR" Filter For Multiple Fields Using "/v2/dataservice/table/{tableName}" API From the Connector [Updated: 08/30/2022]
  • E1: ORCH: How to Pass Output Values from a Service Request (Form, Data, Report, etc) to Connector (External Rest) Body as an Input Variable [Updated: 03/11/2022]
  • E1: ORCH: AIS: How To Call a 3rd Party Web Service (WSDL) From Orchestration [Updated: 08/24/2021]

Orchestrator Logic Extensions

Creating Logic Extensions (Release 9.2.6)

Understanding Logic Extensions

The Orchestrator Studio provides a web-based user interface to create logic extensions. Using logic extensions, you can create business logic to perform operations such as string manipulation, arithmetic calculations, conditions, loops, and even table I/O. Using the logic extensibility framework, you can use the familiar syntax of the JD Edwards Named Event Rules language to create custom logic. The logic extensions component can be added as a step in the orchestration. Logic extensions are created and managed as user-defined objects (UDOs), and therefore they inherit all the lifecycle management and security capabilities of the UDO framework. Logic extensions are ready to run immediately as part of an orchestration.

Click here to view a recording of this feature.

Click here to view an OBE of this feature.

Navigating the Logic Extensions Page The Logic Extensions page displays a list of icons for creating logic extensions. Hover over each icon to view the associated description. The Data Structure tab is displayed by default when you start creating a new logic extension.

Links
Orchestrator Logic Extensions How To and FAQ Documents

Orchestrator Custom Requests

Starting with with Tools Release 9.2.1.4 and Orchestrator 5.1.x, you can create a service request that uses Groovy or Java scripting to execute a custom process or to route data into another database.

Starting with Tools 9.2.4.3, you can call a business function directly from an orchestration.

Links
Custom Service Requests How To and FAQ Documents

Orchestrator Messages Request

Overview

Messages are then sent out to subscribers who need to know that an event has occurred that requires attention. The messages can contain action links to help the recipients act quickly with an appropriate response.

Use a message request if you want an orchestration to send a message to an external email address (requires an SMTP server) or to EnterpriseOne users through the EnterpriseOne Work Center. A message request allows you to send an e-mail message to one or more recipients. You can create the subject and body of the message, including text substitution variables that are populated from previous orchestration steps. The message can include links to EnterpriseOne applications, links to external URLs, links that launch other orchestrations or notifications, and attachments.

You can add a message request to an orchestration to send emails to external email systems or the EnterpriseOne Work Center email system. The following features are supported in a message request:

  • Workflow distribution lists that can be used to send messages to a predefined group of EnterpriseOne users.
  • Message templates from the data dictionary that contain boilerplate text and values related to a particular business process.
  • Links to EnterpriseOne applications.
  • Links to EnterpriseOne reports and BI Publisher reports.
  • Links to URLs.
  • Links to notifications and orchestrations.
Links
Messages Request How To and FAQ Documents

Orchestrator Rules

Orchestrator Rules How To and FAQ Documents
  • E1: ORCH: Rule What Is The Separator For Using multiple Values for "in list" Operator? [Updated: 03/14/2022]
  • E1: ORCH: How to Run Orchestration using XML Input [Updated: 03/08/2022]
  • E1: ORCH: Passing The Exception Message to an Orchestration or Notification on Error [Updated: 02/10/2022]
  • E1: ORCH: How to Test Orchestration Input is Empty / Not populated in Rule [Updated: 09/05/2020]

Orchestrator Cross References

Cross References How To and FAQ Documents

Orchestrator Schedules

Schedules: Creating a Schedule Create a schedule to define how often the Orchestrator should execute an orchestration. You can define a schedule using minutes, hours, days, or a Cron string. Cron is a time-based job scheduler that can be used to schedule jobs to run periodically at fixed times, dates, or intervals (for example, every Tuesday and Friday at 9:00 a.m.).

Adding a Schedule to an Orchestration Adding a schedule to an orchestration does not invoke the orchestration as scheduled. Starting the scheduler is a separate step. After you add a schedule, ask an administrator to start and administer the schedule using the Scheduler page

Links
Scheduler How To and FAQ Documents

Orchestrator Monitor

The EnterpriseOne Orchestrator Monitor (P980060X) is an EnterpriseOne application that enables users to monitor the health and performance of Orchestrator components. It also records any exceptions so that users can take corrective actions to resolve any issues.

The following user defined objects (UDOs) can be monitored with Orchestrator Monitor:

  • Orchestrations
  • Notifications
  • Schedules (Only exception information. It does not provide health details)
Links
Monitor How To and FAQ Documents

Orchestrator Import/Export

Orchestrator Connections

Connections How To and FAQ Documents
  • E1: ORCH: Which Account is Used When an Orchestration is Running and Accessing External Network Folders. [Updated: 04/11/2024]
  • E1: ORCH: How to Decrypt a REST Response Payload Returned From a Third Party [Updated: 10/18/2023]
  • E1: ORCH: How to Create a Connector for Selecting Data From a Table Using a Variable with the EnterpriseOne Database (Read-only) DAD Connection [Updated: 08/03/2023]
  • E1: ORCH: How To Delete Orchestration Connections From Orchestrator Studio User Interface [Updated: 05/23/2023]

Orchestrator Form Extension

Starting with tools release 9.2.3.3 you can use the form extensibility framework to associate orchestration with the events on an EnterpriseOne form.

Beginning with Release 9.2.3.4, you can also associate notifications with the events on a form, invoke orchestrations in the synchronous mode, and map orchestration outputs to the form controls if any output has been defined for the orchestration. With Release 9.2.4, you can associate orchestrations and notifications with the grid row and column events on a form, and map outputs to the controls in an update grid.

Orchestrator Form Extension How To and FAQ Documents

Orchestrator Process Recorder

Creating a Form Request with the JD Edwards EnterpriseOne Orchestrator Process Recorder (Release 9.2.2.4)

The JD Edwards EnterpriseOne Orchestrator Process Recorder enables you to record a series of actions in EnterpriseOne and save those actions as a new form request. This simplified method to create a form request is an alternative to manually creating a form request in the Orchestrator Studio.

> Tutorial

> Tutorial 2

After launching and starting the Process Recorder in EnterpriseOne, you access an application and perform each of the steps to complete the business process or transaction that you want the form request to perform.

The Process Recorder automatically adds inputs to the form request for each field in which you enter data during the recording. The input is the name of the field, and the data you enter becomes the default value. For example, if you click a field called Customer Number and enter 1001, the Process Recorder records an input called Customer Number with a default value of 1001. You can delete, change, or replace the value with a variable by editing the form request in Orchestrator Studio.

When finished, on the last form, you can select any of the controls or grid columns on the form that contain values that you want the form request to return. Starting with EnterpriseOne Tools 9.2.3, you can select return values from any form while recording the form request.

After you save the form request in the Process Recorder, you can open the form request in the Orchestrator Studio, modify it as necessary, and add it to an orchestration.

If you have an open Orchestrator Studio session, you can click the Refresh Cache button on the Orchestrator Client page to access the form requests. (Release 9.2.3.4)

Links
Orchestrator Process Recorder (Record a Process) How To and FAQ Documents

Orchestrator Security

Orchestration Security Considerations Before the EnterpriseOne Orchestrator can process an orchestration, authentication of the JD Edwards EnterpriseOne user ID and password must take place. It is the responsibility of the originator of the service request to tell the orchestration about the user. The user's credentials must be supplied in a basic authorization header or in the JSON body of the request. The user must also have authorized access to the EnterpriseOne application in which the resulting transaction takes place. The following code is an example of credentials in the JSON body of the request: { "username":"JDE", "password":"JDE", "environment":"JDV900", "role":"*ALL" } The AIS service used with orchestrations is stateless; each call passes credentials to establish a separate EnterpriseOne session. After the transaction is complete, the session closes. Orchestrations Guide -> Security:

Locate "Orchestration Security Considerations" section in the Orchestrations guide.

Links
Orchestrator Security How To and FAQ Documents
  • E1: ORCH: Which Account is Used When an Orchestration is Running and Accessing External Network Folders. [Updated: 04/11/2024]
  • E1: ORCH AIS How to Configure SSL/https for Communication Between AIS (includes Orch Studio 9.2.4.x) and HTML - Includes Self-Signed [Updated: 08/10/2023]
  • E1: ORCH: How To Control the "New" Button or Access Control Based on a User ID or E1 Role For Workflow In Orchestrator Studio? [Updated: 05/30/2023]
  • E1: ORCH: How to Setup a "_GLOBALNODE" in E1 to Work With JWT trust Using Orchestration/AIS [Updated: 11/17/2022]
  • E1: ORCH: How to Delete Shared UDO used with Orchestrator [Updated: 06/08/2022]

Orchestrator OMW Promotion

OMW Promotion How To and FAQ Documents
  • E1: ORCH: How "Share/Approve" (Checkin/Checkout) Works for Orchestration UDO Components - P98220U and P98220W [Updated: 03/08/2022]
  • E1: ORCH: How Does Promotion (Promote) Work With Connector With Connections (FTP, REST, DB, etc)? [Updated: 02/10/2022]
  • E1:ORCH Questions on Development and Promoting Objects in Orchestrator Studio [Updated: 06/18/2020]

Orchestrator B98ORCH

Orchestrator B98ORCH How To and FAQ Documents
  • E1: ORCH: Launching orchestrations from EnterpriseOne Events using B98ORCH [Updated: 06/18/2024]
  • E1: ORCH: How to Run B98ORCH Asynchronously? [Updated: 11/22/2022]
  • E1: ORCH: Is it Possible to Populate B98ORCH Response Into a Form Grid? [Updated: 05/19/2021]
  • E1: ORCH: B98ORCH Calling Connectors With JSON Body [Updated: 01/02/2019]
Источник — http://wiki.sgsproject.nichost.ru/index.php?title=JDE_Orchestrator&oldid=108922