Questionnaire Introduction

Questionnaires in AppTracker are dynamic forms that you get to design an build according to your needs. This is part one of a three part series exploring Questionnaires. I'll talk about where they are used, how to building a questionnaire and reporting on them. In this introduction video I show how a tradition QA form in Word can be converted to a Questionnaire form in AppTracker. Future posts will cover modelling more complex forms and reporting.

Managing Your Change History

AppTracker goes a long way to record all changes to an Application or Migration over its life. These can be changes to its basic properties such as name, vendor, version or it can be adding UAT's note, discovery information etc. All these changes are recorded with the before and after values as well as by who and when. This level of history drives a lot of AppTracker's internal reporting and is exposed to you so that you can generate your own custom reports. At the end of this video I create a simple ad-hoc report that shows all the changes to the applications in the Finance department over the previous two weeks, what type of changes were made and who made them.

Application Dependencies

An important part of the packaging and deployment process is tracking application dependencies. We need to not only know if a specific application is ready but also if all of its dependencies are ready too. We need to know what impact changing an application version might have and what needs to be retested. We need to find problems in our chain such as a application being a dependency of itself or having a dependency that is cancelled. All of this information can be mined from AppTracker using the dependencies tab and grid filters.

When looking at a specific application we need to be able to see:

  • What dependencies does this application have
  • What other applications have this application as a dependency 
  • The full chain of all sub-dependencies, not simply the first level 
  • Where in the chain does this application sit

Application Dependencies

When looking at our portfolio as a whole we need to see:

  • Which applications have dependencies
  • Which applications are used as dependencies

Application Dependencies