Update a role

patch

/fscmRestApi/resources/11.13.18.05/compensationPlans/{CompensationPlanId}/child/CompensationPlanRoles/{CompensationPlanRolesUniqID}

Request

Path Parameters
  • The unique identifier of the compensation plan.
  • This is the hash key of the attributes which make up the composite key--- RolePlanId and CompensationPlanId ---for the Compensation Plan - Roles resource and used to uniquely identify an instance of Compensation Plan - Roles. The client should not generate the hash key value. Instead, the client should query on the Compensation Plan - Roles collection resource with a filter on the primary key values in order to navigate to a specific instance of Compensation Plan - Roles.

    For example: CompensationPlanRoles?q=RolePlanId=<value1>;CompensationPlanId=<value2>
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • The unique identifier for a compensation plan.
  • Title: End Date
    The date when the role assignment in a compensation plan becomes inactive. The acceptable format is yyyy-mm-dd. Once a date has been assigned, it cannot be updated to null.
  • Title: Start Date
    The date when the role assignment in a compensation plan becomes active. The acceptable format is yyyy-mm-dd.
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : compensationPlans-CompensationPlanRoles-item-response
Type: object
Show Source
Back to Top