This guide describes the configuration steps to deploy Interviews for Workday Integration.
Prerequisites:
- You must have the Workday Recruiting Module enabled and in scope.
- ‘Interview (Default Definition)’ business process must exist in the tenant.
- Search for ‘bp: Interview’ to check if this exists in the tenant already.
- If not, set up and configure the ‘Interview (Default Definition)’ Business Process in your Workday tenant using the ‘Create Business Process Definition (Default Definition)’ task. Refer to the Workday Community guide. Also, you can refer to additional documentation.
- Download and Install Workday Studio on your computer. For more information, refer to the Installation Guide.
Configure the Workday Studio
Configuring the Workday Studio involves a series of steps:
- Import the CLAR File into Workday Studio
- Add a Connection in Workday
- Deploy the CLAR File to Workday Tenant Using Workday Studio
Import the CLAR File into Workday Studio
-
- On the Studio menu bar, select File -> Import.
- Select the CLAR file import wizard in the Workday folder. You can find the CLAR file at this link.
- Click Browse and select a CLAR file to import.
- Click Next to display the collections and projects in the CLAR file.
- Select collections and projects to import from the CLAR file.
- Edit all project name conflicts if applicable.
- Select a project with a name conflict.
- Click Edit.
- In the Project Name field, rename the project.
- Edit all collection name conflicts if applicable.
- Select a collection with a name conflict.
- Click Edit.
- In the Collection Name field, rename the collection.
- Click Finish.
Add a Connection in Workday
-
- Select Window -> Preferences -> Workday -> Connections. If this is not accessible, you can do the following: Go to Window -> Show View -> Cloud Explorer. Click the icon in the upper left corner of the Cloud Explorer box to open Connection Details.
-
- Click Add.
- On the Add Connection window, consider:
- Option Description
- Name The name of the connection.
- URL The URL of the connection. - https://workdayinc.force.com/partnercenter/apex/PartnerPortalKnowledge?id=kA04X000001DXF4SAO
- Group Adds the connection to a group. (Optional)
-
- In the Credentials section, specify the Tenant and select an authentication method, Basic Auth, or OAuth 2.0.
-
- To use OAuth 2.0 authorization, you must first register an API client. For more information, see the Workday Community Article.
Option Description Basic Auth Specify the Username and Password for the connection. OAuth 2.0 Specify these details for the connection: - Grant Type
- Client ID
- Authorization Endpoint
- Token Endpoint
- Access Token
- To use OAuth 2.0 authorization, you must first register an API client. For more information, see the Workday Community Article.
-
- In the Credentials section, specify the Tenant and select an authentication method, Basic Auth, or OAuth 2.0.
- Click Test Connection.
- The Studio confirms whether it can access the connection.
- The user needs to have certain permissions to deploy. Refer to the list in Workday Studio to ensure the user is a part of at least one of the security groups for each section needed to deploy the CLAR to the tenant. For more information, see the Workday Article for User-Based Security Groups.
Deploy the CLAR File to Workday Tenant Using Workday Studio
-
- Deploy CLAR to Workday Tenant by right-clicking on the project in Workday Studio and clicking Deploy to Workday.
- Select the Workday environment you wish to deploy the CLAR file. Make sure the option Include source code in deployed CLAR is selected.
- Click Next.
- Make sure your project is under the Configured section.
- Click Finish.
Configure the Workday Tenant
Prerequisite
You will need access to the domain ‘Security: Security Configuration’ to perform the following steps.
Create and Configure Access for an Integration System User (ISU) Account
Note: If you are unable to perform these steps, then update the security fields accordingly. If you are not able to access a specific task or report that is a part of this guide, use the View Security for Securable Item report to review the domains required for that task or report and the security groups.
-
Integration System User Configuration:
-
- Access the Create Integration System User task and configure a Workday account for the integration.
- Name the account as “HackerRank_Interview_Integration_User_Step1”.
- Specify a password and save credentials somewhere for future use.
- Keep the Session Timeout Minutes to the default value of zero to prevent session expiration. An expired session can cause the integration to stop before it completes.
- Select Do Not Allow UI Sessions. This option prevents the integration system user from signing in to Workday through the UI.
Follow the above steps and create an additional Integration System User named ‘HackerRank_Interview_Integration_User_Step2’.
-
-
Create Integration System Security Groups (Unconstrained).
-
- Access the ‘Create Security Group’ task and configure an Integration System Security Group for the integration.
- Select the type of ‘Integration System Security Group (Unconstrained)’
- Name the group as “ISSG_HackerRank_Interview_Integration.
- Select the ISUs you created in Step A in the Integration System User box.
- Click OK to save.
-
-
Edit the Domain Security Policies.
-
-
-
-
To grant the security group access to the domains required by your integration, follow these steps for each domain:
-
-
-
-
Domains Required:
- Interview Integrations
- Candidate Data: Interview Schedule
- Candidate Date: Interview Feedback Results
- Worker Data: Public Worker Reports
- Person Data: Work Contact Information
- Access the View Domain report from the search bar and find the domain.
- As a related action on the domain, select Domain > Edit Security Policy Permissions.
-
Domains Required:
-
-
-
- Add the security group you created to the Report or Task Permissions and Integration Permissions. Select Get, Put, View, and/or Modify based on the table in the following step.
-
To grant the security group access to the domains required by your integration, follow these steps for each domain:
-
-
-
- Activate Pending Security Policy Changes.
- Access the Activate Pending Security Policy Changes task.
- Describe your changes in the Comment field.
- Select the Confirm checkbox to activate your changes.
-
-
Access the Maintain Password Rules task. Add the integration system users to the System Users exempt from the password expiration field.
Note: To avoid integration errors caused by expired passwords, Workday recommends that you prevent Workday passwords from expiring. -
Assign ISU to the Integration System.
-
- Search for ‘intsys: Hackerrank_Interview_Integration_Step2” and click into the Integration System.
- Using the Related Actions off of the integration, navigate to Workday Account -> Edit.
- Select your ISU named ‘HackerRank_Interview_Integration_User_Step2’.
- Repeat these steps for adding the other ISU for ‘Hackerrank_Interview_Integration_Step1’ Integration System.
-
-
Manage Authentication Policies for API Access
- Navigate to ‘Manage Authentication Policies’.
- Edit the authentication policy for the environment that you are currently working in.
- Create a new Authentication Ruleset using the Plus icon in the top left corner.
- Provide a Rule Name.
- Select your Integration System Security Group created above under ‘Security Group.’
- Enter a value for ‘Authentication condition name.’
- Choose ‘User Name Password’ for the ‘Allowed Authentication Types’ section.
- Click OK.
- Navigate to ‘Activate All Pending Authentication Policy Changes’ to activate your changes.
Note: If this is not set up correctly, it might result in issues with HackerRank making web service calls back to Workday. If there are issues with authentication, use the ‘Signons and Attempted Signons’ report to troubleshoot the failed sign-on attempt.
Add HackerRank-specific Fields to the Integration
Note: Refer to the Configure the HackerRank Settings section below in the document and complete the setup in HackerRank to retrieve the access_token and Company ID needed in the following steps.
- Search for the integration in the tenant by searching ‘intsys: HackerRank_Interview_Integration_Step2’ in the search bar.
-
-
- Add the ‘Access Token’ provided by HackerRank to the ‘Access Token.’ Integration Attribute using the Related Actions of the Integration System (Integration System -> Configure Integration Attributes).
- Add the ‘Company ID’ provided by HackerRank to the ‘Company ID’ Integration Attribute using the Related Actions off the Hackerrank_Interview_Integration_Step2 integration system and doing Integration System -> Configure Integration Attributes.
-
-
Access the Register External OAuth Client task.
- Navigate to the ‘Register External Oauth Client’ task.
- Find and select your integration system named ‘Hackerrank_Interview_Integration_Step1’.
- Enter these values provided by your HackerRank contact:
- OAuth 2.0 Client Name
- OAuth 2.0 Client ID
- OAuth 2.0 Client Secret
- Scope
- Authorize Endpoint URL
- Token Endpoint URL
- Click OK to save.
Navigate to the Edit Tenant Setup - Recruiting Task
- Select the integration system named ‘Hackerrank_Interview_Integration_Step1’ from the Web Conference Integration System prompt and save.
Build Calculated Fields
Build out the following calculated fields using the Create Calculated Field task using the following screenshots:
-
-
Field Name: CFI LRV Candidate from Interview
- Function: Lookup Related Value
- Business Object: Interview
- Lookup Field: Job Application
- Return Value: Candidate – Field Type: Self-referencing instance (Viewable from the Related Actions off of the field)
-
Field Name: CFI LRV Candidate from Interview
-
Field Name: CFI LRV Candidate Email for Candidate from Interview
- Function: Lookup Related Value
- Business Object: Interview
- Lookup Field: CFI LRV Candidate from Interview
- Return Value: Email
-
Field Name: CFI LRV Recruiter for Interview
- Function: Lookup Related Value
- Business Object: Interview
- Lookup Field: Job Application
- Return Value: Recruiter
-
Field Name: CFI LRV Recruiter Email for Interview
- Function: Lookup Related Value
- Business Object: Interview
- Lookup Field: CFI LRV Recruiter for Interview
- Return Value: Email - Primary Work
Business Process Configuration
Note: Workday recommends the following setup and has been tested for the integration to work. We recommend keeping all the steps mentioned below in the specified order. If you have additional steps in your setup, make sure first to test if the integration works for your setup.
- Search for ‘bp:interview’.
- Click into your ‘Interview (Default Definition).’
- Edit the business process definition using the Related Actions and navigating to Business Process -> Edit Definition. Click OK.
-
Set up Schedule Interview Step:
- Add a new step using the Plus icon in the top left corner.
- Type a letter for ‘Order’ that places the Schedule Interview step after the ‘Initiation’ step.
- Select ‘Action’ in the ‘Type’ column.
- Select Schedule Interview in the Specify column.
- Choose a security group for the Group column that should handle the ‘Schedule Interview’ step.
- (Optional) Populate the Due Date column.
-
Set up Integration Step:
- Add a new step using the Plus icon in the top left corner.
- Type a letter for ‘Order’ that places the Integration step after the Schedule Interview action step. For example, if the ‘Schedule Interview’ step is Order b, make the Integration step Order c.
- Select Integration’ in the Type column. Click OK.
- Hover over the magnifying glass for the Integration step and click Related Actions. Navigate to Business Process -> Maintain Redirect. Click OK. Select the Move to Next Step and Rerun and Integration check boxes and select the allowed security groups for the redirect.
-
Note: If there are no security groups in the drop-down, click Related Actions off the Business Process Definition and navigate to Business Process Policy - Edit. Add the desired security groups in the Redirect Action box.
-
- For the step that you just created, click Configure.
- Select your integration system (Integration System Name: Hackerrank_Interview_Integration_Step2) and Click OK.
- Configure the Integration Criteria as follows:
-
Set up Manage Interview Feedback:
- Add a new step using the Plus icon in the top left corner.
- Type a letter for ‘Order’ that places the ‘Manage Interview Feedback’ step after the ‘Integration’ step.
- Choose Shared Participation from the Type column drop-down.
- Choose Manage Interview Feedback from the Specify column.
- Choose the appropriate security group(s) under the Group column.
-
Set up Make Interview Decision Step:
- Add a new step using the Plus icon in the top left corner.
- Type a letter for ‘Order’ that places the ‘Make Interview Decision’ step after the ‘Manage Interview Feedback’ step.
- Choose Action from the Type column drop-down.
- Choose Make Interview Decision from the Specify column.
- Choose the appropriate security group(s) under the Group column.
- (Optional) Populate the Due Date column.
- Click OK to save.
- Hover over the magnifying glass for the ‘Make Interview Decision’ step and click on the Related Actions. Go to Business Process -> Set and set as Completion.
- Click OK.
Configure the HackerRank Settings Page
- Use any one of the Integration System User's Username you have created.
- Use the Corresponding Integration System User Password.
- Specify the Recruiting Public Web Services Endpoint:
Search for the ‘Public Web Services’ report in your Workday tenant. Navigate to the Recruiting (Public) Web Service. Click on the Related Actions next to it and navigate to Web Service -> View WSDL. Search for ‘soapbind:address’ in the WSDL. - Enter the Interview Rating IDs from Workday that should map to ‘Pass’ and ‘Fail’ on the HackerRank Side.
- The ‘Maintain Interview Feedback Ratings’ task can be used to configure the ratings initially. After setting up initially, the task can be used to update the feedback descriptions only.
- Navigate to the ‘Maintain Reference IDs’ task to update or view the reference IDs for the ‘Interview Feedback Rating’ business object.
Note: If you move tenants, provide updated credentials to the HackerRank team.