Import Playbook/Sub Playbook with Same Name
When you wish to import Playbooks inside Orchestrate, there are chances that the Playbook or Sub Playbook with the same name already exists. Having similar names can lead to confusion. So, instead of renaming the Playbooks, let us discuss how to rectify this situation during the import process.
Before you Start
Ensure you have the necessary permission to perform the import action.
Steps
Import Playbook with the Same Name
For example, assume that you are trying to import a Playbook Incident Response to trigger a set of events, and your account already has a Playbook in the exact name.
Click the Main Menu icon on the left sidebar, and select Playbooks > Manage Playbooks.
Click the Import Playbook icon on the top right.
Browse and select the Playbook to be imported, and click Open.
Under Master Playbook (Playbook that is being imported), you can choose to:
(i) Create New: On import, this creates a new Playbook with a creation date timestamp appended to the name.
(ii) Replace: On import, it simply replaces the existing Playbook, and all the Playbook data will be overwritten with the imported Playbook data.
Click Import.
Import Sub Playbook with the Same Name
For example, assume that you are trying to import a Playbook Incident Response involving a Sub Playbook Incident Action, and your account already has a Sub Playbook in the exact name.
Click the Main Menu icon on the left sidebar, and select Playbooks > Manage Playbooks.
Click the Import Playbook icon on the top right.
Browse and select the Playbook to be imported, and click Open.
Under Sub Playbooks, you can choose to:
(i) Create New: On import, this creates a new Sub Playbook with a creation date timestamp appended to the name.
(ii) Replace: On import, it simply replaces the Sub Playbook.
(iii) Skip: If the Sub Playbook configuration is skipped, no new Sub Playbook will be created. The existing Sub Playbook will be used in the Master Playbook being imported.
Click Import.