Update an element entry value
patch
/hcmRestApi/resources/11.13.18.05/elementEntries/{elementEntriesUniqID}/child/elementEntryValues/{elementEntryValuesUniqID}
Request
Path Parameters
-
elementEntriesUniqID(required): string
This is the hash key of the attributes which make up the composite key--- ElementEntryId, EffectiveStartDate and EffectiveEndDate ---for the Element Entries resource and used to uniquely identify an instance of Element Entries. The client should not generate the hash key value. Instead, the client should query on the Element Entries collection resource with a filter on the primary key values in order to navigate to a specific instance of Element Entries.
For example: elementEntries?q=ElementEntryId=<value1>;EffectiveStartDate=<value2>;EffectiveEndDate=<value3> -
elementEntryValuesUniqID(required): string
This is the hash key of the attributes which make up the composite key for the Element Entry Values resource and used to uniquely identify an instance of Element Entry Values. The client should not generate the hash key value. Instead, the client should query on the Element Entry Values collection resource in order to navigate to a specific instance of Element Entry Values to get the hash key.
Header Parameters
-
Effective-Of:
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. -
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.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object
-
InputValueId: integer
(int64)
Unique identifier for an input value.
-
InputValueName: string
Name of the element's input value.
-
LovScreenEntryValue: string
Maximum Length:
60
Entry values contained within a list of values. -
ScreenEntryValue: string
Maximum Length:
60
Entry for input values available for each entry of the element.
Response
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 : elementEntries-elementEntryValues-item-response
Type:
Show Source
object
-
BaseName: string
Title:
Name
Read Only:true
Maximum Length:80
Unique identifier for the payroll -
DefaultValue: string
Read Only:
true
Maximum Length:60
Default entry value for the element entry. -
DisplaySequence: integer
(int32)
Title:
Display Sequence
Read Only:true
Number assigned to an input value that determines the sequence in which the values appear. -
ElementEntryValueId: integer
(int64)
Unique identifier for an element entry value.
-
HotDefaultFlag: boolean
Title:
Apply default at run time
Read Only:true
Maximum Length:30
Indicates whether the existing entry values should be updated when the default value is updated. -
InputValueId: integer
(int64)
Unique identifier for an input value.
-
InputValueName: string
Name of the element's input value.
-
links: array
Links
Title:
Links
The link relations associated with the resource instance. -
LovScreenEntryValue: string
Maximum Length:
60
Entry values contained within a list of values. -
MandatoryFlag: boolean
Read Only:
true
Maximum Length:1
Indicates whether a value is required for the input. -
PAY_VALUE_SET_ValueSetScreenEntryValue_VALUE_SET_SWITCHER: string
Read Only:
true
-
ReservedInputValue: string
Title:
Special Purpose
Read Only:true
Maximum Length:30
Unique identifier for the payroll -
ScreenEntryDataURL: string
Read Only:
true
Maximum Length:255
Source location of the values contained within a list of values. -
ScreenEntryValue: string
Maximum Length:
60
Entry for input values available for each entry of the element. -
UOM: string
Read Only:
true
Maximum Length:30
Name of the type of measurement that's applicable to a number displayed in a balance, amount, or other type of numeric field such as money, character or number. -
UserEnterableFlag: boolean
Title:
Allow User Entry
Read Only:true
Maximum Length:1
Indicates whether the user can enter input values.
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 update an element entry value by submitting a PATCH request on the REST resource using cURL. In this example, the element entry has been corrected by specifying the range mode and the range start date.
curl -i -u "<username>:<password>" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -H "Effective-Of: RangeMode=CORRECTION;RangeStartDate=2020-07-25" -X PATCH -d <payload> https://<host>:<port>/hcmRestApi/resources/11.13.18.05/elementEntries/00020000000EACED00057708000110F09B3DA3500000004AACED00057372000D6A6176612E73716C2E4461746514FA46683F3566970200007872000E6A6176612E7574696C2E44617465686A81014B59741903000078707708000001798712640078/child/elementEntryValues/00020000000EACED00057708000110F09B3DA3520000004AACED00057372000D6A6176612E73716C2E4461746514FA46683F3566970200007872000E6A6176612E7574696C2E44617465686A81014B59741903000078707708000001798712640078
Example of Payload
The following is an example of the payload.
{ "ScreenEntryValue": 5000 }
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.
{ ScreenEntryValue: "5000" ElementEntryValueId: 300100559414098 InputValueId: 300100003068067 InputValueName: "Amount" "links": [ { ...} ] }