Oracle Fusion HCM Other APIs aggregation

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

Version 8.3

Share all details related to your problem, including any error messages you may have received.

Hi Everyone,

We are currently using Oracle Fusion HCM connector as an authoritative source and are trying to pull the additional attributes from APIs other than worker APIs like the /hcmRestApi/resources/xx.xx/locations and /departments API.

I’ve gone through the documentation, it says that we should be able to pull these attributes by using attributeMappings and resourceIdsMappings. However, when trying to do the same I see the null values even though the values are populated on the HCM side.

It would be highly appreciated if someone can guide me on the same.

Thanks in Advance,
Nirmal Chitlangi

2

Hi @nirmalchitlangi,

Welcome to our community!

As per my understanding the OOTB Oracle Fusion HCM connector only gets data from the workers-endpoint.

We stepped away from the OOTB connector and switched to the Web Services Connector which is way more flexible. Our main requirement to switch was the authentication options. The OOTB only supports username-password authentication and that was not enough for our client (we are now using the JWT authentication).

– Remold

1 Like
3

@Remold, Thank you so much for your response…

We already have an application integrated with the Fusion HCM connector. Hence, I was trying to evaluate the feasibility of using the same connector for those extended APIs.

However, It seems I’ll have to configure a new application for the same.

Thank you,
Nirmal Chitlangi

4

If you really want to extend the functionality, to get all locations and departments, yes you need to switch to the Web Services application.

There are also a few other options like.
Departments and locations are quite static, you can get reports from Oracle HCM and read them in using a DelimitedFile-application (group, not account) to create Managed Attributes/Entitlements for the same.
In the HCM application, you can add customization rule, to find the correct department and location for the account (taken from the DelimitedFile entitlements) and add them to the account. Or create an identity attribute rule to do the same.

There are many ways to Rome :slight_smile:

– Remold

5

I had an idea of invoking the APIs from the customization rule but then I’m concerned on the performance of the aggregation time.

And TBH, the other problem that I’ve with this is I want to create identity records using those APIs as we have different record information in them.

  • Nirmal
6

last year we switched from another HR source to Fusion HCM. It indeed takes some extra time to validate the data returned is exactly the same.
Since you are not changing the HR source, but only the application, the data remains the same. By keeping the schema the same, it should not make a big difference.

In a lower environment you can test it using the ‘Reconfigure’ button:
image
Under schema use: Keep Extra Attributes Of Previous Application Type Schema

The account aggregation endpoung I am using is: /hcmRestApi/resources/11.13.18.05/workers?expand=workRelationships.assignments.managers,names,emails&onlyData=true

So, if you really need to have the extra attributes, I would switch to Web Service :stuck_out_tongue_winking_eye:

– Remold

7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.