Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In this article

Table of Contents
maxLevel2
absoluteUrltrue

Overview

Use You can use the REST Delete Snap to delete business object resources using a REST API call.

Prerequisites

None.

Supported Features

Works in Ultra Task Pipelines. We recommend you to set the batch size to 1.

Limitations and Known Issues

None.

Snap Input and Output

Input/OutputType of ViewNumber of ViewsExamples of Upstream and Downstream SnapsDescription
Input Document
  • Min: 0
  • Max: 1
  • REST Get
  • Mapper
  • Script
Each input document contains the ID of the object to be deleted at the REST API service endpoint.
OutputDocument
  • Min: 0
  • Max: 1
  • REST Post
  • JSON Formatter
  • Mapper

Each output document contains response data from the REST API service endpoint detailing the status of the request.

Snap Settings

Parameter Name
Data Type
Field DependencyDescription
Default ValueExample 
Label*
String
N/A

Insert excerpt
File Writer
File Writer
nopaneltrue

N/ADelete Identified Objects

Default Value: REST Delete
ExampleREST Delete

Service URL

String
N/A

Multiexcerpt include macro
nameREST_Serviceurl
pageREST Get

Note

The Service URL for the REST snap has to be valid. If the Service URL contains any special characters, such as !, =, %21, $, and ^, the Snap throws an exception error. You can escape the special characters (using expression language) using one of the following methods:

We recommend you to use the former (encodeURIComponent) method to escape the special characters.

N

Default Value: N/A

"

Examplehttps://www.example.com/slm/webservice/v2.0/defect/%s".replace("%s", $.widget.id)

HTTP entity
String
N/A

Multiexcerpt include macro
nameHTTP_entity
pageREST Post

Default Value: N/A
Example$response.entity.id 

(if the HTTP entity that you want to delete is the value of the response.entity.id key in the input map.)

Batch size
Integer
N/A

Multiexcerpt include macro
nameBatch_Size
pageREST Patch

NN

Default Value: N/A
Example50

Show all headersCheckbox


Multiexcerpt macro
nameShow_All_Headers

The REST endpoint may return a response with multiple headers with the same header name.

  • If this property is deselected, only one response header will be shown in the output document.
  • If selected, the response header displays all the response header values received as a list of objects.

If any of these objects has a key-value format, it is parsed into the map data.

Deselected


Default Value: Deselected
Example: N/A

Trust all certificates
Check box
N/A

Multiexcerpt include macro
nameTrust_All_Certificates
pageREST Post

Default ValueDeselected

N

Example: N/A

Follow redirects
Check box
N/A

Multiexcerpt include macro
nameFollow_Redirects
pageREST Post

Default ValueSelected

N

Example: N/A

Query parameters
Fieldset

Multiexcerpt include macro
nameQuery_Parameters_REST
pageREST Post

Default Value: N/A
Example:

Query parameter

String
N/A

Specify the name (or key) of the query parameter.

N

Default Value: N/A
Exampleoauth2_access_token

Query parameter value

String
N/A

Specify the value associated with the query parameter.

N

Default Value: N/A
Example$account.access_token

HTTP header
Fieldset

Multiexcerpt include macro
nameHTTP_Header
pageREST Post

Multiexcerpt include macro
nameHTTP_Header
pageREST Post

Key

String
N/A

Specify the name that you want to use for the HTTP header.

N

Default Value: N/A
Example: User-Agent

Value

String
N/A

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

N

Default Value: N/A
ExampleSnapLogic

Response entity type
String
N/A

Multiexcerpt include macro
nameResponse_Entity_Type
pageREST Get

Default ValueDEFAULT
ExampleTEXT

Read timeout
Integer
N/A

Multiexcerpt include macro
nameRead_Timeout
pageREST Post

Default Value900
Example1500

Connection timeout
Integer
N/A

Multiexcerpt include macro
nameConnection_Timeout
pageREST Post

Default Value30
Example45

Maximum request attempts
Integer
N/A

Multiexcerpt include macro
nameMaximum_Request_Attempts
pageREST Post

Default Value5
Example3

Retry request interval
Integer
N/A

Multiexcerpt include macro
nameRetry_Request_Interval
pageREST Post

Default Value3
Example10

Snap Execution
String
N/A

Multiexcerpt include macro
nameExecution_Detail_Write
pageSOAP Execute

Default ValueValidate and Execute
ExampleExecute only

Troubleshooting

ErrorReasonResolution
Batch execution failedThe Pipeline ended before the batch could complete execution due to a connection error.

Verify that the Batch size field is configured to handle the inputs properly. If you are not sure when the input data is available, configure this field as zero to keep the connection always open.

The provided URI is invalidIllegal character in scheme namePlease verify Verify the provided URI and parameters that you provide are syntactically correct.
URL Parse Exception - 403The Service URL path might be containing any of the following special characters: !, =, %, #, $, ^&()_¢äâêîôûñç¡¿ÉÙËǨ°¸ðø©¢¾A+²½µ®§÷¶þ To escape the special characters, use the global function encodeURIComponent on any variables that might contain special characters so that they are encoded properly.

Examples

Creating and Deleting an Account in Salesforce Using REST Snaps

In this example , you create Pipeline, we demonstrate how we create an account in Salesforce and delete it using REST Snaps.

note

Image Added

To


Prerequisites: To use this example, you need at least an account in the free version of Salesforce. To create a Salesforce account, see Salesforce Developers.

You design the Pipeline as follows:
Image Removed
In the JSON Generator Snap, you

Initially, we configure the JSON Generator Snap—we enter a name

for the

Test Account—the account that you want to create.

In this example, you create an account called Test Account.


Image Modified

You


Then, we configure the REST Post Snap to create an account in your Salesforce instance using the account-name string of your choice. To do so:

  1. You We use the URL provided by Salesforce for managing the accounts available in your instance.
  2. You We use '$' in the HTTP entity field to specify indicate that you we want to use the string coming from the Snap upstream.
  3. You We add an HTTP header to the Snap, instructing Salesforce to read the document coming in as a JSON file.
    Image Modified
    You

We click the Account tab and select the account that

you

we want to use with the Snap.
Image Modified

You save your changes and close the Snap. When you


When we validate the Snap, it creates an account in

your

the Salesforce instance and displays the following output:

Image Modified

The id field lists out the unique identifier of the new account created by the Snap.

You


We now want to delete the account that you just created. To do so,

you

we need to isolate the account ID from the REST Post Snap's output.

You

We use a Mapper for this task.
Image Modified

Upon validation, the Mapper Snap

offers

displays the following output:
Image Modified

You


We now use the REST Delete Snap to delete the newly-created account

:

.
Image Modified

When the Snap is executed, the account is deleted.
Image Modified

Downloads

Attachments
patterns*.slp, *.zip

Insert excerpt
REST Snap Pack
REST Snap Pack
nopaneltrue