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.
Fusion > Taleo OOTB Integration: Changing Job Codes in Fusion Creates Duplicate Requisition Template
Summary
The OOTB Integration appears to treat Job Code Changes in Fusion as new templatesContent
All:
We recently opted to create a new naming convention for our jobs in Fusion. In other integration testing, this doesn't appear to have negative impacts. However with the OOTB integration to TEE, we're finding no matter whether we've made the change(s) as an update or correction in Fusion, we get the same result - a second requisition template in TEE.
Is this expected behavior?
Thanks,
Mark
Version
17.5.2
Tagged:
0