Get a position
get
/hcmRestApi/resources/11.13.18.05/positionsLovV2/{positionsLovV2UniqID}
Request
Path Parameters
-
positionsLovV2UniqID(required): string
This is the hash key of the attributes which make up the composite key--- PositionId, EffectiveStartDate and EffectiveEndDate ---for the Positions List of Values V2 resource and used to uniquely identify an instance of Positions List of Values V2. The client should not generate the hash key value. Instead, the client should query on the Positions List of Values V2 collection resource with a filter on the primary key values in order to navigate to a specific instance of Positions List of Values V2.
For example: positionsLovV2?q=PositionId=<value1>;EffectiveStartDate=<value2>;EffectiveEndDate=<value3>
Query Parameters
-
dependency: string
This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2
Format: <attr1>=<val1>,<attr2>=<value2> -
expand: string
When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
-
fields: string
This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.
Format: ?fields=Attribute1,Attribute2
Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2 -
links: string
This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>
Example:
self,canonical -
onlyData: boolean
The resource item payload will be filtered in order to contain only data (no links section, for example).
Header Parameters
-
Metadata-Context:
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".
-
REST-Framework-Version:
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.
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
Metadata-Context:
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".
-
REST-Framework-Version:
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.
Root Schema : positionsLovV2-item-response
Type:
Show Source
object
-
BusinessUnitName: string
Title:
Business Unit
Name of the business unit associated with the position. -
DepartmentName: string
Title:
Department
Name of the department associated with the position. -
DisplayName: string
Title:
Incumbent Name
Name of the incumbent associated with the position. -
EffectiveEndDate: string
(date)
Title:
Effective End Date
Date at the end of the period within which the position is effective. -
EffectiveStartDate: string
(date)
Title:
Effective Start Date
Date at the beginning of the period within which the position is effective. -
FullName: string
Title:
Incumbent Full Name
Full name of the incumbent associated with the position. -
HiringStatus: string
Title:
Hiring Status
Hiring status of the position such as proposed, frozen, or approved. -
JobCode: string
Title:
Job Code
Code of the job associated with the position. -
JobName: string
Title:
Job
Name of the job associated with the position. -
links: array
Links
Title:
Links
The link relations associated with the resource instance. -
LocationCode: string
Title:
Location Code
Unique code of the location associated with the position. -
LocationName: string
Title:
Location
Name of the location associated with the position. -
ParentPositionCode: string
Title:
Parent Position Code
Code of the parent position associated with the position. -
ParentPositionName: string
Title:
Parent Position
Name of the parent position associated with the position. -
PersonNumber: string
Title:
Person Number
Unique Identifier for the person. -
PositionCode: string
Title:
Code
Unique code for the position within the business unit. -
PositionId: integer
Title:
Position ID
Unique identifier for the position. -
PositionName: string
Title:
Name
Name of the position.
Nested Schema : Links
Type:
array
Title:
Links
The link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object
-
href: string
Title:
hyperlink reference
The URI to the related resource. -
kind: string
Title:
kind
Allowed Values:[ "collection", "item", "describe", "other" ]
The kind of the related resource. -
name: string
Title:
name
The name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relation
Allowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]
The name of the relation to the resource instance. Example: self.
Nested Schema : properties
Type:
Show Source
object
-
changeIndicator: string
Change indicator or the ETag value of the resource instance.