This document discusses recruitment and onboarding processes at Cameco, a uranium mining and production company, in the context of its unionized workforce. It provides an overview of Cameco's operations and employee demographics. It then outlines the company's goals in transitioning these processes to SuccessFactors and describes several issues encountered with existing union-specific processes. The document details solutions developed to address each issue and ensure the new system could support all collective agreements and bargaining units. It focuses on customizing the user experience, data, and workflows within SuccessFactors to align with union requirements while achieving adoption of the new technology.
Ask question of audience:
How many companies use a paper/manual process for union job bidding?
How many companies provide onboarding information prior to day 1?
Manually uploaded template resume to 800 candidate profiles (one time). Allows them to bypass resume requirement without turning off required field.
Candidate conversion brings external resume to internal profile removing the need to upload templates going forward.
Resume parsing required education and experience portlets to be enabled. This increased application time and effort required. It was more than our CBA allowed.
Phone number was the only additional required field for internals beyond what comes from SAP.
Fabian to Explain that the resume upload can now be done via ODATA API’s
Configuration selection to allow forwarding candidate profiles. Does cause some issues with custom fields not showing in candidate list view when application is not complete.
Explain other companies requirements first: Employees with no computer access and no email address, which means no intranet access either.
Explain solution requirements: Companies have Partial SSO turned on, Identify employees and load their login method to “password”. Load a dummy password or formulated password. Passwords are managed by HR service center.
Fabian to explain that
Automatic solution means the candidates are selected and hired based on business rules, if that’s what the collective agreement dictates.
Semi-automatic: Data and ranking brought up to the system for a Hiring Manager to make final decision.
Can be done though SFAPI / ODATA. /NSPRO has done with Adhoc reports via SFAPI/Odata with SAP (Using SAP middleware on premise PI).
HTML code to imbed logo in header
Direct link to careers section of SF still allows single sign-on
Explain Job Profile Builder Integration with Recruiting
Workflow configuration – Fabian?
Advanced conditions required fields from recruitment even if not used in forms
Parking passes condition (one of 4 northern sites, work contract reg-full-time, fly point Saskatoon)
Custom panels in Post Hire Verification step to collect flight and substance test appointments with notifications to book
Tags are viewable to only those permissioned
Can have more than one tag per person
Case sensitive
According to my applications analyst here are the technical components:
We used a mobile device management (MDM) system to deploy and manage the app
SAP Afaria was the system we used
The SF rollout strategy documents provide the manage app configuration keys (SFSF_domain, SFSF_instance)
We used a volume purchase plan deployment
Our authentication for single sign on is through ADFS and allowed us to skip the activate with bar code or PIN step
We modified our routing notifications for requisitions and offer approvals to include the deep links that when opened direct you to the mobile app when accessed from a mobile device. Our notifications gave you the choice to open in the app or in the browser so people were more aware that the app was an option
We selected the recipients through the MDM to allow us to only target employees with a company issued IOS device
Because it is a managed app all new devices will automatically receive the SF app with the link to the authentication
The first time they open the app they would use their regular computer credentials to sign in and after that the accounts would link and they could use their fingerprint or app password to access going forward
We also provided work instructions to employees to download to personal devices if they did not have a company issued device