Hello everybody, I’m integrating Oracle HCM Cloud to Sailpoint ISC. I know that by documentation the connector expects future,active and inactive workers in different files, but the client is send them inside one unique file and it marks as active,inactive or future inside one specific attribute field. Can I manage these kind of workers trough the attribute? For example , can I create a workflow that triggers when an account change and send a POST API to Sailpoint in order to disable /enable accounts that become active/inactive?
You can certainly manage them through an attribute, but you won’t need a workflow to trigger anything. Just use profiles and lifecycle states to enable/disable accounts
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.