Troubleshooting Remote Manager Oracle Fusion Middleware Online Documentation Library

22-4 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager ■ If you are upgrading from a predefined release to a predefined release of a connector, then look for a properties file in the connector deployment package. ■ If you are upgrading from a custom release or upgrading to a custom release, then you must add the required entries in the properties file. ■ If you are upgrading from a custom release to a predefined release of a connector, then see if the connector guide provides information about changes to the process form and child forms of the connector. You can use this information to determine the entries that you must add in the properties file. The following are sample entries for the properties file: ResourceObject;OID User FormName;UD_OID_USR FromVersion;8 ToVersion;9 Parent;UD_OID_USR_DEFTVAL;ABC Child;UD_OID_GRP_NORMALFIELD;XYZ;Update ParentChild;UD_OID_USR_FNAME;UD_OID_GRP_NORMALFIELD ChildChild;UD_OID_GRP_GROUP_NAME;UD_OID_GRP_NORMALFIELD ChildParent;UD_OID_GRP_NORMALFIELD;UD_OID_USR_LNAME ParentParent;UD_OID_USR_FNAME;UD_OID_USR_LOGIN; ParentParentLookupOrComboToCheckBox;UD_OID_USR_PREF_LANG;UD_OID_USR_CHKBOXTEST ChildParentLookupOrComboToCheckBox;UD_OID_GRP_GROUP_NAME;UD_OID_USR_CHKBOXTEST ChildDiffChild;UD_OID_GRP_NORMALFIELD;UD_OID_ROLE_DIFFFIELD Apply the following guidelines while adding or modifying entries in the properties file: ■ In the properties file, each line consists of the use case name, followed by old field name and the new field name. Each of these are separated by semicolon. For Example consider following entry in properties file: ParentChild;UD_OID_USR_FNAME;UD_OID_GRP_NORMALFIELD ParentChild: represents that the fields of the parent have been renamedmoved to be in the new child form UD_OID_USR_FNAME: represents the old field name in parent form UD_OID_GRP_NORMALFIELD: represents the new name of the field to be upgraded in the new form. ■ You must include the following lines in the properties file: – ResourceObject;RESOURCE_OBJECT_NAME Note: See the sample entries listed earlier to get a better understanding of the guidelines. Note: There can be spaces in the value as long as a space does not appear immediately after the semicolon. Note: The location and order of these 4 lines in the properties file does not matter. Using the Form Version Control Utility 22-5 In this line, replace RESOURCE_OBJECT_NAME with the name of the resource object. Sample line: ResourceObject;OID User – FormName;FORM_NAME In this line, replace FORM_NAME with the name of the process parent form. Sample line: FormName;UD_OID_USR – FromVersion;CURRENT_VERSION_OF_FORM In this line, replace CURRENT_VERSION_OF_FORM with the current version of the form. Sample line: FromVersion;8 – ToVersion;NEW_VERSION_OF_FORM In this line, replace NEW_VERSION_OF_FORM with the new version of the form. Sample line: ToVersion;9 ■ You can include any combination of the following lines in the properties file: – Parent;FIELD_NAME;DEFAULT_FIELD_VALUE;Update For all records on the parent form, the utility updates the value of the FIELD_NAME field with DEFAULT_FIELD_VALUE. Sample line: Parent;UD_OID_USR_DEFTVAL;MyString;Update – Child;FIELD_NAME;DEFAULT_FIELD_VALUE;Update For all records on the child form, the utility updates the value of the FIELD_NAME field to DEFAULT_FIELD_VALUE. Note: When you run the FVC Utility, only records whose version is the same as CURRENT_VERSION_OF_FORM are updated by the utility. Note: If you want to update form data on a form whose version has not changed, then set NEW_VERSION_OF_FORM to the same value as CURRENT_VERSION_OF_FORM . Note: If a mandatory required field has been added on the parent form, then you must include this line in the properties file for the mandatory field.