Check out a bot
Check out bot files or folders to private workspace from public workspace to create an editable copy of the bot.Check out specific versions of parent and child bots from a public repository to a private workspace to create an editable copy of the bot.
Prerequisites
- You must have Bot Creator or Citizen Developer license to check out a bot to your private workspace.
- You must have check out permission at the folder level.
- You must have the check out permission on the dependency folders to check out a bot with dependent folders and files.
- You must have the Cancel
checkout and View content permissions on
a public workspace to cancel or undo a check out performed by a Bot Creator user,
You do not require the Cancel checkout permission to cancel the checked out bot from a private workspace.
While checking out bot, keep the following considerations in mind:
- If you want to check out 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 out the main bot.
- Only one user can check out a file at a time. When a user checks out a file, it cannot be checked out by any other user.
- If you are checking out a parent bot in the public workspace whose dependencies are checked out by another user, the dependencies of the parent bot will be cloned in your private workspace.
- If a bot is checked out, it cannot be deleted. The bot should be in a checked-in state to be deleted.
- When you edit a checked-out bot, the status changes to Checked out
edited.
You can use the Revert edits option to revert changes you made to the checked-out bot.
- During check out, a cloned bot can be overwritten or replaced.
- The dependent files are automatically cloned if they are checked out by another user and you have the Clone permission on the bot folder.