Analyze report for Internet Explorer bots

You can analyze the report generated by the Bot Scanner to get usage statistics about Internet Explorer used in your bots.

Based on the report that Bot Scanner generates, you can plan and implement a strategy to convert bots that use Internet Explorer to Microsoft Edge with IE mode.

Bot Scanner provides the following information about these bots:

Number of bots analyzed
Number of bots scanned for Internet Explorer usage and those that were not scanned
Internet Explorer usage statistics on the percentage and number of bots using Internet Explorer
Reasons for bots that were not scanned
Reviews required by users after conversion

Folder location and reports

A raw-data folder is created that contains the reports (in XML format) for each bot scanned. It helps our developers to further analyze the scanning process and take corrective actions, if required. No personally identifiable information (PII) is included in the summary report or the individual reports of the scanned bots.

The system creates three folders within the raw-data folder that contain various reports:

Migratable_Bots: Contains reports of bots that are possibly using Internet Explorer.
Failed_to_Analyze: Contains reports of bots that Bot Scanner failed to analyze.
MetaBots: Contains reports of MetaBots that can and cannot be migrated to Automation 360 and the ones that the Bot Scanner failed to analyze.

Summary report for all bots

The summary report provides information about the total number of bots scanned, the number of bots scanned for Internet Explorer usage, the number bots that could not be scanned. It also provides Internet Explorer usage statistics about the percentage and number of bots using Internet Explorer.

For example, consider the Bot Scanner has scanned 31 bots. Of the 31 bots, consider 26 bots are scanned for Internet Explorer usage, and 0 bots could not be scanned. The percentage of bots using Internet Explorer is 84%.

Reviewing the Bot Scanner report

Consider a scenario where you have scanned a total of 72 bots, of which 22 bots are scanned for Internet Explorer usage and 3 bots could not be scanned. In such a scenario, the report enables you to perform the following actions:

Identity bots (8) that require review after conversion and take action if required.
Identify bots (14) that do not require any review after conversion.
Identify the reason why the bots (3) cannot be currently scanned for Internet Explorer usage. The reason might be that the bot is built using a version earlier to Enterprise 10 such as Enterprise 8.

The following image is a sample report from the Bot Scanner:

Internet Explorer Bot Scanner report example

The following table describes the various fields in the sample Bot Scanner report (as numbered in the previous image):


Field/option	Description
	Bots scanned for IE usage > Review required > Bots: Go to this view for a list of bots (8 in this scenario) that should be reviewed after conversion. To view the review required message for a specific bot, click the bot name. The message provides information about changes if any are required in the bot after conversion.
	Bots scanned for IE usage > No review required > Bots: Go to this view for a list of bots (14 in this scenario) that do not require any review after conversion. Click any bot name in this list to view the XML report offline.
	Bots that can't be scanned now > Bots: Go to this view for a list of bots (3 in this scenario) that cannot be currently scanned. To view the error message for a specific bot, click the bot name. An XML report opens in a new tab where you can view the error due to which the bot cannot be scanned.
	Download (as a CSV file) the list of bots or commands that can or cannot be scanned so that you can review the file offline or share the file with others.

Report validity

The report is valid until the next version of Bot Scanner is available. When the next version is available, a report expiry message is displayed. You must download the latest version of Bot Scanner and use that version to scan the bots again.

Automation 360