Pending Catalogs
To approve or reject proposed catalog entries, open Pending Catalogs, the review queue. The screen is titled Pending Titles and lists every proposed catalog entry that no one has approved yet. Nothing on this screen is used for matching until it is approved.
Before you begin
Confirm these prerequisites:
- You are an administrator. Users with the viewer role can read the Software Catalogs screen but do not see Pending Catalogs.
The following image shows the Pending Titles screen on the Global tab.
Pending Titles screen on the Global tab, listing entries awaiting review.
Local and global queues
The screen has the same two tabs as Software Catalogs. Select Local to review your organization's entries, or Global to see the shared queue. Different people review them:
| 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. The global catalog automatically approves entries that Software Discovery enriches successfully, 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, Version, and Category. They also have the same Refresh, Toggle Filters, and Search controls in the grid toolbar.
Approve or reject entries
Approving an entry moves it to Software Catalogs, where OpenLM Platform starts using it to match observed products. Rejecting an entry takes it out of the queue without adding it to the working catalog. Decide on one entry at a time from its row, or on several at once from the grid toolbar.
To act on one entry, hover over its row and select one of these actions:
- Approve Catalog: Opens a confirmation dialog of the same name.
- Deny Catalog: Opens the Reject Catalog dialog. (Optional) Enter a reason in Reason (optional) to record it with the decision. Then select Reject, or Cancel to leave the entry pending.
To act on several entries, use the toolbar buttons. The number in parentheses on each button is how many entries it acts on:
- Approve Selected and Reject Selected: Act on the rows you select. You can't select these buttons until you select a row.
- Approve All and Reject All: Act on every entry that matches the current filter, including entries on other pages of the grid. You can't select them when the count is 0.
Each of these buttons opens an Approve Catalogs or Reject Catalogs dialog. Check how many entries the decision covers, then confirm. The reject dialog also has the optional reason box.
Nothing changes until you confirm in the dialog, so selecting an action by mistake cannot change the catalog. The grid reloads after you confirm. After a decision on a single row, the entry can stay listed until you select Refresh.
OpenLM Platform doesn't delete a denied entry. It keeps the entry in a rejected state, which stops the same proposal from being raised again from scratch, and writes the decision 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.
Check entries before you approve them
Check each entry against this list:
- Feature: Check that the feature code is correct. OpenLM Platform matches on the feature code, so an entry with the wrong code never matches, or matches the wrong product.
- Publisher: Check that the publisher is spelled the way you already record it. The point of the catalog is one spelling per product.
- Category: Check that the category is useful. Entries arrive with Unknown when the pipeline infers nothing. Approving them as is works, but a category makes reporting more useful later, so edit the entry after approving it.
- Duplicates: Search the working catalog for the same feature code before approving.
Related
For more information, see the following pages:
- Software Catalogs: The working catalog, and where approved entries land.
- Software Discovery: The AI pipeline behind the global catalog.
- SAM Catalog: The full approval lifecycle.
The documentation team might draft this page using a large language model. A technical writer reviews every page and verifies it against the product before publishing it. A human makes the final decision.