Get a hierarchy name
/hcmRestApi/resources/11.13.18.05/hcmTreesLOV/{hcmTreesLOVUniqID}
Request
-
hcmTreesLOVUniqID(required): string
This is the hash key of the attributes which make up the composite key for the HCM Trees List of Values resource and used to uniquely identify an instance of HCM Trees List of Values. The client should not generate the hash key value. Instead, the client should query on the HCM Trees List of Values collection resource in order to navigate to a specific instance of HCM Trees List of Values to get the hash key.
-
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).
-
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
- application/json
Default Response
-
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.
object
-
links: array
Links
Title:
Links
The link relations associated with the resource instance. -
TreeCode: string
Title:
Tree Code
Maximum Length:30
Code of the tree. -
TreeName: string
Title:
Tree Name
Maximum Length:80
Name of the hierarchy. -
TreeVersionId: string
Title:
Tree Version ID
Read Only:true
Maximum Length:32
Version identifier for the hierarchy.
array
Links
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.
object
-
changeIndicator: string
Change indicator or the ETag value of the resource instance.
Examples
The following examples show how to retrieve a hierarchy name by submitting a GET request on the REST resource using cURL.
Use a Query Parameter
In this example, the query parameter TreeVersionId
is used to retrieve
a hierarchy name. The following is an example of the cURL command.
curl -i -u "<username>:<password>" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -H "REST-Framework-Version: 4" -X GET "https://<host>:<port>/hcmRestApi/resources/11.13.18.05/hcmTreesLOV?q=TreeVersionId=D25C6EFCB0AC3BC3E0432620F00A2F97"
Example of Response Header
The following is an example of the response header.
Status: HTTP/1.1 200 OK Content-Type: application/vnd.oracle.adf.resourceitem+json
Example of Response Body
The following example shows the contents of the response body in JSON format.
{ "items": [ { "TreeVersionId": "D25C6EFCB0AC3BC3E0432620F00A2F97", "TreeName": "040113023250Position Tree 1", "links": [2] } ] }
Use a Finder
In this example, the finder findByWord
is used with the finder
variables SearchTerms
and FilterAttributes
to retrieve the
hierarchy names that match the specified criteria. The following is
an example of the cURL command.
curl -i -u "<username>:<password>" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -H "REST-Framework-Version: 4" -X GET "https://<host>:<port>/hcmRestApi/resources/11.13.18.05/?finder=findByWord;TreeStructureCode=PER_DEPT_TREE_STRUCTURE,SearchTerms=BI,FilterAttributes=TreeName"
Example of Response Header
The following is an example of the response header.
Status: HTTP/1.1 200 OK
Content-Type: application/vnd.oracle.adf.resourceitem+json
Example of Response Body
The following example shows the contents of the response body in JSON format.
{
"items": [
{
"TreeVersionId": "92179039384AFF46E04044987CF03CE5",
"TreeName": "BI_DEPT_HIERARCHY",
"links": [2]
},
{
""TreeVersionId": "FF39C3F13E245882E0435060F00A6656",
"TreeName": "BI_GEN_XFR_DEPT_TREE",
"links": [2]
},
{
"TreeVersionId": "B2D2D72D2AA63E68E040F00A50164EAE",
"TreeName": "zBIQA_DeptOrg_Tree1",
"links": [2]
}
]
}