Avoid Missing Atom Entries When Processing Them Page-Wise

The Oracle HCM Cloud Adapter fetches fewer entries from the Atom server as compared to Postman or curl in a single invoke. The Oracle HCM Cloud Adapter provides a solution to avoid missing these entries when processing them page-wise.

Assume you fetch a single page of entries when polling an Atom feed with Postman. If the last entry in the response/page has an identical updated timestamp as the next few entries on the consecutive invoke's response/page, these further entries (with the same updated timestamp) are never included in the subsequent response because the updated-min parameter is not inclusive. Similarly, in case future dated updates need to be fetched immediately and the published timestamp needs to be used, if the last entry in the response/page has an identical published timestamp as the next few entries on the consecutive invoke's response/page, these further entries (with the same published timestamp) are never included in the subsequent response because the published-min parameter is not inclusive.

To fix this issue, the Oracle HCM Cloud Adapter processes N- entries (the number of entries with the same updated timestamp/published timestamp towards the end of the page). Here, N is the total number of entries on the page. The remaining entries are included in the next invocation. This ensures that no entries are skipped.