---
title: Incompatible changes
description: When you update to IDM 7.2.2, the following changes may impact existing deployments. Adjust existing scripts, files, and clients, as necessary.
component: pingidm
version: 7.2
page_id: pingidm:release-notes:changed-functionality
canonical_url: https://docs.pingidentity.com/pingidm/8.1/release-notes/changed-functionality.html
llms_txt: https://docs.pingidentity.com/pingidm/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
superseded_by: https://docs.pingidentity.com/pingidm/8.1/release-notes/changed-functionality.html
section_ids:
  onDelete-default-bahavior: Default onDelete behavior
  felix-osgi-upgrade: Felix and OSGi upgrades
  jms-20-upgrade: JMS 2.0 upgrade
  json-patch-exceptions: PATCH request exceptions
  policy-enforcement-on-role-name: Policy enforcement on role name
  preferredLocales-precedence: Precedence in locales in the self-registration email template
  paused-queued-sync-changed: Paused queued synchronization for unavailable routes
  workflow-embedded-db: Embedded workflow database
  default_mysql_connection_driver: Default MySQL connection driver
---

# Incompatible changes

When you update to IDM 7.2.2, the following changes may impact existing deployments. Adjust existing scripts, files, and clients, as necessary.

## Default `onDelete` behavior

The default `onDelete` behavior previously called a file-based script, `onDelete-roles.js`. This has been removed from the managed object configuration *(tooltip: You can edit the managed object configuration over REST at the config/managed endpoint, or directly in the conf/managed.json file.)*.

## Felix and OSGi upgrades

IDM has upgraded to OSGi Core 8.0 and Felix Framework 7.0.0.

## JMS 2.0 upgrade

The samples that use the Java Message Service (JMS) have been upgraded to use the 2.0 API and Apache ActiveMQ Artemis:

* [Subscribe to JMS messages](../samples-guide/scripted-jms-subscriber.html)

* [Direct audit information to a JMS broker](../samples-guide/audit-jms.html)

## PATCH request exceptions

Previously, illegal PATCH requests could return a `400` *or* `500` exception. In such cases, IDM now returns a `400` status.

## Policy enforcement on role name

The `name` property of a [managed role](../objects-guide/managed-roles.html) is now subject to the uniqueness policy by default. This means that you cannot create multiple roles with the same `name`. To change this behavior, adjust the policy validation on the `role` property in your managed object configuration *(tooltip: You can edit the managed object configuration over REST at the config/managed endpoint, or directly in the conf/managed.json file.)*.

## Precedence in locales in the self-registration email template

Previously, the `defaultLocale` specified in the [Self-Registration Email Template](../self-service-reference/email-notification.html#email-user-self-registration) configuration took precedence. As of IDM 7.2, locales specified as `preferredLocales` in the `Accept-Language` header take precedence over the `defaultLocale`.

## Paused queued synchronization for unavailable routes

Synchronization queue processing for a mapping is now *paused* if either the source or target system route are *unregistered*. For more information, see [Configure queued synchronization](../synchronization-guide/chap-implicit-live-sync.html#configure-queued-sync).

## Embedded workflow database

Previously, you could use the Flowable workflow engine's embedded H2 database for demo and testing purposes. IDM no longer includes this database. Before you use workflow, you must [install a JDBC repository](../install-guide/chap-repository.html).

For more information, see [Enable workflows](../workflow-guide/enable-workflows.html).

## Default MySQL connection driver

The default [JDBC Connection Configuration](../objects-guide/repo-config.html#datasource-jdbc-json) now uses the connection driver from MySQL 8.1 (`com.mysql.cj.jdbc.Driver`).