| RSC-301 |
One-Click Export (New Candidate). Export a profile from LinkedIn Recruiter to a job requisition in your ATS. |
1. Demonstrate the candidate appears in the ATS as a candidate for the correct job and the exported candidates are tagged with LI as source in the ATS. 2. Understand which fields are being ingested through 1CE and how are they being displayed in ATS UI . 3. View Profile Widget within the ATS and ensure exact match displays. Relevant Documentation: Retreive Exported Candidates |
| RSC-302 |
Demonstrate or explain which fields are consumed from 1CE and which are consumed from mailstubs, and how they are stored and presented to customers. |
Fields consumed through 1CE and from mailStubs are clearly documented in customer facing documentation. LI understands field usage for 1CE and mailstubs. |
| RSC-303 |
Export update test (Existing Candidate). Edit the ATS record for the candidate exported in the prior step. Export the same candidate to a different job. |
1. Confirm the candidate is not duplicated. 2. Confirm the candidate is associated to both jobs. Relevant Documentation: Retreive Exported Candidates |
| RSC-304 |
Manual profile link test. 1.Add a candidate to the ATS which does not match a profile on LinkedIn by inventing a name and email address. 2. In the ATS Profile Plugin, manually link this new candidate to a complete LinkedIn profile. |
1. Refresh the page and ensure that the chosen LinkedIn profile is still displayed in the Profile Widget. 2. Ensure that the ATS candidate and LinkedIn profile mappings are updated. Relevant Documentation: Profile Plugin & Attach Person URN to Candidate |
| RSC-305 |
Login / logout test Logout of LinkedIn, display the candidate Profile Widget. |
1. Ensure Sign In to LinkedIn widget is displayed. Relevant Documentation: Profile Plugin |
| RSC-306 |
Login / logout test. Login to LinkedIn, display the candidate Profile Widget. |
1. Ensure that scrolling in the Enhanced ATS Profile Widget fits within ATS UI. Relevant Documentation: Profile Plugin |
| RSC-307 |
inMail history test. 1. As a recruiter, send an InMail to a LinkedIn member (1st Connection) from a Recruiter account. 2. As a candidate, (recipient of InMail) reply to InMail. 3. In ATS, display the InMail conversation. |
1. Call the LinkedIn REST API, ensure the pagination and timeRange.start / timeRange.end is used to get all results retrieving a history of received and sent InMails from Recruiter. 2. Ensure that the InMail appears in the results. 3. Ensure both public and private inMail messages are displayed in ATS. Relevant Documentation: Retrieve InMail History |
| RSC-308 |
Stub Profile Based On InMail Response Test. 1. As a recruiter, send an InMail to a LinkedIn member (1st connection not currently in ATS) on your team from a Recruiter. 2. As a candidate, (recipient of InMail) reply to InMail and share contact email. 3. Display new ATS candidate record. As a recruiter, send an InMail to same LinkedIn member. 4. As a candidate, (recipient of InMail) reply to InMail and share a different contact email and phone number. Display existing ATS candidate record has been updated. 5. Call the LinkedIn REST API, ensure the pagination is used to get all results of stub profiles. Ensure the values for all fields match, including: LinkedIn unique identifier, name, title, company, region, email address, and phone number (if applicable). |
1. Demonstrate the frequency to call stubProfile. If a new candidate - create a new record. (Ensure email fields can not be null, it should be valid email or empty when syncing candidate to LinkedIn). If an existing candidate - update an existing record if applicable. Relevant Documentation: Retrieve InMail Stub Profiles |
| RSC-309 |
Retrieve Seat Holders API. To retrieve contract seat holders, use the below API GET https://api.linkedin.com/v2/seatsV2?q=attributes&contracts=urn:li:contract:123456789&start=0&count=10 |
If you are implementing the above API, make sure to use the seatsV2 API along with pagination as explained above. Demonstrate the code snippet/screenshot of the codebase where above API is used to confirm that pagination and v2 api version is used. |
| RSC-310 |
Retrieve Closed Candidate Profiles. 1. Demo where customers will see or be notified of (and have the option to delete) any LinkedIn member profiles that were deleted from LinkedIn after the customer. 2. 1-Click Exported the relevant profile. Optional: Provide customers the option to delete 1-Click Exported LinkedIn member data globally or at member level (for example, LinkedIn Profile URL). |
Ensure that the list of deleted profiles displayed to the customer matches the list retrieved from LinkedIn. Ensure that any profiles deleted by the customer are removed from the ATS. Ensure the push notification sent by LinkedIn for closed profile is processed by your ATS system. Relevant Documentation: Retrieving Closed Candidate Profiles |
| RSC-311 |
Push Notification Handling. Demo how to handle different types of push notification. |
Ensure different types of push notification can be handled in your code. ( RSC push notification type includes EXPORT_CANDIDATE_PROFILE, INTEGRATION_STATUS_CHANGE). Relevant Documentation: Receive Push Events |