Run Forward Path tasks

Aug 14, 2017

Forward Path tasks are typically used to automate the creation of production-ready App-V and XenApp packages, based on logic within the Forward Path report. However, Forward Path tasks can be configured to do many other tasks, such as copying files and sending emails. Forward Path tasks are controlled by Forward Path task scripts that are configured to run based on a value in the Outcome column in a Forward Path report. Forward Path reports are controlled by scenarios.

After you create or import Forward Path scenarios and task scripts, you can run tasks and monitor their status.

To run a Forward Path task

  1. From the side bar, choose Select > All Applications.

  2. In the Application List, select the applications for which you want to run Forward Path.

  3. From the side bar, choose Reports: Applications > Forward Path.

  4. In the Forward Path report viewer, select the Forward Path scenario you want to use.

    You can change the default active scenario in the Forward Path Logic Editor.

  5. Click Evaluate Tasks.

  6. In the Forward Path Task Sequencing screen, click Refresh on the toolbar to ensure you have the latest results.

    • The Outcome column shows the latest results and shows for each application whether there is a task script associated with the value in this column.
    • The MapUNCPathDriveLetter column shows the mapped drive letter if the task script has used the ApplicationDetails.MapUNCPath property to map the \\server\share portion of installation directory to a drive letter.
    • The Install Command column shows the command that launches the application installation. If not overwritten by the task script, this shows the Active Directory or Configuration Manager installation command if the application is linked with an Active Directory or Configuration Manager managed application. Otherwise this column shows a command based on the location and method by which the application was imported into AppDNA.
    • The InstallWrkDir column shows the working directory used by the installation command. When this is blank, the default working directory is used.
  7. Select the applications for which you want to run the tasks.

  8. Click Start on the toolbar.

    The lower part of the screen shows the progress and the error log. Some task scripts are dependent on the successful configuration of Install Capture and a virtual machine. See Install Capture for more information.