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.
Using Job Offer Flexfields in Both Recruiting and HR
Summary
Customer generates contracts (job offers) both in Recruiting for successful candidates and in HR for change to circumstances that require an updated contract.Content
The customer has a large number of contract types, and the requirement means we will have to duplicate the number of contracts / job offer templates created. If the customer has 100 different contract types based on their terms and condition, we would require 200 to be defined (100 in Recruiting and 100 in HR).
I am suggesting limiting the number of contracts to maybe 10, and identifying the blocks within the contracts that are different, that we may use a dynamic process to pull them during the job offer creation as parameters/selection list.
Tagged:
0