Select Extensible and Descriptive Flexfields in an Integration

You can select specific extensible flexfields (EFFs) and descriptive flexfields (DFFs) in the Adapter Endpoint Configuration Wizard of an Oracle HCM Cloud Adapter invoke connection. You can then map the EFFs and DFFs in the mapper.

The following use case provides an overview of how to design this type of integration.
  1. Create an orchestrated integration.
  2. Add a REST Adapter as a trigger connection.
  3. Enter the following details:
    1. On the Basic Info page, enter a name.
    2. On the Resource Configuration page, select the POST action and Configure a request payload for this endpoint and Configure this endpoint to receive the response.
    3. On the Request page, select the following:
      1. Select JSON sample as the request payload and enter the JSON sample.
      2. From the Element list, select request-wrapper.
      3. For the media type of the request body, select JSON.
    4. On the Response page, select the following:
      1. Select JSON sample as the response payload and enter the JSON sample.
      2. From the Element list, select response-wrapper.
      3. For the media type of the response body, select JSON.
  4. Add an Oracle HCM Cloud Adapter as an invoke connection.
  5. Enter the following details.
    1. On the Basic Info page, enter a name.
    2. On the Actions page, select Query, Create, Update, or Delete Information.
    3. On the Operations page, select Business (REST) Resources from the Browse by list.
    4. Select an appropriate business resource and operation to perform on the resource.
    5. On the Child Resources page, select child resources with extensible or descriptive flexfields.
    6. On the Descriptive and Extensible page, select a specific flexfield and associated contexts.
  6. In the request mapper between the two adapters, map appropriate source and target flexfields. For example:
  7. In the response mapper after the Oracle HCM Cloud Adapter, map appropriate source and target flexfields. For example:
  8. Save the integration.
    The completed integration shows a REST Adapter trigger, a mapper, an Oracle HCM Cloud Adapter, a mapper, and a return icon.

  9. Create business identifiers for tracking the integration during runtime.
  10. Activate the integration.