Compare with Oracle search
post
/hcmRestApi/resources/11.13.18.05/workerJourneys/{WorkerJourneyId}/action/compareWithOSCS
Compare database data with Oracle search.
Request
Path Parameters
-
WorkerJourneyId(required): integer(int64)
The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
Header Parameters
-
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.
Supported Media Types
- application/vnd.oracle.adf.action+json
Root Schema : schema
Type:
Show Source
object-
parameters: array
parameters
Parameters for comparing with Oracle search.
Nested Schema : parameters
Type:
arrayParameters for comparing with Oracle search.
Show Source
-
Array of:
object items
Additional Properties Allowed: additionalProperties
Response
Supported Media Types
- application/json
- application/vnd.oracle.adf.actionresult+json
Default Response
The following table describes the default response for this task.
Root Schema : schema
Type:
Show Source
object-
result(required): array
result
Response returned for compare query.
Nested Schema : result
Type:
arrayResponse returned for compare query.
Show Source
-
Array of:
object items
Additional Properties Allowed: additionalProperties