About Custom Subscriptions

By default, the apps are configured to allow users to subscribe to most events that would possibly concern them. For other events, or for custom objects, you can define additional subscriptions. Defining a subscription involves creating an events menu with a command for each event that you want to allow users to subscribe to, then mapping that menu to an object or relationship where the event occurs. You also need to define the notification that will be sent to users who subscribe to the event, and a trigger to send that notification when the event occurs.

This chart shows the administrative objects (menu and command) and business objects (notification and trigger) required for a subscription. As an example, the chart shows how these objects are used to create a subscription for a single Decision event. In this case, when a decision is attached to an object (using the Decision relationship) subscribed users are notified.

Before you create custom subscriptions, you should understand how triggers and macros work. For more information, see Legacy ENOVIA Web Apps Customization Guide: Triggers and MQL Command Reference: Appendix: Macros. You should also be familiar with the schema used to define the event. For the example subscription, the event occurs when a connection is made between two objects.

The events menu does not display from a toolbar like other menus. Instead, it is used to populate the dialog box where uses select events to subscribe to for the object.