Jun. 15, 2016
AppDNA provides information about compatibility issues that have been detected in applications. In AppDNA, the term remediation refers to the process of resolving these issues by making changes to applications or the environment so that the applications work on the target platform.
Remediation reports provide detailed remediation information for a specific application. Sometimes more than one alternative approach is provided. The remediation reports also provide details of the application components that are affected by each issue.
There are two remediation report views for desktop applications and three for web applications:
To open a Remediation report:
To view Remediation Actions, click Application Actions and then click an application link in the report.
To swap between views, click the Switch to link at the top of the report.
For desktop applications for which AppDNA provides an automatic fix, you can download the fix in the form of an .mst file that contain modifications that can be applied to the application's .msi file during installation to correct issues. Click the Get MST fixes button to download the fix.
You can optionally merge remediation report views for multiple standard reports (not custom reports). For example, you can merge the results for the Windows 8 and App-V reports. To do this:
If relevant to the report, the currently selected OS Images are shown at the top of the screen. To change the selection, click Change images on the Export toolbar.
Detail – Shows the application's name, manufacturer, version, installation file, package type, standard RAG status, and the date the remediation report view was generated.
Journal – If the application has any external data or manual journal entries, they are shown in this section. If AppDNA has matched the application with an entry in one of the PCA (shim) database external data sources, this section shows the matching executable (.exe) file(s) and, when relevant, the name of the shim(s). You can click Accept to convert an external data entry into a standard journal entry. This means that the application's RAG status will be overridden by the corresponding compatibility (journal) status.
The remaining details are different in the Issue view and the Action view.
For the Issue view, there is a list of the algorithms that the application has triggered. For each algorithm, the report shows the module and report name, along with the algorithm and algorithm group, the standard RAG, and the number of times the application has triggered the algorithm. The algorithm name is a link that takes you straight to the detailed information about the algorithm below.
The detailed information about each algorithm shows the description of the group, the manifestation of the problem identified by the algorithm, an explanation of the remediation, and a list of the application’s components that triggered the algorithm. These details vary depending on the algorithm.
For the Action view, there is a list of the actions that need to be implemented to fix the issues that the algorithms have uncovered. For each action and action detail combination, the report shows the effort involved, the after action RAG, and the number of issues that need to be addressed. The action detail is a link that takes you straight to the detailed information about it below. This shows details about each algorithm to which the action applies, including the description of the algorithm group, the manifestation of the problem identified by the algorithm, an explanation of the remediation, and a list of the application’s components that triggered the algorithm. These details vary depending on the algorithm.
Remediation reports list the remediation actions and action details for each application. Here are example remediation actions that a report can include:
To view the actions for each algorithm available for a report, go to Configure > Modules > Module > Report Name.
Some of the algorithms built into the AppDNA reports have a green RAG status. Generally, a green RAG status means that the application is ready for user acceptance testing (UAT) on the target platform. However, these algorithms can be broken down into several groups: