Skip to Content

Work flow and Event propagation in addon


Hi, my name is Kumar, and in this video I will explain Work Flow and Event Propagation in Add-on. So, let us start with work flow in Add-on.

Before we start, I would like to give an overview of it. Let us say, after reading the customer requirement document, the development team does feasibility analysis to make sure if the customer's objectives can be achieved by creating an Add-on. If the analysis recommends creating an Add-on, then you proceed further with preparing the Add-on package.

While preparing the package, all feasible requirements are incorporated in the Add-on program and events are declared in it.

Once the Add-on package is ready, it is registered in iVend Management Console. The Management Console application requires a restart to apply all changes, and after that, Add-on gets replicated to all store servers.

Now, there are certain steps to create an Add-on and deploy it.

First step is to start the process, then go to Customer Requirement Document. Check if creating an Add-on can achieve the customer requirements. If yes, design an Add-on using the iVend Add-on template then prepare the Add-on package, register the Add-on in iVend Management console, restart the application, and install the Add-on. This replicates the same Add-on to all Stores. Add-on starts working on all Management Console and Point of Sale.

So, this was the workflow for creating iVend Add-on. Now, let us move to Event Propagation of iVend Add-on where we will learn how an event is handled and executed.

Before we proceed, you should understand that Management Console raises various events according to the set parameters. On the other side, iVend Add-on which is deployed on the stores handles the event as it is called while doing any relevant pro or post transactions.

iVend Add-on then executes all events programmed in it and then redirect to the Management Console where it raises the other events as required. For example, during the transaction if the exception is not handled at the Add-on level then the main application handles the exception and shows the correct message to the retailers.

Now, this is the work flow for Event Propagation of iVend Add-on. Event raised by Management Console or Point of Sale, validate if the events are handled by an Add-on. If yes, then perform the action specified in handler, validate if the performed action executed successfully. If no, then end the process. If yes, check if there is another Add-on registered. If no, then end the process. If yes, then pass the event to the next Add-on and follow the process as mentioned here.

With this, we end our session on Work Flow and Event Propagation of iVend Add-on.

Thank you for watching this video.

Quick Links