Get a visibility option
get
/hcmRestApi/resources/11.13.18.05/personNotesVisibilityOptions/{personNotesVisibilityOptionsUniqID}
Request
Path Parameters
-
personNotesVisibilityOptionsUniqID(required): string
This is the hash key of the attributes which make up the composite key for the Person Notes Visibility Option resource and used to uniquely identify an instance of Person Notes Visibility Option. The client should not generate the hash key value. Instead, the client should query on the Person Notes Visibility Option collection resource in order to navigate to a specific instance of Person Notes Visibility Option to get the hash key.
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 : personNotesVisibilityOptions-item-response
Type:
Show Source
object
-
ContextType: string
Title:
Context Type
Maximum Length:30
Type of context of person notes. Use the ORA_NO_CONTEXT value for person notes without context. -
CreatedBy: string
Read Only:
true
Maximum Length:64
User who created the visibility options for this context type. -
CreationDate: string
(date-time)
Read Only:
true
Date and time when the visibility options for this context type were created. -
LastUpdateDate: string
(date-time)
Read Only:
true
Date and time when the visibility options for this context type were last updated. -
LastUpdatedBy: string
Read Only:
true
Maximum Length:64
User who last updated the visibility options for this context type. -
links: array
Links
Title:
Links
The link relations associated with the resource instance. -
VisibleToAllFlag: boolean
Title:
Visible to All Indicator
Maximum Length:1
Default Value:false
Indicates whether the users can create person notes that will be visible to all users for this context type. The default value is false. -
VisibleToAuthorOnlyFlag: boolean
Title:
Visible to Author Only Indicator
Maximum Length:1
Default Value:false
Indicates whether users can create person notes that will be visible only to themselves for this context type. The default value is false. -
VisibleToManagersAndWorkerFlag: boolean
Title:
Visible to Managers and Worker Indicator
Maximum Length:1
Default Value:false
Indicates whether users can create person notes that will be visible to the managers of the worker and to the worker for this context type. The default value is false. -
VisibleToManagersOnlyFlag: boolean
Title:
Visible to Managers Only Indicator
Maximum Length:1
Default Value:false
Indicates whether users can create person notes that will be visible only to the managers of the worker for this context type. The default value is false. -
VisibleToManagersWorkerPeersFlag: boolean
Title:
Managers, Peers, and Worker Visibility Indicator
Maximum Length:1
Default Value:false
Indicates whether users can create person notes that will be visible to the worker, the managers of the worker, and the peers of the worker for this context type. The default value is false. -
VisibleToWorkerFlag: boolean
Title:
Visible to Worker and Author Indicator
Maximum Length:1
Default Value:false
Indicates whether users can create person notes that will be visible only to themselves and to the worker for this context type. The default value is false.
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.
Examples
The following example shows how to get a visibility option by submitting a singular GET request on the REST resource using cURL.
curl -i -u "<username>:<password>" -X GET "http://host:port/hcmCoreApi/resources/11.13.18.05/personNotesVisibilityOptions?q=ContextType='ORA_NO_CONTEXT'"
Example of Response Header
The following is an example of the response header.
HTTP/1.1 200 OK Content-Type : application/json
Example of Response Body
The following example shows the contents of the response body in JSON format.
{ "items": [ { "ContextType": "ORA_NO_CONTEXT", "VisibleToAllFlag": true, "VisibleToManagersOnlyFlag": true, "VisibleToManagersAndWorkerFlag": true, "VisibleToAuthorOnlyFlag": true, "VisibleToWorkerFlag": true, "CreatedBy": "-1", "CreationDate": "2018-02-13T22:25:44+00:00", "LastUpdatedBy": "TM-MFITZIMMONS", "LastUpdateDate": "2019-04-16T14:39:11.433+00:00", "links": [], "count": 1, "hasMore": false, "limit": 25, "offset": 0, "links": [] }