Input 

Document

• Min: 0

• Max: 1

• Mapper

• Script

• Router

Each input document offers details associated with the data that must be posted to the target Oracle HCM instance.

Output

Document

• Min: 0

• Max: 1

• JSON Splitter

• JSON Formatter

• Join

Each output document contains details associated with the outcome of the Oracle HCM instance.If the Snap fails during the operation, it sends an error document to the error view containing the fields error, reason, resolution, and stacktrace. However, you must enable the Error view to view the error document.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter while running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:

• Stop Pipeline Execution: Stops the current pipeline execution when the Snap encounters an error.

• Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.

• Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Field Name

Label*

Default Value: Oracle HCM Delete
Example: Delete worker

String

Specify a unique name for the Snap.

Version*

Default Value: N/A
Example: 11.13.18.05

String/Expression/Suggestion

Specify the Oracle HCM instance version.

Resources name

Default Value: N/A
Example: workers

String/Expression

Specify the Oracle HCM resources (Tasks). The suggestion list (available resources) is populated based on the selected version. For example: absences, elementEntries, and workers.

Endpoint*

Default Value: N/A
Example: /workers

String/Expression/Suggestion

Specify the Oracle HCM endpoint. The suggestions are populated (available endpoints) based on the selected resource. For example if “worker” resource is selected, the suggestions that populate are:

• /workers

• /workers/{id}

• /workers/{id}/child/addresses/{id}

Entity

Default Value: $  
(the HTTP entity data is at the root of the input Map data)
Example: $.entity 
(if the HTTP entity data is the value of the "entity" key at the root of the input Map data)

String/Expression

Query parameters

Use this field set to add query parameters to your request.

Query parameter

Default Value: N/A
Example: id

String

The Specify the name of the query parameter.

Query parameter value

Default Value: N/A
Example: 

$widget.id

String/Expression

The Specify the value that you want to assign to the parameter.

Header parameters

Use this field set to set the HTTP header key-value pairs.

Header parameter

Default Value: N/A
Example: content-type

String

The Specify the name of the HTTP header.

Header parameter value

Default Value: N/A
Example: application/json

String/Expression

The Specify the value that you want to assign to the HTTP header.

Snap Execution

Default Value: Execute only
Example: Validate & Execute

StringDropdown list

Select one of the following three modes in which the Snap executes:

• Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.

• Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.

• Disabled: Disables the Snap and all Snaps that are downstream from it.