Create a pay group role

post

/fscmRestApi/resources/11.13.18.05/incentiveCompensationPayGroups/{PayGroupId}/child/PayGroupRoles

Request

Path Parameters
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.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: End Date
    The date when the role assignment for a pay group becomes inactive. The acceptable format is yyyy-mm-dd. The date must be equal to or earlier than the pay group end date. The default value is the pay group end date.
  • The unique identifier of the pay group.
  • Title: Name
    The unique identifier of a pay group role.
  • The unique identifier of the role associated with a pay group.
  • Title: Start Date
    The date when the role assignment for a pay group becomes active. The acceptable format is yyyy-mm-dd. The date must be equal to or later than the pay group start date. The default value is the pay group start date.
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 : incentiveCompensationPayGroups-PayGroupRoles-item-response
Type: object
Show Source
Back to Top