Your catalog already knows that a product area owns certain services, that a region maps to specific clusters, that a customer tier corresponds to a set of accounts. That context lives in Rootly Catalogs—but until now, none of it carried over into incident forms automatically. Responders had to bridge that gap themselves, pulling from memory or looking things up mid-incident.
Catalog fields now support automatic cascading based on the relationships already defined in your Rootly Catalogs. When a responder updates one field, any related fields that can be inferred from your catalog structure are populated automatically—no lookups, no cross-referencing, no manual entry.
What this looks like in practice:
- Update Product Area → affected Services populate automatically based on your catalog relationships
- Set the Region → related Clusters fill in based on how your infrastructure is mapped
- Add a Customer Tier → the list of Customers that need communication updates automatically
The data your team enters during an incident gets more accurate, and your responders spend less time filling out forms and more time resolving the problem.
Check out the docs to get started and learn more.
