Update Employee Skill
PUT {{base_url}}/employee/:Employee/skills/:Skill
Use this endpoint to update a skill entry for an employee in the Employees hub. Specify the new data for the skill entry in the request body. In this example, we can update the skill level for the specified employee and skill entry.
- Obtain valid values from the GET {{base_url}}/codeTable/{{codeTable}} using CFGEMSkill, CFGEMSkillLevel, or CFGEMSkillUsage to obtain the code value for the codeTable you want to use.
- Check the employee metadata for details of the field names
Skill
,SkillLevel
, andSkillUsage
.
For example, here is a request to update a skill entry for the employee
with ID equal to EMPLOYEE1234567889 and via skill
set to 32
.
curl --request POST \
--url 'https://{{base_url}}/employee/EMPLOYEE1234567889/skills/32' \
--header 'authorization: Bearer {{oauth_token}}' \
--header 'content-type: application/json' \
--data '
{
"SkillLevel": "5"
}'
Request Params
Key | Datatype | Required | Description |
---|---|---|---|
requiredFieldValidation | string | Optional. |
The flag that indicates whether or not the validation for required screen designer fields is needed.
Use "N" if you want to bypass the validation. Otherwise, the default is "Y," which enforces the validation.
NOTE: This does not apply to required system fields. |
| startWorkflow
| string | | Optional.
The flag that indicates whether or not the trigger for a workflow is initiated.
Use "N" if you want to bypass the trigger. Otherwise, the default is "Y," which initiates the workflow. |
HEADERS
Key | Datatype | Required | Description |
---|---|---|---|
Content-Type | string | Required. |
The type of content supported by the API endpoint. |
| Authorization
| string | | Required.
The type of authorization supported by the API endpoint. |
RESPONSES
status: OK
[{"Employee":"EMPLOYEE1234567889","Skill":"32","SkillDescription":"Structural Engineers","SkillLevel":5,"SkillLevelDescription":"Over Ten Years","SkillUsage":0,"SkillUsageDescription":"","PrimaryInd":"N"}]