Novell Doc: Novell ZENworks 7 Desktop Management Administration Guide

37.4 Adding an Application Dependency

Before adding a dependency to an application, consider the following:

The dependent application must already exist as an Application object. If it does not, see Section 28.2, Configuring the Application in eDirectory.
By default, each user who is associated with the primary application is added as a trustee of the dependent application. This provides the user with the eDirectory™ rights required to the dependent application. You should not associate users directly with the dependent application (dependent Application object > Associations tab) unless you want the dependent application to be displayed by Application Launcher.

To add a dependency to an application:

In ConsoleOne®, right-click the Application object, then click Properties to display the Application object's property page.
Click the Run Options tab > Application Dependencies to display the Application Dependencies page.
Add the dependent applications to the list. To do so:
1. Click Add, browse for and select the Application object, then click OK.
2. If necessary, modify the following distribution attributes for the dependent application:
  
  Continue distributions immediately: By default, Application Launcher waits until it distributes and executes the application before continuing with the action. Select this option if you want Application Launcher to continue with the next action regardless of whether or not the current application's distribution and execution is complete.
  
  For example, if Regedit has a dependency on Notepad, the default action is for Application Launcher to distribute Notepad (if necessary), launch Notepad, and wait for the user to exit Notepad before it launches Regedit. The Continue distributions immediately option, however, would cause Application Launcher to distribute and launch Notepad and then, if the distribution and launch of Notepad was successful, continue immediately with Regedit. In other words, it does not wait for execution of the application to be completed.
  
  Reboot wait: If distribution of the application requires the workstation to be rebooted, select this option to postpone the reboot until 1) Application Launcher distributes another application in the list that requires a reboot (and doesn’t have this option selected) or 2) Application Launcher completes distribution of all applications in the list. This option also applies when uninstalling the application.
3. Repeat Step 3.a and Step 3.b to add another application.
Arrange the dependent applications in the order in which you want them distributed and launched.

The order in which the dependent applications are listed is the order in which Application Launcher distributes and launches them, going from top to bottom. However, if an application has dependencies, the dependent applications must be distributed and launched before the primary application can be distributed and launched. You can use the up and down arrows to change the order.
Click OK to save your changes.