Last updated on DECEMBER 02, 2016
Applies to:Oracle iRecruitment - Version 18.104.22.168 and later
Information in this document applies to any platform.
Disclaimer: Please note that this is a customization and is available for use at your own risk. Do not expect Oracle Support personnel to walk you through your customization setup to troubleshoot errors. We highly recommend you make copies of the seeded responsibilities; we cannot walk through each change and verify it - that is your responsibility. If you change back to the seeded responsibility and it works, then your custom responsibility is setup incorrectly. You will need to step through each change carefully, while checking something as simple as a space or spelling or as complex as adding a link to a page.
Typically, an organization may have multiple business groups. Oracle iRecruitment provides a predefined configuration, which consists of a single JSP: IrcVisitor.jsp that enables external candidates to apply for jobs in any business group in the organization.
However, in an organization that has multiple business groups, it is required to create multiple External Candidate JSPs, one for each business group.
When multiple External Candidate JSPs are created, every JSP would correspond to a business group in that organization and access to other business groups from that JSP can be blocked. When external candidates log in to iRecruitment using the JSP associated with a business group, they can search only vacancies in that business group. During vacancy search from a JSP, only vacancies in a specific business group are visible. Changing the profile options will change the functionality and this allows you to customize your setup as per your requirement.
This document explains how to create custom multiple JSPs and use them in Oracle iRecruitment to meet your business requirements.
You must create this setup on a test instance first and test the setup thoroughly to understand the functionality.
For example, if you create multiple JSPs, you must note what happens when an external candidate registered through one JSP attempts to log in through another JSP and ensure that this behavior is in line with your expectations from the setup. This is just one scenario and several others must be tested before applying this setup to production.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms