Deleting Resources

Resources that have been “created” can also be deleted.

For information about what constitutes a “created” resource, see Creating Resources.

After deleting a resource, that resource can no longer log into the BPM application.

Note that deleting a resource using the Organization Browser does not remove the resource from the LDAP source, nor from the container; it merely deletes any mapping that may have been done for that resource, preventing that user from being able to log into the BPM application.

More than one resource can be deleted at one time.

Procedure

  1. From the Organization Browser, select the LDAP container containing the resource(s) you would like to delete, then select the desired resource(s) from the list of resources.
  2. Click the icon (or select Delete Resource(s) from the Tools menu) in the upper right pane.

    The icon to the left of the resource name changes to a grayed-out icon, indicating that the resource is no longer created nor mapped. The sections in the lower-right pane are also removed, as deleting the resource removes all mapping.

Result

The resource is removed from the database and the resource can no longer log in.

Note: If you delete an LDAP container that contains resources that have been created and/or mapped to a group or position, the resources can optionally be deleted at the same time. For information, see Deleting LDAP Containers .
Note: If an LDAP entry that was used to create a resource in the Organization Browser is deleted from the LDAP source, a reference to the resource continues to exist in the BPM application. It can no longer be used to log in and cannot be edited in the Organizational Browser. The invalid resource can, however, be deleted.

A resource might also appear to be invalid in this same way if key pieces of information used to help uniquely identify the LDAP entry have been changed inside of the LDAP source. If that LDAP data is changed back to the original values, the connection between the resource and the LDAP entry may be re-established. Otherwise, the resource would need to be deleted and re-created to reference the altered LDAP entry. This would constitute a new resource; relationships to the original resource’s BPM data, such as allocated work items and event logs, would not be maintained.