Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
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.

Recruiting Template Design

edited Feb 17, 2020 2:12PM in Recruiting, Opportunity Marketplace 3 comments

Summary

Standalone vs Job Template

Content

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.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!