Create all directly-assigned people for a specified responsibility template

post

/hcmRestApi/resources/11.13.18.05/areasOfResponsibilityTemplates/{TemplateId}/child/AssignedReps

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
Header Parameters
  • This header accepts a string value. The string is a semi-colon separated list of =. It is used to perform effective date range operations. The accepted parameters are RangeMode, RangeSpan, RangeStartDate, RangeEndDate, RangeStartSequence and RangeEndSequence. The parameter values are always strings. The possible values for RangeMode are SET_LOGICAL_START, SET_LOGICAL_END, END_DATE, SET_EFFECTIVE_START, SET_EFFECTIVE_END, REPLACE_CORRECTION, REPLACE_UPDATE, RECONCILE_CORRECTION, CORRECTION, RECONCILE_UPDATE, UPDATE, ZAP and DELETE_CHANGES. The possible values for RangeSpan are PHYSICAL_ROW_END_DATE and LOGICAL_ROW_END_DATE. The values for RangeStartDate and RangeEndDate have to be a string representation of a date in yyyy-MM-dd format. The value for RangeStartSequence and RangeEndSequence must be strings such that when parsed they yield positive integers.
  • 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: Area of Responsibility ID
    Surrogate identifier for the unique identifier for the area of responsibility. This is available only when updating an existing record.
  • Title: Assignment ID
    Unique identifier of the directly-assigned person's assignment assigned to the area of responsibility.
  • Title: Person ID
    Unique identifier of the person who's assigned to the responsibility in the directly-assigned section.
  • Title: Responsibility Name
    Maximum Length: 240
    Unique template responsibility name used to get the responsibility template's list of directly-assigned people.
  • Title: Template ID
    Unique identifier of the area of responsibility template.
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 : areasOfResponsibilityTemplates-AssignedReps-item-response
Type: object
Show Source
  • Title: Area of Responsibility ID
    Surrogate identifier for the unique identifier for the area of responsibility. This is available only when updating an existing record.
  • Title: Assignment ID
    Unique identifier of the directly-assigned person's assignment assigned to the area of responsibility.
  • Title: Assignment Name
    Read Only: true
    Maximum Length: 80
    Name of the directly-assigned person's assignment assigned to the area of responsibility.
  • Read Only: true
    Maximum Length: 64
    User who created the list of directly-assigned people in the responsibility template.
  • Read Only: true
    Date when the list of directly-assigned people in the responsibility template was created.
  • Links
  • Title: Name
    Read Only: true
    Maximum Length: 240
    Display name of the person listed in the directly-assigned section. Don't populate this attribute for POST (CREATE) action.
  • Title: Person ID
    Unique identifier of the person who's assigned to the responsibility in the directly-assigned section.
  • Title: Responsibility Name
    Maximum Length: 240
    Unique template responsibility name used to get the responsibility template's list of directly-assigned people.
  • Title: Template ID
    Unique identifier of the area of responsibility template.
Back to Top