The Business Process Explorer provides you information with respect
to your project. It also provides a hierarchical representation of all project-related
objects.
Figure 1. Object hierarchy flowchart

The explorer
shows a tree form of the hierarchy illustrated in the flowchart shown above.
Each of the objects will have a number besides it which denotes the number
of instances of that object.
Deleting objects in the Business Process
Explorer
All the objects shown in the explorer are top level; however,
deleting some of them might have a cascading effect. Listed here are some
of the rules for these effects:
- Deleting any one of the Business Process Model hierarchy objects will
cause a cascading effect and delete its subobjects as well.
- If you delete a nonleaf node That is, an object that has subobjects under
it in the hierarchy shown in the Business Service Explorer, it
will delete everything under it after a reconfirmation. The reconfirmation
message reads, Deleting this <type> will also delete all child objects
Following objects on deletion will:
Flow Objects are leaf nodes That is, an object that does not have
any subobjects under it in the hierarchy shown in the Catalog Explorer and
therefore can be deleted safely.
Applications and Understanding application suites follow a different rule:
- If you try to delete an Application Suite that has any Applications contained
in it, you will get a popup saying You cannot delete <application suite
name> because it still has Applications associated with it. Please delete
the applications and try again.
- If you try to delete an Application that has any Business Services contained
in it, you will get a popup saying You cannot delete <Application Name>
because it still has Business Services associated with it. Please delete the
Business Services and try again.