Check in a bot

Check in the bot files or folders to the public workspace from private workspace to make it available for all users who have the permission to access and run the bot.

Prerequisites

  • You must have Bot Creator or Citizen Developer license to check in a bot to the public workspace.
  • You must be assigned a custom role with the following permissions:
    • Required: Check in permission at the folder level and at the corresponding parent folder level in the public workspace.
    • Optional: Create folder permission.
    • Optional: View packages permission.
  • To check in a bot with dependent folders and files, ensure you have the following:
    • Create folder permission.

      If you are checking in a bot from your private workspace and if the folder in which the bot is present does not yet exist in the public workspace, you must have create folder permission to successfully check in the bot.

    • Check in permission on the dependency folder.
  • Ensure that your private and public workspaces have the same folder structure so that when you check in a bot from your private workspace, it will appear in the same folder structure in the public workspace.
  • For example, if you check in a bot from the sample bot folder in the private workspace, it will appear in the sample bot folder in the public workspace.

If you want to check in multiple bots as a unit that are not dependent on each other, create a main bot and then add the other bots as dependencies to this main bot. Check in the main bot.

Procedure

  1. Log in to the Control Room as a Bot Creator or a Citizen Developer user.
  2. On the left pane, click Automation in the private workspace.
    A list of available bots and forms is displayed.
  3. You can choose to check in either one bot or multiple bots simultaneously.
    • Check in a single bot.
      1. Select the bot that you want to check in, click the actions menu (vertical ellipsis), and click Check in Task Bot.
      2. In the Check in Task Bot window, add your comment and click Check in.
        Note: Directly referenced dependencies are checked in by default. The General tab shows only the immediate dependencies; however, all the nested dependencies are displayed in the Review dependencies tab, and these are also checked in.

        For example, consider a scenario where we have parent bot Acme Insurance having departments as child bots HR, Sales and Marketing, and IT services. These child bots have dependencies Employee details, Employment type, and Employee status.

        When you check in the parent bot Acme Insurance, in the general dependency tab, only the direct dependencies HR, Sales and Marketing, and IT services are displayed and selected to be checked in by default.

        bot check in dependency general tab

        The review dependencies tab displays all these child bots along with the other available nested dependencies such as Employee details, Employment type, and Employee status that are also checked in along with the parent bot.

        bot check in review dependencies tab

    • Check in multiple bots.
      Note: You can check in up to 10 bots at a time.
      1. Select the bots that you want to check in and click Check in checked items.
        Note: All the inherited dependencies are included to be checked in.

        Bulk check in of bots
      2. Add the comment and click Check in.
      3. Optional: Select Advanced options to view or modify the selected dependencies, add the comment, and click Check in.

    The bot appears in the same folder structure in the public workspace.

    Note:
    • You cannot check in a bot file if another bot file already exists in the same location in the public workspace.
    • When you check in a bot along with a cloned bot and no other bots are dependent on the clone, the cloned bot is deleted.

If you have issues in checking in a bot, see Unable to check-in the bots in Automation 360 (A-People login required).