Subscribe to Atom Feeds in a Scheduled Integration
This use case provides an overview of creating a scheduled orchestrated integration using the Oracle HCM Cloud Adapter to subscribe to Atom feeds. Atom feeds enable you to track changes made to feed-enabled resources in Oracle Global Human Resources Cloud. For any updates of interest to downstream applications such as new hires, terminations, employee transfers, and promotions, Oracle Global Human Resources Cloud publishes Atom feeds.
For this use case, the Oracle HCM Cloud Adapter is configured with the Atom feed Employee Update. This feed consists of three updates (PrimaryPhoneNumber, CitizenshipStatus, and CitizenshipId). An FTP Adapter is also configured to write any feed updates to an FTP server.
- Entries that are already effective.
- Entries that are effective in the future (known as future dated entries).
- Future dated entries are processed on their effective dates.
- Future dated entries are processed immediately.
Note:
Any new Atom feed endpoint that uses Employee-related feeds (for example, new hire, assignment, termination, and updates) with a business object now uses the Workers resource in both design time and runtime. The Workers resource is visible in the mapper.Any existing Atom feed endpoint continues to use the Emps resource for employee-related feeds when it is already deployed with a business object for backward compatibility and to avoid the need for remapping. All new deployments with the Atom feed must use the Workers business object.
The following example shows the Employee update feed with a business object in the mapper:

Process Future Dated Entries on Their Effective Dates
Oracle Global Human Resources Cloud processes future dated entries on their effective dates. This use case provides an overview of how to design this type of integration.
Process Future Dated Entries Immediately
Oracle Global Human Resources Cloud processes future dated entries immediately, as soon as they are published. This use case provides an overview of the differences between designing an integration to process future dated entries on their effective dates and designing an integration to process future dated entries immediately.
- On the Operations page, select Process Future Dated Entries Immediately. Enabling this checkbox changes the request map to have a different query parameter, published-min.
- In the request mapper between the schedule and the Oracle HCM Cloud Adapter, map $ts (timestamp value) to
published-min.
- To make future dated entries available immediately in the feed, you must send
published_timestamp as
published-min in the request.
published_timestamp must also be persisted in the
ts scheduled parameter to process new entries in
subsequent invokes of the flow. ts must store the
published_timestamp.
Summary
In summary, the following changes are required in the integration for handling future dated entries.
Future Dated Entries Options | Request Parameters | Timestamp Stored in Schedule Parameter |
---|---|---|
Processed immediately | published-min | published_timestamp |
Processed on their effective dates | updated-min | updated_timestamp |