Home / Educational Content / JD Edwards / JD Edwards Blogs / A Breakdown of JD Edwards EnterpriseOne Notifications

A Breakdown of JD Edwards EnterpriseOne Notifications

Shelby Klingerman, Content Curator |

JD Edwards EnterpriseOne Notifications were introduced to improve business efficiency by creating more proactive users. Users can be notified of business events as they happen, and they don’t need to be online to be connected and take action. Notifications were introduced in EnterpriseOne Tools 9.2.2.1 and were enhanced in Tools 9.2.2.6. They are available in EnterpriseOne applications 9.0, 9.1 and 9.2. Oracle’s White Paper on Notifications breaks down everything you need to know about Notifications.

Get the Highlights

Types of Notifications

Notifications based on One View Watchlists provide the notification designer with information from a Watchlist like the total number of records or number of records exceeded a warning or critical threshold.

Notifications can also be based on Orchestrations and can include information like data requests and form service requests.

A simple notification is a text message of a certain size that is delivered directly through the notification mechanism. It does not do any processing and does not return any data from the EnterpriseOne application. Think of it as a simple email with a subject and body. The only concern in a performance analysis is the payload size. Simple notifications can be as large as a 12-kilobyte payload message.

How They Work

Notifications are EnterpriseOne User Defined Objects (UDOs) and have all the security and management of other UDOs. Notifications, orchestrations, and their subcomponents are managed by EnterpriseOne as user defined objects (UDOs). As designers create and modify notifications and orchestrations using Orchestrator Studio, the Studio automatically stores the objects in the UDO repository. The objects execute on the AIS server, and the Studio also automatically deploys the objects to the AIS server where they are cached.

Designing Notifications

Business analysts can use Orchestrator Studio to design, test, deploy and schedule Notifications. Orchestrator Studio requires an Oracle Application Development Framework (ADF) application. It also needs its own WebLogic Server and ADF Runtime environment. For step-by-step instructions on how to create and schedule a notification, check out the JD Edwards EnterpriseOne Tools Notifications Guide.

Delivery Methods

Notifications can be delivered to users through the Notification Bell within JD Edwards, in Work Center, by email or text message. Users can now be notified about business events when they are on the move or simply not logged into JD Edwards. Delivery methods can be configured for individual users through “My Subscriptions” (Subscription Manager application).

Learn More

To learn more about Notifications, how they work, and how you can utilize them within your organization, check out the full White Paper from Oracle.

Want hear more directly from Oracle about your JD Edwards software, in-person? Discover everything available at COLLABORATE 19, the Technology and Applications Forum for the Oracle Community, April 7-11, 2019, in San Antonio. Learn more, and follow #C19TX on Twitter to stay up-to-date on all things COLLABORATE 19!

A Breakdown of JD Edwards EnterpriseOne Notifications