Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
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.
How to identify areas that are calling the EMPS REST API
Summary:
How to identify areas that are calling the EMPS REST API
Content (required):
Hi Team,
Greetings!
Oracle will no longer support the EMPS REST API with the application of Update 23D. Prior to receiving Update 23D, customers MUST transition to the Workers REST API which provides richer capabilities and more robust functionality.
Considering this update-
How do we identify areas that are calling the EMPS REST API (customized Alerts, ATOM feed handlers, OIC, and other custom integrations)? What is the best/optimum way to get the correct list as part of the impact analysis before remediation?
Thanks
Parag
Version (include the version you are using, if applicable):
1