Associated Form Is Unaccesible When An Application Instance Is Migrated Via Deployment Manager
(Doc ID 1515225.1)
Last updated on FEBRUARY 11, 2019
Applies to:Identity Manager - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 11g]
Identity Manager - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Scenario: Exported an Application Instance named "CONTRACT" from a reference environment via the Deployment Manager, by selecting the appropriate entry from the "Application Instance" export type. All dependencies were selected during the export except four items: 3 system groups and the default rule. The sandbox used to edit the default Application Instance form and modify the ContractCreate and ContractModify pages has also been exported.
After importing the xml into a new environment via Deployment Manager, the sandbox is also imported and published. When accessing the Application Instances page via the sysadmin url of the new environment, one can see that the "CONTRACT" form is no longer selected as the associated form of the Application Instance and that it is also no longer selectable in the drop-down list of the page.
All the custom form fields created on the reference environments are visible both in the database and from the UI of the new environment on the create new form page, however when attempting to create a form with the same name ("CONTRACT"), get the following error:
As it is no longer available as an option in the drop-down list and can not be recreated/updated, the imported form is rendered unusable and all the UI customizations designed for the form are lost.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!