With this automation, the user does not have to create an ECO and associate it with the part the user simply creates a part and soon after sees the system-generated ECO containing the part. "Since a Capacitor was just created, now (automatically) create a new Change Order and add that new object on the ECO." When the system recognizes that a Capacitor was just created, and this Event Subscription is invoked, the Subscriber provides the specific instructions and the system runs the Handler that produces the desired outcome: Also, you can see that this Handler mask will work with any Event mask that names a subclass of the Parts class, or the Parts class itself.įinally, a Subscriber mask that names the Event mask and Handler mask is: This handler's name gives the idea that a change order will be created with the new part associated with it. This event type takes an object type (most of them do), so this Event mask specifies Capacitor, a subclass of the Parts class. The name of the Event mask is:Įvery Event mask names an Event Type, in this case the Create Object event type. Let's say the administrator builds on the "Create Object" event type to specify "objects from the Capacitor subclass". Here is an example of names for three masks in a possible Event Subscription. In any case, choose names that help you see at a glance what their use is. System-provided names follow internal conventions, but the provided name may not be unique and you may need to modify the provided name.Ī naming system will be a benefit when you have stored many masks in your Event-node libraries. However, nothing happens unless one (or more) Event Subscription gives the information to the system about what to do when an event type is triggered. and when the Event Subscription is invoked, the configured result is completed by the system.Īs end-users perform normal actions in PLM, the default Event Types may be triggered dozens of times a day. The Event Subscription provides complete instructions for an automation, including what kind of object is to be acted on, what actions will be taken, and what result or outcome will be accomplished by the system.Īn Event Subscription, configured and ready to be invoked, consists of.Īn Event mask – specifies the conditions under which an automation will be invoked, includes an Event Type, an Object Type (often but not always), and additional attributes Īnd a Handler mask or a Notification mask – describes the intended automated result, a Handler mask is a configured Java PX or a configured Script PX a Notification mask is a configured Notification Īnd a Subscriber mask – binds a Handler to an Event, a Subscriber names Event and Handler/Notification masks to work in tandem with additional attributes that refine the Event Subscription's behavior An Event Subscription is a single instance of an "administrator-configured event".
0 kommentar(er)
