15Job Posting and Job Boards
Job Posting and Job Boards
Requisition Posting Process
Requisition posting consists of publishing a requisition in order to have candidates applying on the job.
Once a requisition has been created and approved, the next step is to post it. Here is a basic posting and sourcing process. System administrators create a master Source Tracking list which is used by recruiters and candidates. Recruiters post requisitions to Career Sections. Recruiters can post to additional sources such as job boards, agencies and also use gateways to send out requests for sourcing help. Candidates apply to jobs and complete the Source Tracking information. Some tracking is automated if the candidates are coming from certain job boards. They can also put in event ID's from advertisements. Once the source of the candidate is tracked, recruiters then can view the information in the candidate file.
Accessing the Posting and Sourcing feature
There are several ways to access the Posting and Sourcing feature:
When a requisition is ready for posting or already posted, you can click the Status Detail link in the requisitions list and you will be taken to the Posting and Sourcing tab of the requisition.
From the More Actions menu within the requisition file.
From the Posting and Sourcing tab within the requisition file.
From the Contextual Action menu in the requisitions list.
From the Tasks channel, the Ready for Sourcing link will take you directly to a list of requisitions that need to be posted.
Places and services to post requisitions
Depending on what your organization has activated and your permissions, the Posting and Sourcing feature provides several services to post requisitions:-
Internal or external career sections.
Mobile career sections: Customers can specify if a career section can be accessed from mobile devices. When candidates receive a message on their mobile device regarding a new job opening and decide to take a look at the job while using their mobile device, candidates are automatically redirected to the mobile career section and are able to view and apply for the job. System administrators specify if the career section is a mobile career section and then link the standard career section to a mobile career section. When a requisition is posted to a standard career section, the system automatically posts the requisition to the mobile career section to which the standard career section is linked. In the Recruiting Center, when posting a requisition, the mobile career section to which a standard career section is linked is not displayed in the Career Sections list. This is to prevent users from posting requisitions directly to a mobile career section.
-
eQuest job boards: Recruiters can post their requisitions to multiple job boards through the eQuest job distribution portal. Recruiters must post a requisition on a career section before posting the requisition to a job board. A requisition can be posted as many times as required but it cannot be posted twice on the same job board account. All job board accounts to which a requisition is already posted will be unavailable in the Sourcing Manager page. The requisition must be posted on an external company career section for at least the same time as on eQuest job board account.
Certified job posting distribution suppliers: Recruiters can select a certified job posting distribution supplier (other than eQuest) that will distribute job postings through job boards. A new type of Oracle Validated Integration (OVI) has been put in place to allow integrations with job posting distribution suppliers. Recruiters must post a requisition on a career section that is external and public before posting the requisition to a job board.
-
Staffing agents: Users can ask an advertising agency to post an ad.
-
Non-electronic media such as newspapers, magazines and trade publications, billboards and broadcasting. A list of preferred non-electronic media can be created in My Setup, under Preferences.
Gateways such as internet mining.
When posting a requisition, the system dynamically calculates the posting start date and end date for the mobile career section. The posting start date and end date on the mobile career section are based on the dates of the standard career section to which the mobile career section is linked.
If the mobile career section is linked to a single standard career section, the posting start date and end date of the standard career section are used.
If the mobile career section is linked to multiple standard career sections, the earliest start date among the standard career sections is used; the latest end date among the standard career sections is used.
Requisition Posting Permissions
Permissions are granted to Recruiting Center users so they can post requisitions.
| User Type Permission | Description | Location |
|---|---|---|
| Access Posting and Sourcing | Provides access to the requisition Posting and Sourcing tab. | Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Sourcing |
| Post requisitions | Allows users to post requisitions to career sections and job boards. When a user receives a Ready for Sourcing task, the user must have the "Post requisitions" permission to be able to complete the task. |
Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Sourcing |
| Post to staffing agents/agencies | Allows users to post, unpost and extend the posting of requisitions via staffing agents and agencies. | Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Sourcing |
| Request Internet mining by specialized agencies | Allows users to request resume searching services over the Internet. | Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Sourcing |
| Invite matching candidates to apply | Allows users to preview, select and request the sending of job posting notifications. | Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Sourcing |
| Submit ads to non-electronic media | Allows users to submit a request to post requisitions in non-electronic media. | Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Sourcing |
| Prevent and allow posting | Allows users to do the Prevent Posting and Allow Posting actions in order to block or unblock the publication of a requisition. | Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Sourcing |
| Extend posting and unpost | Allows users to extend the posting and to unpost requisitions on career sections, job boards and staffing agencies. | Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Sourcing |
| Request sourcing strategy by specialized agencies | Allows users to request a sourcing strategy | Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Sourcing |
| Access the posting through social networks feature | Allows users to share the career section url with different social networks. | Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Sourcing |
| Distribute job postings to job boards | Enables users to post requisitions to job posting distribution suppliers. See Certified Job Posting Distribution Suppliers. | Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Sourcing |
Requisition Posting via eQuest Job Boards
Recruiters can post their requisitions to multiple job boards through the eQuest job distribution portal.
eQuest job board accounts are created by the system administrator. These accounts must first have been created in eQuest, with the same user name and password defined by the system administrator. Therefore, job boards available for a specific account are set by eQuest. The system administrator can create as many accounts as needed. However, only one account can be designated as the default account.
A list of core job boards is bundled with the Recruiting Cloud Service subscription. Customers must work with eQuest for additional job boards. This list is subject to change.
Monster - All US and International locations.
USAJOBS - United States.
CareerBuilder - United States.
LinkedIn - All US and International locations.
Workopolis - Canada.
SEEK - Asia Pacific.
Wildcard - Two additional job boards may be selected from eQuest's current list of electronically supported job boards at inception of their Taleo contract ("Additional Core Board"). eQuest will support a process to allow customers to change their Additional Core Boards up to one time per year following the customer's first anniversary date of contract with eQuest.
In the event that a customer requests the delivery of job postings to a job board that is not in the above list, such request may be referred to eQuest to be managed via a direct contract between eQuest and the customer.
Once the Oracle Talent Acquisition Cloud (OTAC) integration setup is completed for eQuest, eQuest will work directly with the customer to collect appropriate credentials and complete setup to any core job boards or non-core job boards and any related configuration for customer reporting and analytics. eQuest will provide customers with an Activity Report each month listing key data elements associated with each job posting, including date of insertion, recruiter name, requisition number, job title and job location, and total eQuest transactions for the prior month.
Creating a Job Board Account
Click New...
Under the Properties tab, select eQuest in the Supplier drop-down list.
Enter a name for the account. The name is displayed in the requisition to distinguish the different accounts created with eQuest.
In the language drop-down list, select a language. The language drop-down list is used to provide the account name in different languages.
Under the Login tab, provide a login name and a password. The login name and password are used to automatically log the user in the job board's system. When clicking Post, the job board's page is opened and the user is already logged in with this account. The login name must be unique for each job board.
Under the Permissions tab, indicate if the job board account is the default account.
If the job board account was not designated as being the default account, you can associate the job board account with specific organizations, groups or users. When a recruiter is posting a requisition to a job board, job board accounts to which the recruiter user is assigned and those matching at least one of the specified organizations or groups of the requisition will be available for selection.
Click Save.
The newly created job board account appears in the Job Board Accounts list.
Sending Customer City and Zip/Postal Code to eQuest
Organizations can send the customer city and its zip/postal code to eQuest.
The setting City Location Level for eQuest Posting allows system administrators to specify the location level that will be considered when posting a requisition to eQuest. Once set, the location sent to eQuest to represent the requisition city will no longer be the reference locations level 3 and its postal code, but the location level specified in this setting. This will allow recruiters to post a requisition to the most precise city location, usually located at level 3 or level 4.
| Setting | Description | Possible Value | Location |
|---|---|---|---|
| City Location Level for eQuest Posting | When posting requisitions to eQuest, the level specified here will be considered as the location level for cities. | A number from 1 to 5 based on locations configuration | Configuration > [Recruiting] Settings |
In SmartOrg (under Locations Element Management), the Zip/Postal Code field is available for each level of location.
In Recruiting, when associating a Location structure to a requisition, the zip/postal code set for the location in SmartOrg is used by eQuest to post a requisition on a job board at the appropriate location (instead of using the reference locations set by the system), provided the City Location Level for eQuest Posting setting has been configured in the administration module.
Requisitions can be associated to any level of company defined locations. When Oracle sends the requisition to eQuest, we always try to send three location values:
Country: this is derived from the mapping between location and the reference location level 1 done in SmartOrg by the administrator.
State/Province: this is also derived from the mapping done in SmartOrg between the location and location level 2. This exists only if the requisition has an associated location at least at the state/province level.
City: by default, this is also derived from the mapping between location and location at level 3, if the requisition is associated to a location with a level 3 mapping. If not, such information is not sent to eQuest, although it is usually required, depending on the country and job board. With the City Location Level for eQuest Posting setting, customers can send a more precise location, as defined in SmartOrg, instead of sending the broader location level 3, which represents a region rather than a city. For a large city such as San Francisco, this does not change the situation that much, although you can define a more precise zip/postal code if required. But for a city like Dublin, CA, which does not exist in our list of reference regions, you can now use your own location instead of using the closest region, which would be Hayward on this example, which is about 10 miles away.
Zip/postal codes will be considered by eQuest when posting a requisition only if the zip/postal code is for the US and few other countries, but not all.
Sending Department Code to eQuest
Organizations can send the department code in order to do some reporting in eQuest.
The setting Send Department Information to eQuest When Posting Requisitions allows system administrators to specify if the department number will be provided to eQuest when posting requisitions to eQuest. This is not used for posting purposes, but rather to allow reporting at the department level in eQuest.
| Setting | Description | Default Value | Location |
|---|---|---|---|
| Send Department Information to eQuest When Posting Requisitions | Send department information to eQuest when posting requisitions. By default, department information is not sent. | No | Configuration > [Recruiting] Settings |
Deleting a Job Board Account
Select a job board account.
Click the Delete icon.
The job board account no longer appears in the Job Board Accounts list.
The job board account will no longer be displayed in Recruiting Center to users with appropriate permission.
Requisition Posting via Certified Job Posting Distribution Suppliers
A new type of Oracle Validated Integration (OVI) has been put in place to allow integrations with job posting distribution suppliers so that customers can select their suppliers of choice.
Customers first need to sign a contract with their job posting distribution suppliers of choice. The supplier must have worked with Oracle to provide a certified integration. If such an integration is available for the desired supplier, customers can request the integration to be made available on their zone. Then, Recruiting Center users who have the permission to distribute job postings to job boards are able to select these certified job posting distribution suppliers.
Recruiters can select certified job posting distribution suppliers via the Job Boards section, under the requisition Posting and Sourcing tab. To post a requisition to a job posting distribution supplier, recruiters must first post the requisition on a career section that is external and public.
After selecting a supplier and account and clicking the Post button, recruiters are asked to select a language if the integration was configured to distribute requisitions in multiple languages. The requisition content provided to the job posting distribution supplier is provided in the selected language.Recruiters are then taken to a page where they need to provide different information. The main part of the page is provided by the supplier. Some of the requisition information is automatically provided to the supplier, making it possible to pre-fill some fields requested by the supplier. When recruiters are done completing the information, they are taken back to the Recruiting Center Posting and Sourcing tab and the list of job board postings is updated to show the job boards where the requisition has been posted.
The list of job board postings shows all the job boards on which a requisition is posted, unposted, scheduled to be posted, etc. The following information and actions related to a job posting distribution supplier are available:
Supplier: Shows the various suppliers that are active on the zone, certified job posting distribution suppliers or eQuest.
Account: Shows the accounts available to the current user. The Account list is sorted to show the most relevant account for the user (based on the information configured on his user account).
Job Board: Name of the job board.
Language: Language in which the requisition was posted on the job board.
Status: Status of the job board. See below for a complete list of possible statuses.
Start Date: Requisition posting start date.
End Date: Requisition posting end date.
Post: The Post button launches the job distribution process for the requisition. The posting is performed by using the selected supplier and account. It is possible to Post the same requisition using multiple suppliers and/or accounts. This requires the user to repeat the posting process multiple times.
Unpost: The Unpost button makes it possible to unpost the requisition from individual job boards. An unpost request is sent to the job posting distribution supplier and the requisition is unposted. No further action is required by the user.
Unpost All: The Unpost All button unposts the requisition from all job boards where it is currently posted. An unpost request is sent to the job posting distribution supplier and the requisition is unposted. No further action is required by the user.
Refresh Status: The Refresh Status button updates the information displayed in the Job Boards list. The information in this list is not updated automatically (unless an action such as Unpost is performed). Users need to click the Refresh Status button to get the most up to date information.
Not posted
Incomplete
Authorization required
Scheduled for posting
Being processed
Posting request in process
Posted
Posted - User update incomplete
Posted - Unposting request in process
Posted - Update request in process
Posted - Update authorization required
Unposted
Expired
Error
In the requisition file History tab, three different types of events can be created by the job distribution feature:
Requisition Posting (Job Board ): Used when the user clicks on the Post button.
Requisition Unposting (Job Board ): Used when the user clicks on the Unpost or Unpost All button.
Requisition Posting Status Change: Used when the status displayed for a posting on a job board changes, whatever the status is Posted, Expired, Unposted, Error, etc.
Granting the Job Posting to Job Boards Permission
Select a user type.
Click Recruiting.
Click Edit next to Sourcing.
Select the permission Distribute job postings to job boards.
Click Save.
Configuring the Supplier Service
The job posting distribution supplier must work with Oracle in order to be certified.
Once the above is done, system administrators can configure the supplier as a sourcing service. Properties and settings must be specified and the service is then activated. Oracle Support needs to deploy the integration in the zone (after that administrators can activate it).
Click on the service name.
Click Edit next to Properties.
Edit the Properties fields as required. For details, see Job Posting Distribution Supplier Service Properties and Settings.
Define the values for each of the settings. For details, see Job Posting Distribution Supplier Service Properties and Settings.
Click Save.
Click Activate.
Once the supplier service has been activated, system administrators can add user accounts to be used for this supplier by using the Job Board Accounts feature in Recruiting Administration. See Creating the Supplier Account.
Creating the Supplier Account
Click New...
Under the Properties tab, select the certified supplier in the Supplier drop-down list.
Enter a name for the account. The name is displayed in the requisition to distinguish the different accounts created with a specific job posting distribution supplier.
Select a language in the drop-down list. The language drop-down is used to provide different values to the "Account-specific name". For example, if you select French, you can type in the French account name, then select English and provide the English account name.
Under the Login tab, provide a login name and a password. The login name and password are used by Oracle to automatically log the user in the supplier's system. When clicking Post, the supplier's page is opened and the user is already logged in with this account. The login name must be unique for each supplier.
Under the Permissions tab, indicate if the supplier account is the default account. Designating a supplier account as the default account makes it available to all users having access to the Job Boards feature.
If the account was not designated as the default account, the account can be associated with any number of organizations, groups and users. When a recruiter is posting a requisition to a job board, only the job board accounts having the same organizations, groups and users as those specified in the requisition are displayed for selection.
Click Save.
The newly created supplier account appears in the Job Board Accounts list.
Job Posting Distribution Supplier Service Properties and Settings
| Property | Description | Location |
|---|---|---|
| Name | Name of the sourcing service. | Configuration > Recruiting Administration > Integration > Candidate Sourcing |
| Description | Description of the sourcing service. | Configuration > Recruiting Administration > Integration > Candidate Sourcing |
| Provider Name | Name of the provider. | Configuration > Recruiting Administration > Integration > Candidate Sourcing |
| Provider Description | Description of the provider. | Configuration > Recruiting Administration > Integration > Candidate Sourcing |
| Setting | Description | Location |
|---|---|---|
| Requisition Posting Language |
Possible values are:
|
Configuration > Recruiting Administration > Integration > Candidate Sourcing |
| Highest security level of fields that can be sent when posting requisitions |
For example, if a field is marked Confidential and this setting is set to General, the field will not be sent when posting requisitions. Possible values are:
|
Configuration > Recruiting Administration > Integration > Candidate Sourcing |
| Location level to be considered as a city when posting requisitions to Multiposting | The number entered in the field represents the location level to be considered as a city. | Configuration > Recruiting Administration > Integration > Candidate Sourcing |
Candidate Information Import from USAJOBS
Candidates coming from USAJOBS (the official job site of the U.S. federal government) can automatically log into a Career Section and automatically import their USAJOBS profile into a job submission.
Below is the basic flow of activities taking place when applying through USAJOBS.
Posting a requisition on USAJOBS
Requisitions can be posted on the USAJOBS Web site through eQuest (requisitions are posted on other job board in the same manner).
Creating an account on USAJOBS
When creating an account on USAJOBS, candidates need to create their general profile by providing general information such as their name, telephone number, email address. They also need to create a resume by providing their work experience, education, references. Candidates can create multiple resumes but they can only use one of them when they apply for a job.
Applying on a job on USAJOBS
Candidates log into the USAJOBS Web site, search for the job for which they want to apply, select a resume they created on the USAJOBS Web site and click the "Apply online!" button. Candidates are then redirected to a Career Section to complete the application process.
Option 1: If candidates have an account because they applied on the Career Section before, they can log in with their career section credentials and choose to import their USAJOBS profile information. When the candidates log in, their USAJOBS ID is linked to their existing Career Section candidate ID.
Option 2: If candidates have an account because they applied on the Career Section before, they can log in with their career section credentials and choose not to import their USAJOBS profile information. When candidates log in, their USAJOBS ID is linked to their existing Career Section candidate ID.
Option 3: If candidates do not have an account because they never applied on the Career Section, they are asked to create one. When candidates do that, their USAJOBS profile is automatically imported and the new account is linked to their USAJOBS ID.
Creating a new career section account
If candidates select option 3, they have to specify a user name and a password to log into the career section. From there, the standard candidate creation process takes place.
Importing candidate information from USAJOBS
Candidates' information is imported from USAJOBS. As a result, some fields in the application flow are filled automatically with information coming from the candidate USAJOBS general profile and resume. Resume information entered manually on USAJOBS is imported, not information contained in a file attachment. Also, imported information that is not part of the application flow is saved in the candidate file but the candidate will be unable to see it.
This table shows career section fields whose content may be imported from USAJOBS.
| Personal Information | Work Experience | References | Education |
|---|---|---|---|
| Address (Line 1) | Current Job | Email Address | City |
| Address (Line 2) | End Date | First Name | Education Level (Achieved) |
| Cellular Number | Other Employer | Last Name | GPA |
| City | Other Function | Middle Name | GPA out of |
| Email Address | Start Date | Organization | Graduation Date |
| Fax Number | Phone Number | Other Institution | |
| First Name | Title | Other Program | |
| Home Phone Number | Type | ||
| Job Type | |||
| Last Name | |||
| Middle Name | |||
| Place of Residence | |||
| Preferred Location | |||
| Shift Availability Grid | |||
| Work Phone Number | |||
| Zip/Postal Code |
Files attached to a candidate general profile in USAJOBS cannot be imported into a career section.
The Reference Name in a USAJOBS resume is imported into the Reference First Name field because USAJOBS does not use two separate fields as Oracle does.
Returning to USAJOBS
Once candidates have completed their job application, the Thank You page is displayed. Candidates can click a link on the page to return to the USAJOBS Web site. Customers might consider adding additional links back to the USAJOBS Web site on other career section pages (such as the My Submissions page). Candidates can monitor the status of their submissions by accessing the USAJOBS Application Status page. As candidates move through the various steps and statuses of the candidate selection workflow, status update notifications are sent to USAJOBS and the Application Status page displays up-to-date information.
Application Received: Set if candidates click the "Return to USAJOBS" link.
Application Status not Available: Set if candidates do not click the "Return to USAJOBS" link.
Once a candidate has accessed a career section through USAJOBS either by creating a new career section account or using an existing one, the USAJOBS account and the career section account are linked together. As a result, when updating an existing application or applying on a new job through USAJOBS, the candidate is automatically logged into the career section and does not need to provide a user name or password.
If candidates modify their USAJOBS profile and resume, they can re-import them before accessing their candidate submission. Once they log into the career section, the application flow is filled automatically with information coming from the updated candidate USAJOBS general profile and resume.
Sending Candidate Submission Status Updates to USAJOBS
This feature permits Recruiting to send candidate submission status updates to USAJOBS so that candidates are kept informed of the status of their submissions on the USAJOBS Web site.
Once candidates have applied through USAJOBS, they have access to an Application Status page on the USAJOBS Web site where they can view the status of their submissions. As candidates move through the various steps and statuses of the candidate selection workflow, status update notifications are sent to USAJOBS and the Application Status page displays up-to-date information.
It is possible to send status updates to USAJOBS based on the following events:
Submission Created: A status update is sent to USAJOBS the first time candidates click the Save and Continue button while creating a submission.
Submission Completed: A status update is sent to USAJOBS when candidates click the Submit button to complete their submission.
Submission Changes: A status update is sent to USAJOBS when candidates reach a specific workflow/step/status combination in Recruiting. When the bypass action is used to change a step/status, updates are not sent to USAJOBS even if the action was mapped to a USAJOBS status.
Once a status update has been sent to USAJOBS and the status is updated on USAJOBS, an event is added in the Recruiting Center, on the candidate file History tab. It may take a few minutes for the status update to be sent to USAJOBS and for the history event to be displayed.
Configuration
In the Status Update section of the Sourcing page, system administrators can view the list of current status mappings and invalid mappings (mappings for which the workflow, step or status no longer exists.), remove mappings and create new ones. When creating a status mapping, system administrators have to map Recruiting statuses to USAJOBS statuses. The configuration of the status mapping is done in the Candidate Sourcing module (Configuration > [Recruiting] Administration > [Integration] Candidate Sourcing).
| Announcement Cancelled (3423) | Ineligible - "Who May Apply" Requirements Not Met (9006) | Multiple Grades/Status/Agencies – Minimum Qualifications Requirements Not Met (11316) |
| Applicant Declined Appointment (11112) | Ineligible - Application Incomplete (9008) | Multiple Grades/Status/Agencies – Not Referred/Not Among the Top Candidates (11538) |
| Application Incomplete (3419) | Minimum Qualification Requirements Met (11312) | Multiple Grades/Status/Agencies – Not Selected (11319) |
| Application Received (3420) | Minimum Qualification Requirements Not Met (9007) | Multiple Grades/Status/Agencies – Selected (11320) |
| Application Status Not Available (11542) | Multiple Grades/Status/Agencies – Announcement Cancelled (11321) | Not Referred/Not Among the Top Candidates (11537) |
| Application Withdrawn (3417) | Multiple Grades/Status/Agencies – Applicant Declined Appointment (11322) | Not Selected (3425) |
| Eligible - Application Not Referred to Selecting Official (9005) | Multiple Grades/Status/Agencies – Eligible-Application Not Referred to Selecting Official (11313) | Resume Received (3418) |
| Eligible - Application Referred to Selecting Official (3422) | Multiple Grades/Status/Agencies – Eligible-Application Referred to Selecting Official (11314) | Reviewing Applications (9004) |
| Eligible – Referred for Structured Interview (11539) | Multiple Grades/Status/Agencies – Ineligible – Application Incomplete (11318) | Selected (3426) |
| Eligible – Referred to Next Step in Selection Process (11540) | Multiple Grades/Status/Agencies – Ineligible – "Who May Apply" Requirements Not Met (11315) | |
| Hired (11541) | Multiple Grades/Status/Agencies – Minimum Qualifications Requirements Met (11317) |
Configuring Candidate Information Import from USAJOBS
The configuration of the candidate information import from USAJOBS consists of the following steps.
Deploying the USAJOBS Certification. The system administrator, Oracle Support or Oracle Consulting Services performs this task in the Passport Console.
When configuring the career section to which candidates will be redirected when they apply on the USAJOBS Web site, the following option must be set to Yes: Allow new users to register in system (Configuration > [Career Section] Administration > Career Sections > click a career section > Sign In).
When configuring the career section, consider providing clear explanations (text) on the login page to inform candidates that they have been redirected to a career section and why they need to create an account. Also, since candidates have the opportunity to import information from USAJOBS, it is not necessary to include the Resume Upload block in the career section application flow for candidates coming from USAJOBS. If you decide to use the Resume Upload block, keep in mind that the information in this block will override information imported from USAJOBS.
Configuring USAJOBS Settings
The system administrator must obtain from USAJOBS the authentication token string used to authenticate transactions on USAJOBS portal and enable Oracle to connect to the USAJOBS Web services.
The system administrator must obtain from USAJOBS the target URL for the USAJOBS integration server.
Activating the USAJOBS Certification
The Access integration services configuration permission is required to access the Candidate Sourcing module (Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Administration).
Click the USAJOBS sourcing service.
Click Edit.
Enter values in the fields.
Click Save.
Mapping Statuses to USAJOBS Statuses
The Access integration services configuration permission is required.
Not all workflow/step/status combinations need to be mapped; only those for which updates need to be sent to USAJOBS.
Click the USAJOBS sourcing link.
Click Create next to Status Update.
Select the desired event type.
If you selected Submission Created or Submission Completed, select the desired USAJOBS status in the Action drop-down list.
If you selected Status Changed, select the desired workflow/step/status combination and map it to the desired USAJOBS status in the Action drop-down list.
Click Save.