Scan bots that use email action with EWS option - You can use the Automation 360 Bot Scanner for EOL Features to scan and identify bots that are using EWS.

Automation 360

You can use the Automation 360 Bot Scanner for EOL Features to scan and identify bots that are using EWS.

Before you begin

  • Ensure that the user credentials used to connect to the Control Room has the View content permission on the Bots folder.

    The Bot Scanner utility connects to your Control Room using these credentials.

  • Ensure that you meet the following system requirements for using the Bot Scanner:
    • Hardware requirements
      Processor 2.66 GHz or higher (64-bit)
      RAM 2 GB or higher
      Disc space 200 MB
    • Software requirements

      Operating systems: Windows 7 or later (32-bit or 64-bit)

About this task

Note: Microsoft has deprecated EWS API for Exchange Online and has recommended that users move to Graph API. See Upcoming API Deprecations in Exchange Web Services for Exchange Online.

We recommend that you replace each email-related action with the equivalent new action in the Microsoft 365 Outlook package (based on Graph API) if your bots are impacted by the deprecation. See Microsoft 365 Outlook package.

Procedure

  1. Download the latest version of Bot Scanner from the Automation Anywhere Support site:
    1. Navigate to the A-People Downloads page (Login required).
    2. Click the Automation 360 v.xx <Build_number> link.
      The xx in the link refers to the release number. For example, Automation 360 v.29.
    3. Click the Installation Setup folder.
    4. Click the AAE Bot Scanner zip file, and then click Download on the toolbar.
    Note: Ensure that you use the .exe file made available with Automation 360 v.29 and later releases.
  2. Extract the files from the zip file you have downloaded and double-click the executable file to run the utility.
  3. In the Bot Scanner page, click the drop-down list and select Bots using Email action with EWS option to select bots that use the EWS protocols.
    Bot Scanner wizard displaying option to select Bots using Email action with EWS option
  4. Click Continue.
  5. In the Automation 360 Bot Scanner EOL features page, perform these steps:
    1. Enter the Control Room URL that you want to connect to
    2. Based on the authentication type configured in your Control Room, choose one of the following authentication methods in the Authentication Type field:
      Authentication type Steps
      Active Directory
      1. Enter the Username (Domain\\username).
      2. Enter the Password (domain user password).
      Database
      1. Enter the Username (Control Room database username).
      2. Enter the Password (Control Room database user password).
      Single Sign-On
      1. Enter the Username.
      2. Enter the API Key.
    3. Click Test connection.
      A connection success or failure message is displayed. Validate your credentials if the connection fails.
    4. In the Select destination path field, enter the location where you want to save the generated report.
    5. Click Scan bots.
    Connect to your Control Room and select destination path to download the report
    The scanner scans all the bots in your Control Room repository. After the scan is complete, a report (.CSV file) is available in the destination path you selected for your review.
    • If a .CSV file already exists in the output folder, a message is displayed that the previous .CSV file will be deleted. When you click Continue, a new .CSV file is generated.
    • If the previous .CSV file is in use, a message is displayed that the file cannot be deleted. Close the file and click Scan bots.
  6. Click Open report to analyze the report.
    The report contains the following details:
    • Task Bot name: Name of the Task Bot.
    • Line number: The line number of the actions that are using the EWS option.
    • Package and action name: The Email package and action that is using EWS.
    • Searched text: The hostname of the Email server or the domain name of the EWS server for the respective action.
    • Action and review message: Use this information to understand the action that you have to perform or the information that you have to review for the corresponding action that is using the EWS option.
    • Task Bot path: The path to the repository where the bot resides.

What to do next

After you identify the bots that are impacted, edit the impacted bot by replacing each action using the EWS option with the equivalent actions in the Microsoft 365 Outlook package. Test the bot and ensure the result is same.