Pending Catalogs
Pending Catalogs is the review queue. The screen is titled Pending Titles and lists every catalog entry that has been proposed but not yet accepted into the working catalog. Nothing on this screen is used for matching until it is approved.
Pending Catalogs is available to administrators. Users with the viewer role can read the Software Catalogs screen but do not see this one.
Local and global queues
The screen has the same two tabs as Software Catalogs, and they are reviewed by different people:
| Tab | Holds | Reviewed by |
|---|---|---|
| Local | Entries proposed for your organization's own catalog: everything you add, import, or edit yourself. | Your administrators |
| Global | Entries proposed for the catalog that all organizations share. OpenLM owns this queue. | OpenLM |
Not everything is reviewed here. Entries that Software Discovery enriches successfully are written to the global catalog and approved automatically, so they never pass through this screen.
Both tabs show the same columns as the working catalog — Software Name, Publisher, Feature, Deployment Type, Part of a Package, and Category — with the same Refresh, Toggle Filters, and Search controls in the grid toolbar.
Approve or deny an entry
Hover over a row to reveal its two actions:
- Approve Catalog — accepts the entry. It moves to Software Catalogs and starts being used to match observed products.
- Deny Catalog — rejects the entry. It leaves the queue without joining the working catalog.
Either action opens a confirmation dialog first — Approve Catalog or Deny Catalog, asking you to confirm the decision — so a mis-aimed click cannot change the catalog. The grid reloads once the decision goes through.
A denied entry is not deleted. It is kept in a rejected state, which stops the same proposal from being raised again from scratch, and the decision is written to the entry's audit trail along with who made it. You can review that history from the Audit Trail action on the Software Catalogs screen.
What to look for when reviewing
- Is the Feature correct? The feature code is what OpenLM matches on. An entry with the wrong code never matches, or matches the wrong product.
- Is the publisher spelled the way you already record it? The point of the catalog is one spelling per product.
- Is the category useful? Entries arrive with Unknown when the pipeline infers nothing. Approving them as-is is fine, but a category makes reporting more useful later — edit the entry after approving it.
- Is it a duplicate? Search the working catalog for the same feature code before approving.
Related
- Software Catalogs — the working catalog, and where approved entries land.
- Software Discovery — the AI pipeline behind the global catalog.
- SAM Catalog overview — the full approval lifecycle.