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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
ATOM feed query parameter stopped working
Summary:
We are consuming the atom feeds utilizing the Query parameter (q) on the content element. Suddenly, the ATOM feed call breaks with the q parameter
Content (required):
We implemented a call to the newhire ATOM feed with utilized the query parameter to restrict the result set to an element in
content's Context JSON payload. This works fine in one of our development environments. However, in our second development environments, it suddenly stopped working this week. We receive a 500 error when we have the q parameter in the ATOM feed call. Does anyone have experience using the q parameter in the ATOM feeds?
1