Step 2: Create a population to synchronize with Workday

POST {{apiPath}}/environments/{{envID}}/populations

In Step 7: Create a Workday propagation rule, you must provide an expression that selects a population of users to synchronize from Workday. One method (the method used in this use case) selects all users that belong to a particular PingOne population, identified by its population UUID. While an existing PingOne population can be used, this use case creates the population for Step 7 in this step. Creating a population requires a password policy to apply to users in its population. While an existing PingOne password policy can be used, this use case creates the password policy for this step in Step 1: Create a password policy for the Workday population.

Use POST /environments/{{envID}}/populations/ to create a Workday population in the specified environment.

In the request body, the population name is a required property. The description property is optional.

Populations, by default, use the password policy of their environment. However, you can optionally assign a password policy specific to this population with the passwordPolicy.id property in the request body. To unassign the passwordPolicy.id property, omit passwordPolicy.id from the request body and the population again uses the default password policy.

See the Populations data model for full property descriptions.

Request Body

{"name"=>"Workday {{$timestamp}}", "description"=>"Population of users in Workday", "passwordPolicy"=>{"id"=>"{{wdPasswordPolicyID}}"}}

HEADERS