Upgrade Considerations

• (Optional) After upgrading to the latest version of IdentityIQ, perform the following for provisioning of a responsibility of type other than ‘Oracle Applications’:

  1. Go to Provisioning Policies > Create Group.
  2. In Responsibility Version, select Edit. Select Edit Options > Settings, and modify the name from PASSWORD_EXPR to VERSION.
  3. Select Edit Options > Value settings. In Allowed Values enter Oracle Mobile Application and select the + icon.
  4. Select Apply and Save the provisioning policy.
  5. Select Save on the next screen and save the application.

• Account Aggregation Filters

  After upgrading to the latest version of IdentityIQ, by adding the <entry key="useEffectiveDate" value="true"/> parameter in the application debug page, users have the ability to select the type of users to be aggregated: Employees, Contractors, Employees and Contractors, or all users from FND_USER table.

  For more information on adding the useEffectiveDate parameter, refer to Additional Configuration Parameters.

• Assigning responsibilities to future dated E-Business users

  After upgrading to the latest version of IdentityIQ, the Oracle E-Business Suite connector will be able to provision and aggregate future E-Business users. If responsibilities are provided in the create request of the future user, the connector will use the user's start date as the responsibility assignment's start date.

  For provisioning of future dated users for the application created prior to the previous IdentityIQ version, add the skipFutureAssignedGroups entry key to the application debug page. For more information, refer to Additional Configuration Parameters.

• Disabling existing accounts during provisioning

  After upgrading to the latest version of IdentityIQ, the Oracle E-Business Suite connector will be able to disable any existing active FND accounts.

  For disabling any active FND accounts for the application created prior to the previous IdentityIQ version, set the value of the disableOldFNDAccounts parameter to true in the application debug page. For more information, refer to Additional Configuration Parameters.

• Identifying responsibility group uniquely

  After upgrading to the latest version of IdentityIQ, the Oracle E-Business Suite connector can use a combination of Responsibility_id and Application_id to identify the responsibility group uniquely for new applications.

  For the existing application, the user can use this feature by setting the value of the useResponsibilityWithApplication to true in the application debug page.

  For more information, refer to Additional Configuration Parameters.

  Note
  After setting the value of the useResponsibilityWithApplication attribute to true, the previous entitlement data cannot be retrieved.

• After upgrading to the latest version of IdentityIQ, the Oracle E-Business Suite Connector will not aggregate indirect roles and responsibilities assigned to Oracle E-business users during account aggregation.
• After upgrading to the latest version of IdentityIQ, you can aggregate disabled accounts on the previous application of Oracle E-Business Suite, by setting the value of the aggregateActiveAccounts parameter to false in the application debug page.

• After upgrading to the latest version of IdentityIQ, you can aggregate the MENU GroupObjectType attribute by performing the following:

  • Add the MENU attribute in the RESPONSIBILITY schema through the application debug page as follows:

    <AttributeDefinition multi="true" name="MENU" schemaObjectType="MENU" type="string">

    <Description> Menu assigned to a Responsibility </Description>

    </AttributeDefinition>

  • Add the MENU GroupObjectType attributes to the schema manually through the application debug page as follows:

    <Schema aggregationType="group" descriptionAttribute="MENU_NAME" displayAttribute="MENU_NAME" identityAttribute="MENU_ID" nativeObjectType="MENU" objectType="MENU">

    <AttributeDefinition name="MENU_ID" type="string">

    <Description> An internal ID for the menu </Description>

    </AttributeDefinition>

    <AttributeDefinition name="MENU_NAME" type="string">

    <Description> The name of the menu </Description>

    </AttributeDefinition>

    <AttributeDefinition name="TYPE" type="string">

    <Description> The type of menu </Description>

    </AttributeDefinition>

    <AttributeDefinition entitlement="true" multi="true" name="SUB_MENU" schemaObjectType="MENU" type="string">

    <Description> The list of sub-menus </Description>

    </AttributeDefinition>

    <AttributeDefinition multi="true" name="FUNCTION_NAME" type="string">

    <Description> The functions assigned to a menu </Description>

    </AttributeDefinition>

    </Schema>

    For more information on the additional MENU GroupObjectType attributes, refer to Group Attributes.