Summary of the Form Version Control Process

22-6 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager Sample line: Child;UD_OID_GRP_NORMALFIELD;XYZ;Update – ParentParent;OLD_FIELD_NAME;NEW_FIELD_NAME On the parent form, the utility moves data from the OLD_FIELD_NAME field to the NEW_FIELD_NAME field. Sample line: ParentParent;UD_OID_USR_FNAME;UD_OID_USR_DEFTVAL; – ParentParentLookupOrComboToCheckBox;OLD_FIELD_NAME;NEW_FIELD _NAME; On the parent form, for a Lookup Field or Combo Box type field that has been changed to a Check Box type field and also renamed, the utility sets the check box for each record to the selected state if the field value is True case insensitive. For all other values, the utility sets the check box to the deselected state. Sample value: ParentParentLookupOrComboToCheckBox;UD_OID_USR_PREF_LANG;U D_OID_USR_CHKBOXTEST – ChildChild;OLD_FIELD_NAME;NEW_FIELD_NAME On the child form, the utility copies data from the OLD_FIELD_NAME field of the earlier version to the NEW_FIELD_NAME field of the new version. Sample line: ChildChild;UD_OID_GRP_GROUP_NAME;UD_OID_GRP_NORMALFIELD – ParentChild;OLD_FIELD_NAME;NEW_FIELD_NAME The OLD_FIELD_NAME field was moved from the parent form to the child form and renamed to NEW_FIELD_NAME. The utility moves data from the OLD_FIELD_NAME field to the NEW_FIELD_NAME field. Sample line: ParentChild;UD_OID_USR_FNAME;UD_OID_GRP_NORMALFIELD – ChildParent;OLD_FIELD_NAME;NEW_FIELD_NAME The OLD_FIELD_NAME field was moved from the child form to the parent form and renamed to NEW_FIELD_NAME. The utility moves data from the OLD_FIELD_NAME field to the NEW_FIELD_NAME field. Sample line: ChildParent;UD_OID_GRP_NORMALFIELD;UD_OID_USR_DEFTVAL – ChildParentLookupOrComboToCheckBox;OLD_FIELD_NAME;NEW_FIELD_ NAME From a child form, a Lookup Field or Combo Box type field OLD_FIELD_NAME has been changed to a Check Box type field and moved to the parent form. On the parent form, the utility sets the check box for each Note: If a mandatory required field has been added on the child form, then you must include this line in the properties file. Using the Form Version Control Utility 22-7 record to the selected state if the field value is True case sensitive. For all other values, the utility sets the check box to the deselected state. Sample line: ChildParentLookupOrComboToCheckBox;UD_OID_GRP_GROUP_NAME;U D_OID_USR_CHKBOXTEST – ChildDiffChild;OLD_FIELD_NAME;NEW_FIELD_NAME The utility moves data from the OLD_FIELD_NAME field on the source child form to the NEW_FIELD_NAME field on the target child form. Sample line: ChildDiffChild;UD_OID_GRP_NORMALFIELD;UD_OID_ROLE_DIFFFIEL D

22.5.2 Addressing Prerequisites for Using the FVC Utility

Before you run the utility:

1. Set the Java home directory path in the FVC Utility script as follows:

a. Depending on the operating system and application server that you are using,

open one of the following files in a text editor: fvcutil.sh fvcutil.cmd

b. Search for set JAVA_HOME.

c. Set the Java home directory path as shown in the following example:

set JAVA_HOME=C:\Java\

d. Save and close the file.

2. Verify that the version of the process parent form on which you want to run the

utility is the Active version. To check if the version of a form is the Active version:

a. Log in to the Design Console

b. Expand the Development Tools folder, and then double-click Form Designer.

c. Search for and open the form.

d. Active Version field of the form displays the active version of the form.

3. The utility cannot update a form field if the field is associated with error-handling

adapters. If any field is associated with error-handling adapters, then dissociate the adapters as follows: Note: This update is carried out only if the source child form contains a single row. A scenario in which the source child form contains more than one row is not supported. Note: After you run the utility, you can again set up the association between the field and its error-handling adapters. The procedure is described later in this chapter.