Publish components

publish components to publish a component to the docid\ ybfrgy2bhve9nsrskctb3 library before you publish confirm the component name and description are accurate verify inputs/outputs are configured as intended test the component in a playbook to validate behavior publish as new content (v1) steps you can publish a component by selecting publish from the ellipsis icon of components screen or navigate to the desired playbook open the component settings menu and select publish in the publish content window select publish as new content (v1) provide a name and description for the content click next select content to publish all the playbook components are listed click next review content review the selected content and check for potential issues if everything looks good, click next summary confirm the details version (1 0 0), content name, description, and publish message click publish success a success message confirms that the component has been published as new content the new content is now available in the content library publish as a new version of existing content (v1+) this scenario applies when you need to update an already published component package steps follow steps 1–3 as in the publish as new content process in the publish content window select publish as a new version of existing content (v1+) from the list, choose the package you want to update click next review changes review the selected content and check for issues click next summary confirm the new version (for example, 3 0 0 > 4 0 0) provide a detailed publish message (what was changed and why) click publish merge conflicts (if applicable) if conflicts are detected between the local changes and the remote repository, a merge conflicts screen appears you have two options keep library changes (retains local changes) keep remote changes (keeps remote repository changes) click apply to resolve conflicts success the updated content is now published, and a confirmation message appears you can navigate to the user content library to verify the playbook published limitations and restrictions component nesting is limited to 10 you can configure assets and settings, but you cannot remove actions within a nested component task deletion if you want to delete tasks within a component, duplicate the component as a user made one and modify it as needed ungrouping components ungrouping only affects the current flow; it does not delete the component from the library cross workflow limitation you cannot create a component that spans across multiple workflows branching limitation parallel actions and conditions must be within the same branch