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.
Recruiting Template Design
Summary
Standalone vs Job TemplateContent
With the redesign of recruiting templates in 19D - I'm curious how other users are using Standalone vs Job Recruiting templates. Our previous design was to have two "generic" templates (one for hourly jobs, one for salary jobs) plus specific job templates for our "most recruited for jobs" (cocktail server, chef, etc). From what I can tell, the actual JOB field doesn't exist on the templates anymore (I believe it did prior to 19D) so I am confused on what our best approach should be.
Note : We are not live at this time, we are in final design stage with a June golive.
Tagged:
0