​
System Requirements

The TechWolf skills integration will make use of existing Workday functionality. The customer will need a TechWolf contract with a live TechWolf tenant. This TechWolf tenant must be populated with (a subset of) the job’s entities in Workday.

​
Workday Configuration

A Workday integration user must be configured in the Workday tenant with an implementation security group. Requests will be sent over HTTPS using username/password authentication for the SOAP API.
This step can be skipped if there is already an Employee Skill Sync Integration configured. In this case, the same ISU can be used and only the Integration Permissions need to be updated in step 4.
  1. Create Integration System User (ISU)
    • Create Integration System User business process.
    • Do not allow UI sessions as this user will only be used for automations.
    • The username and password of this user must be shared with TechWolf as it will be used to access specific WWS endpoints.
    • Note: Make sure to share the secrets through a secure channel. Create Integration System User
  2. Update password expiration rules for ISU
    • In the Maintain Password Rules business process under “System Users exempt from password expiration” add the newly created ISU to the list.
    • Note: This ensures the integrations will keep running without interruptions due to password expiration. Maintain Password Rules
  3. Set up security permissions for the ISU through security policies
    • Go to Create Security Group, choose “Integration System Security Group”.
    • You can choose between “(Constrained)” or “(Unconstrained)”. For this integration, “(Unconstrained)” should be enough since job data is not really sensitive.
    • Note on acceptance testing: Consider using two different security groups, one Unconstrained and one Constrained. This way, the test-set is scoped while the correct permissions are applied for other Web Services. Create Security Group Create Security Group Detail
    • The next screen presents you with an Edit form to add additional information. Add your ISU to the list. This can be changed later too. Don’t check “Inactive”. Edit Security Group
  1. Edit the Security Group’s domain security policies
    • Search for “View Security Group” and select your created security group. View Security Group
    • Select the option menu next to the Security Group’s name, go to “Security Group” and select “Maintain Domain Permissions for Security Group”. View Security Group Action
    • Under Integration Permissions add the following Domain Security Policies, and run the Activate Pending Security Policy Changes task to apply the changes.
    Domain Security PolicyAccess
    Job InformationPut
    Manage: External SkillsPut
    Set up: Skills and ExperiencePut
    Integration Permissions
  1. Find out the correct Workday API URL
    • Search for Public Web Services in the search bar at the top of the Workday home page.
    • In the list, click the three dots next to the Human Resources (public) entry. select View WSDL under Web Service. View wsdl
    • The resulting page will take some time to load. Once it is loaded, look for “soapbind:address location” near the bottom of the page and copy the URL you find next to it.
    • Note that the API URL can differ between implementation tenants and production tenants, so the steps described above need to be repeated for each tenant individually.
When the Integration System User credentials and Workday API URL are shared, the setup is complete on the customer’s Workday tenant. TechWolf will validate that the ISU has the required permissions and that the API URL is correct.

​
TechWolf Configuration

The TechWolf tenant will be configured by TechWolf itself.
  1. In the integration service on the TechWolf side, TechWolf adds the credentials of the customer-created ISU.
  2. TechWolf adds TechWolf API credentials with correct scopes to have access to the TechWolf API and links that TechWolf tenant to a Workday tenant.
  3. In communication with the customer, TechWolf or the customer inserts Jobs into the TechWolf API, corresponding to the Workday Jobs to which the integration is scoped.

​
Linking Workday & TechWolf

This section is only required if the customer is NOT using the Workday ID as the API ID in TechWolf.

​
Seamless Matching of Job IDs

A critical aspect of this process is the seamless coupling of job IDs across both platforms: TechWolf (aligned with API IDs) and Workday (using Workday IDs). If this is not possible, the IDs should be linked through means of custom properties.

​
Creating Custom Properties

  • For each job in the TechWolf system, introduce a new custom property such as job_workday_id. This property will store the corresponding Workday ID of the job.
  • Detailed instructions for creating new custom property definitions can be found here .

​
Setting Custom Property Values

  • Once the custom property is defined, assign the Workday ID to each job’s TechWolf profile.
  • Steps for setting these values are outlined here .
During a pilot phase, it is possible to manually establish a link between TechWolf IDs and Workday IDs for each job. While this approach is feasible for a limited scope, it lacks scalability for broader deployment.

​
Deployment Methodology

The following tasks and responsibilities assume that:
  1. The customer has the appropriate TechWolf API license(s).
  2. The TechWolf API contains all job information corresponding to Workday jobs and data from other external systems.

​
Deployment Tasks & Responsibilities

  1. Customer: Create Integration System User (ISU) based on workflow described above.
  2. Customer: Share ISU credentials with TechWolf.
  3. Customer: Share Workday API URL with TechWolf.
  4. TechWolf: Run initial sync of job profiles with TechWolf API.
  5. TechWolf: Setup tenant configuration and start bidirectional sync process.
  6. Customer: Check end-user test scenarios.

​
Customer / User Acceptance Testing

Tests will be conducted on the production environment using a constrained Integration System Security Group. The Security Group should be constrained to the select number of jobs that will perform the user acceptance testing. An overview of the acceptance tests can be found in the “Test Scenarios” Excel - “Testing as an end-user” sheet. To promote the configuration to production, an unconstrained Integration System Security Group should be created and added to the ISU. This allows TechWolf to read and update all job skill profiles. User acceptance testing is done on the production or sandbox tenant, with a constrained security group.