1. Net Change for Tools Documentation Library
  2. Documentation Updates for EnterpriseOne Tools 9.2.2.4

Documentation Updates for EnterpriseOne Tools 9.2.2.4

The following table contains links to documentation updates in support of EnterpriseOne Tools 9.2.2.4:

Feature

Description

Documentation

Form extension

Form extension is a new user defined object (UDO) that enables users to add available (unused) business view columns to EnterpriseOne forms.

Note that the design mode of the form extensions feature is not available in the Oracle WebCenter Portal, IBM WebSphere Portal, JD Edwards EnterpriseOne for iPad, and JD Edwards EnterpriseOne for Android-based tablets.

See the following topics in the JD Edwards EnterpriseOne Tools Using and Approving User Defined Objects Guide:

See the following topic in the JD Edwards EnterpriseOne Tools Security Administration Guide:

See the following topic in the JD Edwards EnterpriseOne Tools Foundation Guide:

Menu exit personalization

The form personalization functionality has been enhanced to enable users to hide, unhide, and rename menu exits.

See the following topic in the JD Edwards EnterpriseOne Tools Using and Approving User Defined Objects Guide:

Grid header personalization

The grid personalization functionality has been enhanced to enable users to rename grid column headers in the list view and table view grid formats.

See the following topic in the JD Edwards EnterpriseOne Tools Using and Approving User Defined Objects Guide:

See the following topic in the JD Edwards EnterpriseOne Tools Foundation Guide:

Delivered notification content

JD Edwards EnterpriseOne provides preconfigured notification content for EnterpriseOne applications. This content is available for several key roles, business processes, and modules within EnterpriseOne. Users can subscribe to these notifications, and notification designers can personalize them for your unique use cases or use them to seed new ideas for notifications for your specific business needs.

See the following topic in the JD Edwards EnterpriseOne Tools Notifications Guide:

Assigned subscriptions to notifications

The Assigned Subscriptions (P980053X) application provides a manager, business analyst, or administrator the ability to assign subscriptions to groups with a common interest or role as an alternative to every user subscribing individually.

Subscription Manager enables users to work with subscriptions they have created for themselves and now also assigned subscriptions. Updates have been made to the application to reflect this.

See the following topics in the JD Edwards EnterpriseOne Tools Notifications Guide:

See the following topic in the JD Edwards EnterpriseOne Tools Foundation Guide:

Scheduler resilience for notifications and orchestrations

Scheduler resilience enables you to store the scheduled job properties for notifications and orchestrations centrally in the database.

See the following topic in the JD Edwards EnterpriseOne Application Interface Services Server Reference Guide:

  • Configuring Scheduler Resilience

    As part of this update, the Scheduler Administration section in the Notifications Guide and the Orchestrator Guide was moved to the Configuring Scheduler Resilience chapter.

Notifications - Performance characterization

Updates have been made to the notification bell user interface to improve performance.

See the following topic in the JD Edwards EnterpriseOne Tools Foundation Guide:

Orchestrator Process Recorder

The JD Edwards EnterpriseOne Orchestrator Process Recorder enables you to create form requests from within JD Edwards EnterpriseOne applications. The Process Recorder allows a business analyst to walk through a business process program by program, form by form, field by field, and record each step of the process. At the end of the process, the business analyst can save the recorded steps as a form request, which can then be edited in EnterpriseOne Orchestrator Studio 6.1.0 and added to an orchestration.

See the following topic in the JD Edwards EnterpriseOne Tools Orchestrator Guide for Studio Version 8 and Prior:

Defining mapped values and default values in a form request

Orchestrator Studio 6.1.0 enables you to define mapped values and default values in the Order of Execution area. Before, you could only do this in the Available Actions area before adding an action to the Order of Execution. This makes it easier to modify these values, especially when working with a form request that was created using the Orchestrator Process Recorder.

See the following topic in the JD Edwards EnterpriseOne Tools Orchestrator Guide for Studio Version 8 and Prior:

EnterpriseOne Orchestrator file transfer support

Business analysts can create orchestrations that can retrieve a file or send a file to a known external location using FTP and SFTP protocols, or send a file to an external location using the REST protocol.

In Orchestrator Studio 6.1.0, you can create and add an FTP connector or REST connector to an orchestration to enable file transfers with these protocols.

See the following topics in the JD Edwards EnterpriseOne Tools Orchestrator Guide for Studio Version 8 and Prior:

Launch a report as an orchestration step (Orchestrator Studio 6.1.0)

Add a report service request to an orchestration to launch a JD Edwards EnterpriseOne report or batch job.

See the following topic in the JD Edwards EnterpriseOne Tools Orchestrator Guide for Studio Version 8 and Prior:

Orchestration error and exception handling

In Server Manager, you can enable error and exception handling for orchestrations. When enabled, each exception in an orchestration is saved as a single serialized JSON object and stored in a directory on the AIS Server. In addition to storing these files, the directory serves as a buffer for storing orchestration requests if the EnterpriseOne system is down.

See the following topic in the JD Edwards EnterpriseOne Tools Orchestrator Guide for Studio Version 8 and Prior:

Orchestration input enhancements, including support of arrays as inputs (Orchestrator Studio 6.1.0)

To simplify working with orchestration inputs in the Orchestrator Studio, the Orchestration inputs grid was redesigned with three separate expandable grids to categorize manually entered inputs, inputs defined from values returned from other orchestration components, and default system inputs.

After adding a component as an orchestration step, use the “Add Inputs to Orchestration" button to automatically add inputs defined in the component as inputs to the orchestration. This makes it easier to define orchestration inputs that you need to, in turn, map to the inputs defined in an orchestration step or component.

When creating orchestrations, business analysts can include an array as an orchestration input, defining the set of data to pass within the array. You can use an array in two ways: with the orchestration “Iterate Over" feature to repeatedly call a service request for each row in the array; or add to or update a grid by referencing the array name inside the service request at the grid level.

See the following topic in the JD Edwards EnterpriseOne Tools Orchestrator Guide for Studio Version 8 and Prior:

"Select First Row" option changed to "Select Row" in the Form Request design page in Orchestrator Studio 6.1.0

On the Form Request design page, you can use the Select Row action to configure a form request to select the first row in an EnterpriseOne grid. You can enter a variable name for this action, which enables you to map an orchestration input to this variable in order to pass in a specific row to select. Or you can enter default value to specify a specific row to select.

See the following topic in the JD Edwards EnterpriseOne Tools Orchestrator Guide for Studio Version 8 and Prior:

"Select All Rows" option in the Form Request design page in Orchestrator Studio 6.1.0

Use the “Select All Rows" option in the Form Request design page to configure a form request to perform an action on all rows in a grid. The form invoked by the form request must have a feature or button for performing an action on all selected grid grows. For example, if you want to update the PO status for all rows in a grid, add this action to the Order of Execution area and then configure the next action to update the PO status.

See the following topic in the JD Edwards EnterpriseOne Tools Orchestrator Guide for Studio Version 8 and Prior:

Run synchronously option for form requests in Orchestrator Studio 6.1.0

Enabled by default in the Form Request design page, this option ensures that the form request completes all actions before the Orchestrator executes the next step in the orchestration. It also ensures that the events in the EnterpriseOne application are run synchronously.

See the following topic in the JD Edwards EnterpriseOne Tools Orchestrator Guide for Studio Version 8 and Prior:

Orchestrator Studio 6.1.0 - Passing in an application version from an orchestration input

When creating a form request, you can leave the version of the form blank, which gives you the option to pass in the version from an orchestration input.

See the following topic in the JD Edwards EnterpriseOne Tools Orchestrator Guide for Studio Version 8 and Prior:

Additional services in the REST API for AIS Server

With EnterpriseOne Tools 9.2.2.4, the REST API for the AIS Server includes additional services for invoking external REST services, transferring files to external REST services, launching a report or batch job in EnterpriseOne, and administering multiple schedulers for scheduling orchestrations and notifications.

See the JD Edwards EnterpriseOne Tools REST API for the Application Interface Services Server Guide.

Oracle Application Development Framework (ADF) 12.2.1.3 Certification

Verified support of Oracle ADF 12.2.1.3 to create EnterpriseOne ADF applications.

See the following topic in the JD Edwards EnterpriseOne Tools Deploying and Developing Oracle Application Development Framework (ADF) Applications for EnterpriseOne: