I was corresponding with a Citrix AppDNA user not too long ago and they were telling me how they had three distinct deployment scenarios in their environment. Scenario 1 was Windows Server 2012 R2, XenDesktop/XenApp and App-V. Scenario 2 was simply Windows Server 2012 and XenDesktop/XenApp. Scenario 3 was a desktop deployment to Windows 7 or Windows 8. The user didn’t want to apply any business logic to these scenarios, they just wanted to see the standard AppDNA reports with all of these platform considerations combined.

One approach to configuring AppDNA to target this scenario would be to use Forward Path. Forward Path is an extremely powerful solution, but without the need to apply business logic it would be overkill to use it here. There are some blogs on how to use forward path already if you are curious: Application Management Cost Savings and Automated Workflows or The Non-Developers Survival Guide to Citrix AppDNA Forward Path

The simplest approach for this scenario was to use the Custom Report feature in AppDNA. Custom Reports allows users to create their own AppDNA reports by simply dragging and dropping algorithms from the AppDNA existing standard reports into their own report. The result is a first-class AppDNA report that sits in the AppDNA reporting architecture just like the standard reports but that is targeted at your enterprise specific use cases.

The drag and drop configuration experience for creating your own custom reports is quite simple.

Once your reports have been created they are acted on by the reporting architecture as first class reports along with all of the bells and whistles that come with the AppDNA standard reports.

Custom Reports are also exposed via Forward Path. So if you decide later that you want to start applying automated business logic to your Custom Reports you have the flexibility to do so.

In short, when you want to create new reports that are simply combinations of existing algorithms you should use Custom Reports. When you are looking to apply automated business logic to either standard reports or your own Custom Reports you should use Forward Path.