You can now completely customize the catalogs that are available in Cortex! We know that in many cases, while the defaults of Services, Resources, Domains, and Teams are useful, you have your own taxonomy and important top-level entities that may differ from our defaults.With catalog customization, you can add new catalog pages (and remove ours, if you want) at the top level, letting you create new pages like “APIs,” “Libraries,” “Web Components,” and more using group or CQL based filters, similar to filters in Scorecards.While our Catalogs support custom entity types today, we know that they’re not treated as first class from a UX standpoint. Now, both our built-in and your custom entity types will be available at the top level and you’ll be able to mix and match them in the Catalogs, Scorecards, and more. Existing catalogs will port over seamlessly.
Providing the flexibility to define your own catalogs required many changes to the product. The general theme is that your catalogs are no longer limited to the core entity types of Domain, Resource, Service and Team. Since you now have any number of entities defined in your catalogs, changes throughout the product have been made to generalize references to these original core entity types to Entity.
As you navigate through the application you'll find these changes:
- Creating or importing an Entity (if you have these options enabled in your Admin settings) has been generalized and accessible from all catalog pages and from the All Entities page.
Without Catalog Customization
With Catalog Customization
- More filter options exist and they are consistent across catalogs.
Without Catalog Customization
With Catalog Customization
- The View as hierarchy toggle has been removed from the Domains and Teams catalogs. This change was needed to ensure performant load times of the catalog.
Without Catalog Customization
With Catalog Customization
- For Actions, CQL Reports and Scorecards the entity selector has been updated to match the selector when creating a catalog page. That’s because now you can now select across all entity types.
Without Catalog Customization
With Catalog Customization
Comments
0 comments
Article is closed for comments.