SimpleVMS mappings within BOLD are essential for ensuring jobs, contacts, and skills are aligned between the two platforms. Follow this article to complete the SimpleVMS Mapping Setup.
Chapters:
- Locating SimpleVMS Settings
- Company Mapping
- Contact Status Mapping
- Job Skill Mapping
- Job Type Mapping
- Job Status Mapping
- Placement End Reason Mapping
Locating SimpleVMS Settings
- Click Account & Settings, then Utilities
- Type 'SimpleVMS' in the search bar and click on the SimpleVMS Settings Utility
Company Mapping
Buyers mapped to the staffing agency vendor record in SimpleVMS will be displayed in the Company Mapping screen. There are two approaches to mapping SimpleVMS companies to receive jobs in BOLD:
- Direct Company Mapping: Map the VMS company directly to a BOLD company
- Worksite-Only Mapping: Use "Map by Worksite" without mapping the parent VMS company
If needed, you can create a new BOLD company from this screen.
Default Job Owners must be configured for each mapped BOLD company.
Map by Worksite: This feature allows mapping individual worksites to different BOLD companies, and can be used in two ways:
- With mapped parent company: When a VMS company is mapped to a BOLD company, worksites can be mapped to different BOLD companies for multi-regional employers. Jobs from unmapped worksites will be created under the parent company's mapped BOLD company.
- Without a mapped parent company: Worksites can be mapped directly to BOLD companies without mapping the parent VMS company. Jobs will only be created for mapped worksites - jobs from unmapped worksites will not be created in BOLD.
Manually Create Placements: Checking “Manually Create Placements” - The nomination stage in BOLD is updated to 'Hired' and the user is able to manually place the talent in BOLD. Leaving unchecked - The nomination stage in BOLD is updated to 'Hired', and the talent is automatically placed.
Job Template Override: This allows job details to be overridden based on templates when jobs are created. Job templates at the company level with exact name matching to the job title will use the template details instead of the job posting from SimpleVMS.
Contact Status Mapping
Each SimpleVMS manager status must be mapped to a BOLD contact status.
Job Skill Mapping
Each SimpleVMS job skill must be mapped to a BOLD skill code.
When a new SimpleVMS job is created in BOLD, the BOLD job will then have the mapped skill codes based on the job skill mapping configuration. This is vital for the purposes of job matching and distribution through 24/7.
Job Type Mapping
Each SimpleVMS job type must be mapped to a BOLD job type.
Job Status Mapping
Each SimpleVMS job status must be mapped to a BOLD job status.
Placement End Reason Mapping
Each SimpleVMS worker end reason must be mapped to a BOLD placement end reason.
- You add a new BOLD placement end reason and would like to change your SimpleVMS placement end reason mapping
- A newly mapped SimpleVMS buyer has custom worker end reasons configured in SimpleVMS
Comments
0 commentsPlease sign in to leave a comment.