Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Extract Behavior with Changes Only parameter as Blank

edited Feb 1, 2021 6:32AM in HCM Integrations 4 comments

Summary

HCM Extract behavior when scheduled / submitted with Changes Only parameter set as blank.

Content

Hello, 

I'd like to know if anyone has come across / looked into this aspect of HCM Extracts - 

While submitting the extract, how would a changes only extract behave 
1) If the Changes Only parameter was left blank while submitting? 
2) If the default value for the changes only parameter was updated to a value, say BLOCK, after submitting the extract? (While submitting the field was set as blank)
3) If the parameter values were updated at Refine Extracts > Parameters tab to say BLOCK / BLOCK_OLD

We have an extract that was (accidentally) scheduled for a week in a similar manner and was hoping to look at options before I head to the Scheduled Processes to cancel and reschedule.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!