Check in API Tasks to Repository

To make an API Task available, check in the API Task from the private workspace to the public workspace. Perform this operation after adding the API Task to a form and process.

Prerequisites

Ensure the following prerequisites are met for you to check-in an API Task.
Note: A bot developer can test a process without checking in the API Tasks.
  • Bot Creator license to check in an API Task to the public workspace.
  • 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 an API Task with dependent folders and files, ensure you have the following:
    • Create folder permission.

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

    • 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 an API Task from your private workspace, it will appear in the same folder structure as in the public workspace.

Procedure

  1. Log in to the Control Room as a Bot Creator user.
  2. On the left pane, click Automation.
    A list of available bots and forms is displayed.
  3. Choose to check in either one API Task, or multiple API Tasks simultaneously.
    • Select the API Task that you want to check in, click the actions menu (vertical ellipsis), and click Check in API Task.
    • Select the API Task that you want to check in and click Check in checked items.
      Note: You can check in up to 10 items at a time.
  4. In the Check in window, add your comment and click Advanced options. Select the dependencies you want to check in and click Check in.
    The API Task appears in the same folder structure as in the public workspace and directly referenced dependencies are automatically checked in.