1 Understanding JD Edwards EnterpriseOne Notifications

This chapter contains the following topics:


JD Edwards EnterpriseOne Notifications enable you to improve your business efficiency through the use of proactive notifications that are actionable. Proactive notifications enable the system to notify users of business events as they happen without the need for the user to be online.

As a notification designer, you decide and implement the notifications that provide pertinent business information to your users. Users can then choose to subscribe to available notifications and receive updates within EnterpriseOne, as browser pop-up messages, through the Work Center, by email, or by email to SMS (Short Message Service).

Starting with Release 9.2.3, users can also view these messages in the Message Center and on the My Worklist page. See "Message Center" in the JD Edwards EnterpriseOne Tools Foundation Guide for more information.

By creating notifications that are valuable to your subscribers, you enable them to know when key transactions or events occur without even having to log into EnterpriseOne. This close monitoring helps them respond quickly and perform their jobs more efficiently.

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.

How It Works

Notifications use inputs, such as counts from Watchlists or data collected through orchestrations, and apply rules to decide whether a notification message should be dispatched to subscribers. You define what these inputs are, assign them default values if necessary, or allow subscribers to override the inputs so that they can receive notifications more specific to their needs. For example, you might have a notification for when a customer exceeds their credit limit and you allow subscribers to identify specific customers that they want to monitor.

You can use variables and shortcuts in the notification message to give the subscriber more specific information and direct access to an application, enabling the subscriber to respond to the information quickly.

As you create a notification, you define whether it should be unique for each subscriber or if one uniform message to all subscribers meets your business needs.

You can create three types of notifications based on what you are trying to accomplish. The Orchestrator Studio is the tool that you use to create all three types of notifications:

  • Simple Notification. A simple notification provides a way to send reminders or updates and include shortcuts to applications in a notification message. This type of message is not dependent on any business event tied to the data in JD Edwards EnterpriseOne.

  • Watchlist-based Notification. A notification based on a Watchlist enables you to use existing Watchlists to send notification messages that include threshold levels, counts, and application shortcuts to subscribers.

  • Orchestration-based Notification. A notification based on an orchestration enables you to use all of the functionality available in an orchestration and proactively deliver the data to subscribers in a notification message.

    You can also create a notification step within an orchestration.

    See the JD Edwards EnterpriseOne Tools Orchestrator Guide for more information on orchestrations and notification steps in an orchestration.

Using Schedules

A schedule defines how often the system executes a notification. You can define a schedule using minutes, hours, days, or a Cron string (for example, every Tuesday at 2:00 pm). The schedule is then attached to a notification to determine how often the notification runs. You can attach the same schedule to multiple notifications.

As a notification designer you can assign your notifications to existing schedules by picking a schedule from the drop-down list. You may also have privileges to create new schedules, in which case the New Schedule button will be active for you. Schedules are managed as User Defined Objects (UDOs), so you can publish and share your schedules for others to use, and you can use schedules that others have published.

The task of starting, stopping, and managing the scheduler itself is a system administrator task. The scheduler runs as a process on the Application Interface Services (AIS) server. The scheduler is managed using a set of REST APIs, which are documented with all other JD Edwards REST APIs:

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