Three ways to list the artifacts of a process app, from the quickest to the most complete:
- Process Designer library - the library view lists everything by category; the web designer's library search with an empty term and the All filter shows all items; select-all + tag (question 1410) gives a smart folder.
- REST API (per snapshot):
GET /rest/bpm/wle/v1/processApps -> apps with their snapshots (IDs)
GET /rest/bpm/wle/v1/assets?snapshotId=2064.xxxx -> managed assets (web / server / design files)
GET /rest/bpm/wle/v1/snapshot/2064.xxxx?parts=all -> exposed items, dependencies, validation
GET /rest/bpm/wle/v1/exposed?snapshotId=2064.xxxx -> exposed processes, services, dashboards
# BAW 20+ Operations REST: library items of a container version
GET /ops/std/bpm/containers/{acronym}/versions/{snapshot} -> container version details (see /ops/docs for the optional parts of your level)- The twx export - the complete inventory: META-INF/package.xml lists every object with id, type and name; one XML file per artifact under objects/. A few lines of scripting turn it into a spreadsheet:
unzip -p MyApp-1.4.twx META-INF/package.xml | grep -o '<object [^>]*>' | sed 's/.*type="\([^"]*\)".*name="\([^"]*\)".*/\1;\2/' | sort | uniq -c | sort -rn # count per type
# object types: 25 = BPD, 1 = service / human service, 64 = coach view, 12 = business object, 7 = team, 61 = managed asset, 4 = tracking group, 24 = UCA, 50 = EPV, 21 = decision
For "which artifacts are used vs orphaned" the twx is also the source: references between objects are the ids inside the XML files - a script that builds the reference graph from the tip finds unreferenced coach views and services (the same technique the TWX code analyzers use). On BAW 20+ the designer also offers Where used per artifact.
References