Create a value criteria range
post
/hcmRestApi/resources/11.13.18.05/payLocalizationCriteriaDefinitions/{payLocalizationCriteriaDefinitionsUniqID}/child/ValueCriteriaConditions/{ValueCriteriaConditionsUniqID}/child/ValueCriteriaRanges
Request
Path Parameters
-
ValueCriteriaConditionsUniqID(required): string
This is the hash key of the attributes which make up the composite key--- LeafValueDefnId, EffectiveStartDate and EffectiveEndDate ---for the Values Defined by Criteria Conditions resource and used to uniquely identify an instance of Values Defined by Criteria Conditions. The client should not generate the hash key value. Instead, the client should query on the Values Defined by Criteria Conditions collection resource with a filter on the primary key values in order to navigate to a specific instance of Values Defined by Criteria Conditions.
For example: ValueCriteriaConditions?q=LeafValueDefnId=<value1>;EffectiveStartDate=<value2>;EffectiveEndDate=<value3> -
payLocalizationCriteriaDefinitionsUniqID(required): string
This is the hash key of the attributes which make up the composite key--- ValueDefnId, EffectiveStartDate and EffectiveEndDate ---for the Value Defined by Criteria Definition Root resource and used to uniquely identify an instance of Value Defined by Criteria Definition Root. The client should not generate the hash key value. Instead, the client should query on the Value Defined by Criteria Definition Root collection resource with a filter on the primary key values in order to navigate to a specific instance of Value Defined by Criteria Definition Root.
For example: payLocalizationCriteriaDefinitions?q=ValueDefnId=<value1>;EffectiveStartDate=<value2>;EffectiveEndDate=<value3>
Header Parameters
-
Effective-Of: string
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: string
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: string
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.
-
Upsert-Mode: string
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
- application/json
Root Schema : schema
Type:
Show Source
object-
EffectiveEndDate: string
(date)
Effective end date of the value criteria range.
-
EffectiveStartDate: string
(date)
Effective start date of the value criteria range.
-
HighValue: number
Upper bound of the range value.
-
LegislationCode: string
Maximum Length:
30Legislation code associated with the range. -
LegislativeDataGroupName: string
Maximum Length:
240Legislative data group name associated with the range. -
LowValue: number
Lower bound of the range value.
-
Name: string
Maximum Length:
120Name of the value criteria range. -
ParentValueDefnId: integer
(int64)
Parent value definition identifier for the range.
-
RangeDefId: integer
(int64)
Identifier of the range definition.
-
RangeEndDate: string
(date)
End date applicable for the range.
-
RangeMode: string
Mode indicating how the range is interpreted.
-
RangeStartDate: string
(date)
Start date applicable for the range.
-
ValueDefnId: integer
(int64)
Value definition identifier associated with the range.
-
ValueGroupName: string
Maximum Length:
120Value group name associated with the range. -
ValueOne: string
Maximum Length:
60Primary value associated with the range. -
ValueThree: string
Maximum Length:
60Tertiary value associated with the range. -
ValueTwo: string
Maximum Length:
60Secondary value associated with the range. -
VBCEffectiveDate: string
(date)
Value by criteria effective date for the range.
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 : payLocalizationCriteriaDefinitions-ValueCriteriaConditions-ValueCriteriaRanges-item-response
Type:
Show Source
object-
EffectiveEndDate: string
(date)
Effective end date of the value criteria range.
-
EffectiveStartDate: string
(date)
Effective start date of the value criteria range.
-
HighValue: number
Upper bound of the range value.
-
LegislationCode: string
Maximum Length:
30Legislation code associated with the range. -
LegislativeDataGroupName: string
Maximum Length:
240Legislative data group name associated with the range. -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
LowValue: number
Lower bound of the range value.
-
Name: string
Maximum Length:
120Name of the value criteria range. -
ParentValueDefnId: integer
(int64)
Parent value definition identifier for the range.
-
RangeDefId: integer
(int64)
Identifier of the range definition.
-
RangeEndDate: string
(date)
End date applicable for the range.
-
RangeMode: string
Mode indicating how the range is interpreted.
-
RangeStartDate: string
(date)
Start date applicable for the range.
-
ValueDefnId: integer
(int64)
Value definition identifier associated with the range.
-
ValueGroupName: string
Maximum Length:
120Value group name associated with the range. -
ValueOne: string
Maximum Length:
60Primary value associated with the range. -
ValueThree: string
Maximum Length:
60Tertiary value associated with the range. -
ValueTwo: string
Maximum Length:
60Secondary value associated with the range. -
VBCEffectiveDate: string
(date)
Value by criteria effective date for the range.
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object-
href: string
Title:
hyperlink referenceThe URI to the related resource. -
kind: string
Title:
kindAllowed Values:[ "collection", "item", "describe", "other" ]The kind of the related resource. -
name: string
Title:
nameThe name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relationAllowed 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.