Creating a Notification

With the JD Edwards EnterpriseOne Orchestrator Studio, you can create notifications that provide pertinent and actionable notification messages to your users.

Important: Remember that when you are ready to "request to publish" a notification, you need to make sure that you also request to publish all components associated with the notification. The administrator also needs to apply the correct view security to the shared components so that when the notification runs, all dependent objects are available and the notification process will not end in error.

To create a notification:

1. On the Orchestrator Studio Home page, click the Notifications icon.

2. On the Notifications side panel, click the New button.

3. On the Notifications design page, enter a unique name for the notification in the Name field. Make sure that it is very descriptive and includes scheduling information for subscribers. For example, you might enter "Check for Purchase Orders Received Every Four Hours," and not "trkPO_h4."

   Note: The name cannot be empty, blank or contain the following characters: ~`'!@#$%^&*()+={[}]|\;:"<,>.?/.

4. Click the Product Code drop-down list to select a product code to associate with the notification. If you leave this field blank, the notification defaults to product code 55.

   This gives an administrator the option to manage UDO security for orchestration components by product code.

5. In the Description field, enter a short description with a maximum of 200 characters.

   This description will show as hover text when your subscribers choose to subscribe to this notification, so this is a good place to tell your subscribers about any inputs they may provide and how often they can expect the notification to run. For example: "This notification allows you to track the status of a purchase order. Enter the purchase order number as input. You will receive updates hourly."

6. Click the Edit Long Description button to provide more detail about the component.

   Use this field to describe the purpose of the notification and any details that differentiate the notification from other notifications that you create.

7. Click the Type drop-down menu and select the appropriate type. The type you choose is very important because it defines the events or conditions on which the notification is sent, as described below:

   • Simple (default). A simple notification does not check for any events or conditions; it simply sends the notification message on the schedule you choose. This type of notification is best suited for informational messages or reminders to your subscribers.

   • Orchestration. An orchestration can be a very powerful way to detect an event or condition upon which you want to send a notification. Orchestrations can read data from JD Edwards tables, invoke JD Edwards applications, and even query external systems. When you create an orchestration you can also define its output, which can then be input into your notification. Refer to the JD Edwards EnterpriseOne Tools Orchestrator Guide for more information about building orchestrations.

   • Watchlist. If you have created a Watchlist in EnterpriseOne you can use that Watchlist as the trigger to send the notification. For example, if you have a Watchlist that monitors the number of backlogged items, you can build a notification that sends that information to subscribers.

8. Enable the Run As Subscriber toggle if you would like to run the notification once for each individual user who is subscribed to the notification. If selected, the subscriber's security settings will be used when the notification is run for them. If you do not select this option, the notification will only be run once with the user information of the person who starts the notification job and all subscribers will receive the same notification message.

9. Enable the Allow Subscriber Overrides toggle if you want to give subscribers the ability to enter override values for the notification inputs in Subscription Manager.

10. At this point, you can click Save to save your notification.

    You can also use Save As and rename an existing notification to create a new one.

    The Orchestrator Studio saves the notification as a "Personal" UDO.

    Caution: If you use Save As to create a copy of a notification, only the notification is copied. The Orchestrator Studio does NOT create a copy of the components that are associated with the notification. That is, both the original notification and the new notification use the same components that comprise the notification. Therefore, in the new notification, do NOT modify the components in any way that would break other notifications that use the same components. You can also click the About link from Manage drop-down menu to understand where else the component is being used, so that you don't break other usages. See "Reusable Orchestration Components" in the JD Edwards EnterpriseOne Tools Orchestrator Guide for Studio Version 8 and Prior.

11. Next, refer to the appropriate sections to complete the remaining parts of the notification: notification inputs, orchestration, Watchlist, rule, message, and schedule.