Trigger JML as soon as SuccessFactor Data changes

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hi All,

Is it possible to process the live data from SF i.e. SailPoint should process the joiner, mover, leavers as soon as the changes have been made in SF.

2

For Joiners, it’s going to be pretty hard since those records don’t exist in IDN yet, but if SuccessFactor has the ability to make outbound API calls triggered by changes to worker attributes and termination, you can point it at the Reload Account API endpoint and have it reload that worker’s SF account specifically.

3

You can get it to be as close as to real time depending upon how soon you get the data in IDN and also, how much data is coming.

4

I think the API call to trigger should be cc/api/source/loadAccounts/:cloudExternalId
that will run an optimized aggregation on the source

5

Two problems with that:

  1. That’s using a cc API, which means it’s not a good long-term production solution as those are getting ready to be deprecated.
  2. That triggers an optimized agg on the entire source, which could take a long time depending on how many accounts/attributes there are at play. If that’s being triggered whenever there’s any update done in the HRIS system, that’s going to be a bad time and likely result in a lot of errors due to already-running aggregations.
2 Likes
6

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