With the unique and powerful Action designer you can precisely define the flow of your installation.

If you install for instance your application together with third party software (like the BDE or Oracle Client) it would be nice if all dialogs were

Action Designer in Action grouped together, so your end-user has to answer questions only once. With the Action Designer you can synchronize the sequence of installation when more packages are installed, and group the Dialogs together.

This is realized by showing linked packages together with the main package in one page of LizaJet Installer Studio.

Dialogs and Action  handler
You can create actions with and without an own Dialog.
For each action you can define up to 6 action handlers, a special kind of event handlers that fires when a certain condition is met. For normal simple installation you do not need them, but it is nice if you know you can interfere at each point during the installation and write an action handler.
WIth the action handlers you can check if an Action must be executed at all. You can define an Action handler before execution of the Dialog, before and after showing of the Dialog and what must be done if the user presses the Previous of Exit button.

to the components of a Dialog. Those event handlers you will use for Dialog related scripts, like input checking, combo box and TreeView handling.

Installing and upgrading

LizaJet Installer has an integrated framework for installation and upgrading, and it recognizes that between first Installation and upgrade there are similarities but also differences. Similarities are for instance that you want to show a Progress and Final Dialog.  

You can set which actions are executed during installations and during upgrade

Differences are for instance that for first Installation you a File Destinations Dialog, but for an upgrade you want to skip this Dialog.

With LizaJet Installer you can define for each Action must be executed only at first Installation or only at upgrade.

The built-in dialogs and components directly call the  Installation Library. So normally you do not need to add event handlers.
But if necessary you can do it. You can define an event handler that checks if the Action must be executed at all, validate user input, and define what script must be executed when the Action is executed.