AppTracker - How it Works


If we haven't previously added our application to our deployment tool then now is the time. AppTracker can assist here in one of two ways:

  1. By allowing us to trigger PowerShell scripts to run on a specific event, such as when an application is changed to the "Deployment" phase. This script would typically create all the items in the deployment tool (and possibly Active Directory too) so that the application is ready for deployment to live machines. 
  2. If the Deployment Team prefer to create the deployment objects manually then they can use AppTracker as an information source. What is the package name? What is the command line needed for install? What are the prerequisites and dependencies? AppTracker can answer all these questions without the need for emails and phone calls to the packager (who happens to be on leave today).

At this point you may be interested in taking a look at your applications journey from request through to "Live" in AppTracker to see how long it has spent in each process. We can do this using the built-in reports to create a pivot chart. Here we can see the amount of time (in minutes) that the application spent in each process. It's clear that packaging took the most amount of time for this application.

A pivot chart showing how long the application spent in each process

Time Saved

Why is this process more efficient with a workflow tool such as AppTracker?

  • Trigger creation of deployment objects (eg. SCCM Application etc) via PowerShell scripts
  • Centralised application knowledgebase provides deployment team access to all necessary information to create deployment objects

In our experience you can save approximately 25% of the time getting the application into Live by using AppTracker. 

Next process: Retire

To see what savings are possible for your organisation please refer to our ROI Calculator.