# Notification Center

Mar 2026

Cases entity type and condition templating

Cases as a notification entity type — Notification Center now supports Cases alongside Alerts as an entity type. Create routing rules that trigger on Case lifecycle events, use Ownership Tags for Case routing, and define Case-specific conditions and destinations. **[Learn more](https://coralogix.com/docs/user-guides/notification-center/routing/define-routing-rule/index.md)**

Condition templating for routing rules — Write advanced routing rule conditions using Tera templates. Includes support for alert name matching, label checks, regex patterns, case status and severity conditions, and entity-type routing. **[Learn more](https://coralogix.com/docs/user-guides/notification-center/routing/condition-templating/index.md)**

ServiceNow destination type — ServiceNow is now available as a Notification Center destination, enabling incident creation and management directly from Coralogix notifications. **[Learn more](https://coralogix.com/docs/user-guides/notification-center/destination-types/introduction/index.md)**

JSM (Jira Service Management) configuration via HTTPS — Configure Jira Service Management as a notification destination alongside OpsGenie. Includes JSM connector setup, Atlassian API endpoints, message presets, and a migration guide reflecting OpsGenie deprecation. **[Learn more](https://coralogix.com/docs/user-guides/notification-center/destination-types/https/index.md)**

notification.deliveries dataset update — The `notification.deliveries` dataset is now enabled by default at no cost. Alerts record delivery failures only, while Cases record both successful and failed deliveries.