1. Notifications Guide
  2. Understanding Notifications and Orchestrator Studio

Understanding Notifications and Orchestrator Studio

Important: This chapter has been updated in support of Orchestrator Studio 9.2.4. The features related to this release are notated with the release number. Orchestrator Studio 9.2.4 is the latest version which requires a minimum of EnterpriseOne Tools 9.2.4.0. If you have not installed Orchestrator Studio 9.2.4, see "Getting Stated" in the JD Edwards EnterpriseOne Tools Orchestrator Guide. Instructions for using prior versions of the Orchestrator Studio are in the appendices of this guide.

Just like all other orchestration components, notifications and schedules:

  • Are created using Orchestrator Studio design pages, which have the standard design page features.

  • Are reusable components.

  • Are saved and managed as user defined objects (UDOs) in EnterpriseOne.

  • Utilize the standard UDO life cycle features (for example, can be published or shared).

For more information, see:

You can use the Orchestrator Studio to create the following components related to notifications:

  • Notifications. A notification is an object that enables the system to notify users of business events as they happen without the need for the user to be online. You can specify that the notification execute a Watchlist or an orchestration. You define what the notification message looks like and whether it includes a shortcut to an application. You can also attach report output from an EnterpriseOne report or BI Publisher report, and you can link to an orchestration, notification, or URL. You attach the schedule for when it runs, and any rules that must be met to send the notification message.

  • Schedules. A schedule defines how often the system runs a particular job. A schedule consists of a time interval in minutes, hours, or days, or a Cron string. A schedule can be attached to multiple notifications or orchestrations to determine how often they run. The scheduler runs as a process on the Application Interface Services (AIS) server and is managed using a set of REST APIs.

  • Orchestrations. An orchestration is a high-level object that provides a unique name for an orchestration process. The orchestration is where you define the inputs for the orchestration, the expected incoming data. It also includes orchestration steps, which are invocations to the other components. When the Orchestrator invokes an orchestration, it processes the steps defined in the orchestration to enable the transfer of data within EnterpriseOne or between third-party sources and EnterpriseOne.

  • Rules. A rule on a notification is used to determine whether the message is dispatched to the subscribers. The rule must evaluate to true in order for the message to be dispatched. If there is no rule specified, the message is always dispatched.