Date: Fri, 29 Mar 2024 03:18:08 -0500 (CDT) Message-ID: <323970048.29796.1711700288876@bmc1-rhel-confprod1.managed.contegix.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_29795_79716636.1711700288876" ------=_Part_29795_79716636.1711700288876 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
You can delete a folder, group, smart group, or system object.= p>
You have the option of making it impossible to delete a folder or group = unless that folder or group is empty. To perform this procedure, use the Ap= plication Server Administration console (that is, the blasadmin utility), a= s described in Deleting groups in the BMC Server Automation Cons= ole. This procedure has no effect on smart groups, which you can always= delete.
Note
You cannot delete or remove objects from smart groups.
If other objects depend on the object you plan to delete, you can delete= the other objects and the object you choose to delete. Alternatively, if y= ou are deleting an object and a component template, Deploy Job, or Batch Jo= b depends on that object, you can choose to delete only the original object= and break all dependencies those component templates, Deploy Jobs, or Batc= h Jobs might have on the deleted object. If you choose to break dependencie= s, the component templates, Deploy Jobs, or Batch Jobs with broken dependen= cies appear in the content editor with a red X in one corner.
Note
To break a dependency with a component template, you must have, at minim= um, the ComponentTemplate.Break authorization. To break a dependency with a= Deploy Job, you must have, at minimum a DeployJob.Break authorization. To = break a dependency with a Batch Job, you must have, at minimum, a BatchJob.= Break authorization.
You can use a smart group to locate system objects with broken dependenc= ies. For details, see Finding system objects with broken dependencies= .