No. IdentityIQ upgrades do not automatically rewrite customer-developed Java or BeanShell code when APIs or methods become deprecated. Deprecation indicates that an API is obsolete, replaced, or scheduled for eventual removal; it does not provide automatic source-code migration.
Before an upgrade, an engineer must inventory custom rules, workflow scripts, plugins, libraries, connector customizations, Java classes, and other code that calls IdentityIQ APIs. Release notes, upgrade documentation, and API changes must then be reviewed to identify deprecated or removed methods. References to affected methods must be manually evaluated and, where necessary, refactored to use the supported replacement API. The resulting customizations must be compiled or executed and regression-tested against the target IdentityIQ release.
This matters particularly for BeanShell because many errors are discovered at runtime rather than during a traditional compilation phase. Assuming automatic conversion could therefore result in broken workflows, aggregation rules, provisioning logic, or plugins after the upgrade.
Therefore, custom method references are the implementation team ' s responsibility and are not automatically updated by the IdentityIQ upgrade.
References/topics: IdentityIQ Engineer — upgrade planning, API compatibility, deprecated methods, BeanShell customization, custom Java code, regression testing.
=======
