JDE Orchestrator: различия между версиями
Yarkin.m (обсуждение | вклад) |
Yarkin.m (обсуждение | вклад) м |
||
(не показано 113 промежуточных версий этого же участника) | |||
Строка 1: | Строка 1: | ||
− | * Orchestrator | + | * Orchestrator Studio Version 9.2.4 |
− | * Orchestrator | + | * Orchestrator Studio Version 8 and Prior |
+ | {| | ||
+ | | | ||
+ | {| class="wikitable" style="text-align: center;" | ||
+ | |+ Framework | ||
+ | |- style="height:100px;" | ||
+ | ! style="width:150px; color:orange" | Orchestrations </br> [[JDE_Orchestrator#Orchestrator Orchestrations | [Overview]]] [[JDE_Orchestrator#Orchestrator Orchestrations | [wiki] ]] | ||
+ | |- style="height:100px;" | ||
+ | ! style="width:150px; color:red" | Notifications </br> [[JDE_Orchestrator#Orchestrator Notifications | [Overview] ]] [[JDE_Orchestrator#Orchestrator Notifications| [wiki] ]] | ||
+ | |- style="height:100px;" | ||
+ | ! 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; " | ||
+ | |+ Orchestrator Componets | ||
+ | |- style="height:100px;" | ||
+ | | 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;" | ||
+ | | 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;" | ||
+ | | 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" | | ||
+ | {| class="wikitable" style="text-align: center; color:blue;" | ||
+ | |+ Orchestrator Services | ||
+ | |- 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 | ||
+ | |} | ||
+ | |- | ||
+ | | 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]; | * Нотификация (Notifications) [Release 9.2.2]; | ||
* График (Schedules) [Release 9.2.2]; | * График (Schedules) [Release 9.2.2]; | ||
* Process Recorder [Release 9.2.2.4]; | * 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)] | ||
=== Orchestrator Orchestrations === | === 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: | ||
+ | |||
+ | <code> http://<AIS_server>:<port>/jderest/orchestrator/<orchestrationname> </code> | ||
+ | |||
+ | 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 | ||
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2799676.2 E1: ORCH: Orchestrator Orchestrations Reference Center] (Doc ID 2799676.2) | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2799676.2 E1: ORCH: Orchestrator Orchestrations Reference Center] (Doc ID 2799676.2) | ||
: Orchestrator Orchestrations How To and FAQ Documents: | : Orchestrator Orchestrations How To and FAQ Documents: | ||
Строка 61: | Строка 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 | ||
Строка 71: | Строка 129: | ||
::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2654791.1 E1:ORCH: How to Assign Notifications to Multiple Users in EnterpriseOne?] [Updated: 03/31/2020] | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2654791.1 E1:ORCH: How to Assign Notifications to Multiple Users in EnterpriseOne?] [Updated: 03/31/2020] | ||
− | === Orchestrator | + | === Orchestrator Workflows === |
− | * E1: ORCH: Orchestrator | + | 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 | ||
+ | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2908654.2 E1: ORCH: Orchestrator Workflows Reference Center] (Doc ID 2908654.2) | ||
+ | : Orchestrator Workflows How To and FAQ Documents | ||
+ | :* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2952425.1E1: 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] | ||
+ | :* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2901823.1 E1: ORCH: WRKFLW: New Feature for Release 23, Tools Release 9.2.7.0 Call Orchestration/Notification From Workflow] [Updated: 10/20/2022] | ||
+ | |||
+ | === 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 | |
− | *E1: ORCH: Orchestrator | + | * [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 | |
− | :* E1: ORCH: | + | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2972469.1 E1: ORCH: Form Request - Row / Grid Filtering Option For The "Row Update" Does Not Work For a "Date" Column] [Updated: 09/05/2023] |
− | :* E1: ORCH: | + | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2779029.1 E1: ORCH: How to Create Multiple Sales Orders With Multiple SO Lines By Sending a Multiple JSON Array Orchestration Input ( Object )] [Updated: 08/30/2023] |
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2934455.1 E1: ORCH: How to include Defined Query when Recording a Process to Create a Form Service Request (FSR)] [Updated: 03/14/2023] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2591608.1 E1: ORCH: How to Pass Output Values from one Form Service Request to Another Form Service Request] [Updated: 10/12/2022] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2614484.1 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] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2733709.1 E1: ORCH: How To Iterate Over a Form Service Request Without Grid Records - Example: P0015A work With Currency Exchange Rate] [Updated: 03/09/2022] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2729899.1 E1:ORCH: Orchestrator does not Support Creating Array Variables from Subform Grids Forms] [Updated: 11/18/2020] | ||
− | === Orchestrator | + | === 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= | + | * [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 |
− | ::* E1: ORCH: How to | + | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2775242.1 E1: ORCH: Is it Possible to Create Dynamic Runtime Queries on E1 Tables Using Orchestrator REST API?] [Updated: 04/10/2023] |
− | ::* E1: ORCH: | + | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2775242.1 E1: ORCH: How to Iterate Over the Results From a Data Request?] [Updated: 03/11/2022] |
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2775242.1 E1: ORCH: AIS: How to Invoke a Data Service Request For Accessing Table/Views Using Orchestration or AIS REST APIs - "You are not authorized to access this table or view"] [Updated: 05/03/2021] | ||
=== 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 | ||
Строка 123: | Строка 203: | ||
::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2479495.1 E1: ORCH Pass Through Value From Data Request To Report Service Request In Orchestrator] [Updated: 11/30/2018] | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2479495.1 E1: ORCH Pass Through Value From Data Request To Report Service Request In Orchestrator] [Updated: 11/30/2018] | ||
− | === Orchestrator | + | === Orchestrator Attachments === |
− | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id= | + | ; 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. |
− | ::* E1: ORCH: How " | + | |
− | ::* E1: ORCH: How | + | Using Attachments, you can perform the following actions for a specified key: |
− | ::* E1:ORCH | + | * 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) | ||
+ | : Attachments How To and FAQ Documents | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?d=2901144.1 E1: ORCH: How to Attach the CSV Output from a Data Request to a Message Service (Email the attachment)] [Updated: 12/29/2023] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2941949.1 E1: ORCH: When Using Record a Process Can Adding an Attachment Also be Recorded?] [Updated: 05/23/2023] | ||
+ | |||
+ | === 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 | ||
+ | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2729965.2 E1: ORCH: Orchestrator Connector Reference Center] (Doc ID 2729965.2) | ||
+ | |||
+ | : 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 === | === 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 | ||
Строка 167: | Строка 324: | ||
::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2901832.1 E1: ORCH: LE: New Feature Release 23 Tools Release 9.2.7.0 Array and Aggregation Support in Logic Extensions] [Updated: 10/20/2022] | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2901832.1 E1: ORCH: LE: New Feature Release 23 Tools Release 9.2.7.0 Array and Aggregation Support in Logic Extensions] [Updated: 10/20/2022] | ||
::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2901820.1 E1: ORCH: BSFN: Is There A Wait Function That Can be Used in Logic Extensions (LEX) in Orchestrator Studio] [Updated: 10/10/2022] | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2901820.1 E1: ORCH: BSFN: Is There A Wait Function That Can be Used in Logic Extensions (LEX) in Orchestrator Studio] [Updated: 10/10/2022] | ||
+ | |||
+ | === 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 | ||
+ | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2725378.2 E1: ORCH: Orchestrator Custom Requests Reference Center] (Doc ID 2725378.2) | ||
+ | : Custom Service Requests How To and FAQ Documents | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2905923.1 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] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2731194.1 E1: ORCH: How To Create an Orchestration to Export EnterpriseOne Data to CSV, JSON, and XML Formats - OBE] [Updated: 05/23/2023] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2794768.1 E1:ORCH: Are the "IF condition" and "FOR" Statements Supported in Groovy for a Custom Service Request] [Updated: 07/26/2021] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2464581.1E1: ORCH: Can You Return an ArrayList From Groovy Custom Service Request to be used in Subsequent Steps?] [Updated: 11/05/2018] | ||
=== 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 | ||
Строка 180: | Строка 364: | ||
::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2488444.1 E1: ORCH: Message Center P980051X Application Showing Blank Screen] [Updated: 12/25/2018] | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2488444.1 E1: ORCH: Message Center P980051X Application Showing Blank Screen] [Updated: 12/25/2018] | ||
::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2364388.1 E1: ORCH: How To Update Existing Emails (Multiple) Using Orchestrator] [Updated: 02/28/2018] | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2364388.1 E1: ORCH: How To Update Existing Emails (Multiple) Using Orchestrator] [Updated: 02/28/2018] | ||
+ | |||
+ | === Orchestrator Rules === | ||
+ | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=ID 2725385.2 E1: ORCH: Orchestrator Rules Reference Center] (Doc ID 2725385.2) | ||
+ | : 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 === | ||
+ | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2725356.2 E1: ORCH: Orchestrator Cross References Reference Center] (Doc ID 2725356.2) | ||
+ | : Cross References How To and FAQ Documents | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2648153.1 E1: ORCH: A Simple Cross-Reference Example to Validate The Functionality.] [Updated: 01/31/2021] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2297347.1 E1: ORCH: How To Use Cross Reference with Multiple Line Items on an Order with Orchestrator Studio?] [Updated: 03/18/2019] | ||
+ | |||
+ | === 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 | ||
+ | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2846750.2 E1: ORCH: Orchestrator Schedules Reference Center] (Doc ID 2846750.2) | ||
+ | : Scheduler How To and FAQ Documents | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2818323.1 E1: ORCH: Frequently Asked Questions for Orchestrator Scheduler] [Updated: 12/13/2023] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2760145.1 E1: ORCH: How to Start/Stop a Scheduler Server, Start/Stop a Scheduled Job, List Scheduled Jobs Manually using Postman - Scheduler REST APIs] [Updated: 02/24/2022] | ||
+ | |||
+ | === 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 | ||
+ | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2725416.2 E1: ORCH: Orchestrator Monitor (P980060X) Reference Center] (Doc ID 2725416.2) | ||
+ | : Monitor How To and FAQ Documents | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2976525.1 E1: ORCH: How to Install / Configure Orchestrator Monitor Including UDO, ESU, INI setup [Updated: 07/11/2024] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=3023538.1 E1: ORCH: Enhancement Request for Monitor to Display Running Orchestrations [Updated: 05/17/2024] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2634404.1 E1: ORCH: How To Remove (Purge) Orchestration Health Monitor Data [Updated: 03/19/2024] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2975046.1 E1: ORCH: Orchestrator Monitor Release 23 TR 9.2.7.4 now Includes Run Details for Orchestrations, Notifications and REST APIs [Updated: 09/21/2023] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2913018.1 E1: ORCH: What is the Purpose of the Trace Step button in Orchestration Monitor? [Updated: 12/09/2022] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2588133.1 E1: ORCH: Orchestrator Monitor Exception Alerts And Exception Records from F980060 Table [Updated: 04/02/2020] | ||
+ | |||
+ | === Orchestrator Import/Export === | ||
+ | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2725375.2 E1: ORCH: Orchestrator Import/Export Reference Center] (Doc ID 2725375.2) | ||
+ | |||
+ | === Orchestrator Connections === | ||
+ | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2846191.2 E1: ORCH: Orchestrator Connections Reference Center] (Doc ID 2846191.2) | ||
+ | : 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 === | === 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. | ||
+ | |||
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2799675.2 E1: ORCH: Orchestrator Form Extension Reference Center] (Doc ID 2799675.2) | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2799675.2 E1: ORCH: Orchestrator Form Extension Reference Center] (Doc ID 2799675.2) | ||
: Orchestrator Form Extension How To and FAQ Documents | : Orchestrator Form Extension How To and FAQ Documents | ||
Строка 189: | Строка 432: | ||
::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2607560.1 E1: ORCH: Iterate Over Grid Data Functionality When Calling Orchestration From A Interactive Application Form Extension Button.] [Updated: 11/26/2019] | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2607560.1 E1: ORCH: Iterate Over Grid Data Functionality When Calling Orchestration From A Interactive Application Form Extension Button.] [Updated: 11/26/2019] | ||
− | === Orchestrator | + | === Orchestrator Process Recorder === |
− | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id= | + | Creating a Form Request with the JD Edwards EnterpriseOne Orchestrator Process Recorder (Release 9.2.2.4) |
− | + | ||
− | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id= | + | 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. |
− | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id= | + | |
+ | > 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 | ||
+ | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2914793.2 E1: ORCH: Orchestrator Process Recorder (Record a Process) Reference Center] (Doc ID 2914793.2) | ||
+ | |||
+ | :Orchestrator Process Recorder (Record a Process) How To and FAQ Documents | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2952425.1 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] | ||
+ | ::* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2901823.1 E1: ORCH: WRKFLW: New Feature for Release 23, Tools Release 9.2.7.0 Call Orchestration/Notification From Workflow] [Updated: 10/20/2022] | ||
+ | |||
+ | === 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: | ||
+ | * https://docs.oracle.com/en/applications/jd-edwards/cross-product/9.2/eotos/orchestrator-guide.pdf | ||
+ | Locate "Orchestration Security Considerations" section in the Orchestrations guide. | ||
+ | |||
+ | ;Links | ||
+ | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2799686.2 E1: ORCH: Orchestrator Security Reference Center] (Doc ID 2799686.2) | ||
+ | : 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 === | ||
+ | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2725467.2 E1: ORCH: Orchestrator OMW Promotion Reference Center] (Doc ID 2725467.2) | ||
+ | : 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 | + | === Orchestrator B98ORCH === |
− | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id= | + | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=2724996.2 E1: ORCH: Orchestrator B98ORCH Reference Center] (Doc ID 2724996.2) |
+ | : 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] |
Текущая версия на 12:11, 2 октября 2024
- Orchestrator Studio Version 9.2.4
- Orchestrator Studio Version 8 and Prior
|
| ||||||||||||||||||
| |||||||||||||||||||
|
Компоненты Orchestration (Orchestration components) [Release 9.2.1];
- Нотификация (Notifications) [Release 9.2.2];
- График (Schedules) [Release 9.2.2];
- Process Recorder [Release 9.2.2.4];
Содержание
- 1 Orchestrator Studio Version 9.2.4+
- 1.1 Orchestrator Orchestrations
- 1.2 Orchestrator Notifications
- 1.3 Orchestrator Workflows
- 1.4 Orchestrator Form Request
- 1.5 Orchestrator Data Requests
- 1.6 Orchestrator Reports
- 1.7 Orchestrator Attachments
- 1.8 Orchestrator Connector
- 1.9 Orchestrator Logic Extensions
- 1.10 Orchestrator Custom Requests
- 1.11 Orchestrator Messages Request
- 1.12 Orchestrator Rules
- 1.13 Orchestrator Cross References
- 1.14 Orchestrator Schedules
- 1.15 Orchestrator Monitor
- 1.16 Orchestrator Import/Export
- 1.17 Orchestrator Connections
- 1.18 Orchestrator Form Extension
- 1.19 Orchestrator Process Recorder
- 1.20 Orchestrator Security
- 1.21 Orchestrator OMW Promotion
- 1.22 Orchestrator B98ORCH
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
- E1: ORCH: Orchestrator Orchestrations Reference Center (Doc ID 2799676.2)
- Orchestrator Orchestrations How To and FAQ Documents:
- E1: ORCH: How to Attach the CSV Output from a Data Request to a Message Service (Email the attachment) [Updated: 12/29/2023]
- E1: ORCH: Output File Handling In Orchestrations Using CSV Format[Updated: 07/21/2023]
- E1: ORCH: PKG: How to Build a Package from Orchestration? [Updated: 03/17/2023]
- E1: ORCH: Is There a Way to Format Orchestration Input Variables (e.g. Convert String to Upper-Case) Without Using BSFN or Custom Step? (Manipulate Input Option) [Updated: 02/28/2023]
- E1: ORCH: How To Use Output Grid to File to generate Output in CSV, JSON,XML [Updated: 01/16/2023]
- E1: ORCH: How to Pass Output Values from one Form Service Request to Another Form Service Request [Updated: 10/12/2022]
- E1: ORCH: Is there a way to Compare Orchestrations between 2 Environments? [Updated: 09/29/2022]
- E1: ORCH: How to Format a Date Which is Being Returned From a Logic Extension Step [Updated: 08/10/2022]
- E1: ORCH: How to Delete Shared UDO used with Orchestrator [Updated: 06/08/2022]
- E1: ORCH: How to Iterate Over Multiple Records From a CSV File - Fetch All The Records From a CSV File and Validate if the Same Info. Exists In F0117. If It Does Not Exist, Then Insert The Record. [Updated: 05/26/2022]
- E1: ORCH: How are the System Values including 'Orchestration Inputs' Used in Orchestration Mapping? [Updated: 04/13/2022]
- E1: ORCH: Request To Create A Package Build/Deploy Flow Using Orchestration To Automate and Schedule It. (includes Define, Promote, Build and Deploy) [Updated: 03/23/2022]
- E1: ORCH: Is There A Way To Save Values From One Record From a CSV File and Compare the Value With The Next Record in the CSV file ? - How to use Orch Variables. [Updated: 03/09/2022]
- E1: ORCH: How "Share/Approve" (Checkin/Checkout) Works for Orchestration UDO Components - P98220U and P98220W [Updated: 03/08/2022]
- E1: ORCH: How To Update All Lines For Sales Order With The Same Value [Updated: 02/21/2022]
- E1: ORCH: How to Setup Text Substitution With Orchestrator Studio 9.2.4. [Updated: 02/08/2022]
- E1: ORCH: NEW Enhancements included in Orchestrator Studio with Tools Release 9.2.6 (Release 22) [Updated: 10/12/2021]
- E1: ORCH: Orchestration’s Ability To Encrypt/decrypt Using PGP using SFTP and FTP [Updated: 05/26/2020]
- E1: ORCH: How To View the Orchestration JSON Input in EnterpriseOne? TR 9.2.3.x and above [Updated: 10/02/2019]
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
- E1: ORCH: Orchestrator Notifications Reference Center (Doc ID 2725461.2)
- Notifications How To and FAQ Documents
- E1: ORCH: How to Create a Simple Notifications in Orchestrator Studio - External Email, Work Center and Bell. [Updated: 04/20/2023]
- E1: ORCH: Passing The Exception Message to a Notification / Email for Only Failed Transactions (Continue on Error) - Parse the Exception Message. [Updated: 09/27/2022]
- E1: ORCH: How to Delete Shared UDO used with Orchestrator [Updated: 06/08/2022]
- ORCH: How To Create a Notification That Filters Data Based On the Subscription Input Override [Updated: 02/25/2022]
- E1: ORCH How to Show/Remove "My Subscription" and "Assign Subscription" Under "Manage Notification" Personalization Option For E1 Users/Role. [Updated: 02/12/2022]
- E1: ORCH: How To Create A Notification Based On Orchestration With Information From Orchestration Output [Updated: 02/07/2022]
- E1:ORCH: How to Assign Notifications to Multiple Users in EnterpriseOne? [Updated: 03/31/2020]
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
- E1: ORCH: Orchestrator Workflows Reference Center (Doc ID 2908654.2)
- 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
- E1: ORCH: Orchestrator Form Request Reference Center (Doc ID 2834816.2)
Form Service Request How To and FAQ Documents
- E1: ORCH: Form Request - Row / Grid Filtering Option For The "Row Update" Does Not Work For a "Date" Column [Updated: 09/05/2023]
- E1: ORCH: How to Create Multiple Sales Orders With Multiple SO Lines By Sending a Multiple JSON Array Orchestration Input ( Object ) [Updated: 08/30/2023]
- E1: ORCH: How to include Defined Query when Recording a Process to Create a Form Service Request (FSR) [Updated: 03/14/2023]
- E1: ORCH: How to Pass Output Values from one Form Service Request to Another Form Service Request [Updated: 10/12/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 Iterate Over a Form Service Request Without Grid Records - Example: P0015A work With Currency Exchange Rate [Updated: 03/09/2022]
- E1:ORCH: Orchestrator does not Support Creating Array Variables from Subform Grids Forms [Updated: 11/18/2020]
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
- E1: ORCH: Orchestrator Data Requests Reference Center (Doc ID 2725398.2)
- Data Request How To and FAQ Documents
- 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 Iterate Over the Results From a Data Request? [Updated: 03/11/2022]
- E1: ORCH: AIS: How to Invoke a Data Service Request For Accessing Table/Views Using Orchestration or AIS REST APIs - "You are not authorized to access this table or view" [Updated: 05/03/2021]
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
- E1: ORCH: Orchestrator Reports Reference Center (Doc ID 2846181.2)
- Reports Request How To and FAQ Documents
- E1: ORCH: Report Service Request with Override Version on Processing Options (PO) - Does the Overriden PO Value Permanently Affects the Version PO Value or Only When Orchestration is Executed [Updated: 02/27/2024]
- E1: ORCH: How To Output Processing Option Values From A Called Report [Updated: 10/10/2023]
- E1: ORCH: How to Change Processing Option for a Report Run from Orchestration [Updated: 08/25/2023]
- E1: ORCH: How To Allow For UBE Completion Before Next Step In Orchestration to Run - wait() sleep() [Updated: 04/19/2023]
- E1: ORCH: How to Attach PDF from Report Service Request (Regular and BIP/RD) by Message Service Request [Updated: 11/15/2021]
- E1: ORCH Pass Through Value From Data Request To Report Service Request In Orchestrator [Updated: 11/30/2018]
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
- E1: ORCH: Orchestrator Attachments Reference Center (Doc ID 2908321.2)
- 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
- E1: ORCH: Orchestrator Connector Reference Center (Doc ID 2729965.2)
- 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
- E1: ORCH: Orchestrator Logic Extensions Reference Center (Doc ID 2908653.2)
- Orchestrator Logic Extensions How To and FAQ Documents
- E1: ORCH: Logic Extension - How to Fetch Records From a Table And Based On the Result Of the 1st Table, Update Another Table Using Table I/O (Array) 9.2.7.0 and above [Updated: 02/13/2024]
- E1: ORCH: Can a Logic Extension be Called After the Cancel (X) Button has Been Clicked to Display a Warning Message and Prompt Y/N? [Updated: 07/19/2023]
- E1: ORCH: Are Logic Extensions Included In The Decustomizer (R9540DC - Decustomizer Dataload Report)? [Updated: 01/20/2023]
- E1: ORCH: LE: New Feature Release 23 Tools Release 9.2.7.0 Array and Aggregation Support in Logic Extensions [Updated: 10/20/2022]
- E1: ORCH: BSFN: Is There A Wait Function That Can be Used in Logic Extensions (LEX) in Orchestrator Studio [Updated: 10/10/2022]
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
- E1: ORCH: Orchestrator Custom Requests Reference Center (Doc ID 2725378.2)
- Custom Service Requests How To and FAQ Documents
- 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 Create an Orchestration to Export EnterpriseOne Data to CSV, JSON, and XML Formats - OBE [Updated: 05/23/2023]
- E1:ORCH: Are the "IF condition" and "FOR" Statements Supported in Groovy for a Custom Service Request [Updated: 07/26/2021]
- ORCH: Can You Return an ArrayList From Groovy Custom Service Request to be used in Subsequent Steps? [Updated: 11/05/2018]
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
- E1: ORCH: Orchestrator Messages Request Reference Center (Doc ID 2829064.2)
- Messages Request How To and FAQ Documents
- E1: ORCH: How to Attach the CSV Output from a Data Request to a Message Service (Email the attachment) [Updated: 12/29/2023]
- E1: ORCH: How to Specify the Sender Email Address For Notification and Message Request [Updated: 08/23/2023]
- E1: ORCH: The Formatted Text within a Message Subject Is Not Included In Email as Expected [Updated: 04/19/2023]
- E1: ORCH: How to Insert Carriage Return/Line Feed Into Message Request Within a Logic Extension [Updated: 01/27/2023]
- E1: ORCH: My Worklist and Message Center [Updated: 12/07/2021]
- E1: ORCH: How to Attach PDF from Report Service Request (Regular and BIP/RD) by Message Service Request [Updated: 11/15/2021]
- E1: ORCH: Is there a Way to Format the Text in a Message Service Request? [Updated: 08/31/2020]
- E1: ORCH: Message Center P980051X Application Showing Blank Screen [Updated: 12/25/2018]
- E1: ORCH: How To Update Existing Emails (Multiple) Using Orchestrator [Updated: 02/28/2018]
Orchestrator Rules
- 2725385.2 E1: ORCH: Orchestrator Rules Reference Center (Doc ID 2725385.2)
- 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
- E1: ORCH: Orchestrator Cross References Reference Center (Doc ID 2725356.2)
- Cross References How To and FAQ Documents
- E1: ORCH: A Simple Cross-Reference Example to Validate The Functionality. [Updated: 01/31/2021]
- E1: ORCH: How To Use Cross Reference with Multiple Line Items on an Order with Orchestrator Studio? [Updated: 03/18/2019]
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
- E1: ORCH: Orchestrator Schedules Reference Center (Doc ID 2846750.2)
- 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
- E1: ORCH: Orchestrator Monitor (P980060X) Reference Center (Doc ID 2725416.2)
- Monitor How To and FAQ Documents
- E1: ORCH: How to Install / Configure Orchestrator Monitor Including UDO, ESU, INI setup [Updated: 07/11/2024
- E1: ORCH: Enhancement Request for Monitor to Display Running Orchestrations [Updated: 05/17/2024
- E1: ORCH: How To Remove (Purge) Orchestration Health Monitor Data [Updated: 03/19/2024
- E1: ORCH: Orchestrator Monitor Release 23 TR 9.2.7.4 now Includes Run Details for Orchestrations, Notifications and REST APIs [Updated: 09/21/2023
- E1: ORCH: What is the Purpose of the Trace Step button in Orchestration Monitor? [Updated: 12/09/2022
- E1: ORCH: Orchestrator Monitor Exception Alerts And Exception Records from F980060 Table [Updated: 04/02/2020
Orchestrator Import/Export
- E1: ORCH: Orchestrator Import/Export Reference Center (Doc ID 2725375.2)
Orchestrator Connections
- E1: ORCH: Orchestrator Connections Reference Center (Doc ID 2846191.2)
- 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.
- E1: ORCH: Orchestrator Form Extension Reference Center (Doc ID 2799675.2)
- Orchestrator Form Extension How To and FAQ Documents
- E1: ORCH: FORMEXTNS: Is There a Way to Validate Data Entered on Form so That When Orchestration/Logic Extension Throws an Error, the Action of Saving is Stopped [Updated: 07/22/2024]
- E1: ORCH: How To Get The Orchestration Output In E1 Application Using Form Extension [Updated: 04/06/2023]
- E1: ORCH: How To Trigger an Orchestration From The OK Button In E1 Application Using Form Extension [Updated: 03/08/2022]
- E1: ORCH: Iterate Over Grid Data Functionality When Calling Orchestration From A Interactive Application Form Extension Button. [Updated: 11/26/2019]
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
- E1: ORCH: Orchestrator Process Recorder (Record a Process) Reference Center (Doc ID 2914793.2)
- 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
- E1: ORCH: Orchestrator Security Reference Center (Doc ID 2799686.2)
- 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
- E1: ORCH: Orchestrator OMW Promotion Reference Center (Doc ID 2725467.2)
- 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
- E1: ORCH: Orchestrator B98ORCH Reference Center (Doc ID 2724996.2)
- 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]