Microsoft Dynamics NAV 2016 - How to Use Trigger Events - Part 1
Hi All,
Recap - "Till Now We Have Discussed the Concept of Events and Subscription With an Example".
If you are missing the Story, Refer Table of Index For Events & Subscriptions.
Let's start it with What Microsoft Says About Events, Publisher and Subscribers.
> An event is the declaration of the occurrence or change in the application. An event is declared by a C/AL function, which is referred to as an event publisher function. An event publisher function is comprised of a signature only and does not execute any code.
> A publisher is the object that contains event publisher function that declares the event. The publisher exposes an event in the application to subscribers, essentially providing them with a hook-up point in the application. Publishing an event does not actually do anything in the application apart from making the event available for subscription.
> A subscriber listens for and handles a published event. A subscriber is a C/AL function that subscribes to a specific event publisher function and includes the logic for handling the event. When an event is raised, the subscriber function is a called and it code is run.
If you don't understand what above statement says don't worry I will make sure that all doubts get clear when we finish this series about Event, Publisher and Subscribers.
Read Complete Article »
Recap - "Till Now We Have Discussed the Concept of Events and Subscription With an Example".
If you are missing the Story, Refer Table of Index For Events & Subscriptions.
Let's start it with What Microsoft Says About Events, Publisher and Subscribers.
> An event is the declaration of the occurrence or change in the application. An event is declared by a C/AL function, which is referred to as an event publisher function. An event publisher function is comprised of a signature only and does not execute any code.
> A publisher is the object that contains event publisher function that declares the event. The publisher exposes an event in the application to subscribers, essentially providing them with a hook-up point in the application. Publishing an event does not actually do anything in the application apart from making the event available for subscription.
> A subscriber listens for and handles a published event. A subscriber is a C/AL function that subscribes to a specific event publisher function and includes the logic for handling the event. When an event is raised, the subscriber function is a called and it code is run.
If you don't understand what above statement says don't worry I will make sure that all doubts get clear when we finish this series about Event, Publisher and Subscribers.