In this article
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.
Input/Output | Type of View | Number of Views | Examples of Upstream and Downstream Snaps | Description |
---|
Input | Document | | | Each input document contains the ID of the object to be deleted at the REST API service endpoint. |
Output | Document | | - 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
Data TypeField Dependency | Description |
---|
Default Value | Example StringN/A | Insert excerpt |
---|
| File Writer |
---|
| File Writer |
---|
nopanel | true |
---|
|
|
N/A | Delete Identified ObjectsDefault Value: REST Delete Example: REST Delete |
Service URL |
StringN/A | Multiexcerpt include macro |
---|
name | REST_Serviceurl |
---|
page | REST 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"Example: https://www.example.com/slm/webservice/v2.0/defect/%s".replace("%s", $.widget.id) |
HTTP entity |
StringN/A | Multiexcerpt include macro |
---|
name | HTTP_entity |
---|
page | REST 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.)IntegerN/A | Multiexcerpt include macro |
---|
name | Batch_Size |
---|
page | REST Patch |
---|
|
|
NNDefault Value: N/A Example: 50 |
Show all headers | Checkbox |
Multiexcerpt macro |
---|
| 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 boxN/A | Multiexcerpt include macro |
---|
name | Trust_All_Certificates |
---|
page | REST Post |
---|
|
Default Value: Deselected
|
NExample: N/A |
Follow redirects |
Check boxN/A | Multiexcerpt include macro |
---|
name | Follow_Redirects |
---|
page | REST Post |
---|
|
Default Value: Selected
|
NExample: N/A |
Query parameters |
Fieldset | Multiexcerpt include macro |
---|
name | Query_Parameters_REST |
---|
page | REST Post |
---|
|
Default Value: N/A Example: |
Query parameter |
StringN/A | Specify the name (or key) of the query parameter. |
NDefault Value: N/A Example: oauth2_access_token |
Query parameter value |
StringN/A | Specify the value associated with the query parameter. |
NDefault Value: N/A Example: $account.access_token |
HTTP header |
Fieldset |
Multiexcerpt include macro |
---|
name | HTTP_Header |
---|
page | REST Post |
---|
|
Multiexcerpt include macro |
---|
name | HTTP_Header |
---|
page | REST Post |
---|
|
|
Key |
StringN/A | Specify the name that you want to use for the HTTP header. |
NDefault Value: N/A Example: User-Agent |
Value |
StringN/A | Specify the value that you want to assign to the HTTP header. |
NDefault Value: N/A Example: SnapLogic |
Response entity type |
StringN/A | Multiexcerpt include macro |
---|
name | Response_Entity_Type |
---|
page | REST Get |
---|
|
Default Value: DEFAULT Example: TEXT |
Read timeout |
IntegerN/A | Multiexcerpt include macro |
---|
name | Read_Timeout |
---|
page | REST Post |
---|
|
Default Value: 900 Example: 1500 |
Connection timeout |
IntegerN/A | Multiexcerpt include macro |
---|
name | Connection_Timeout |
---|
page | REST Post |
---|
|
Default Value: 30 Example: 45 |
Maximum request attempts |
IntegerN/A | Multiexcerpt include macro |
---|
name | Maximum_Request_Attempts |
---|
page | REST Post |
---|
|
Default Value: 5 Example: 3 |
Retry request interval |
IntegerN/A | Multiexcerpt include macro |
---|
name | Retry_Request_Interval |
---|
page | REST Post |
---|
|
Default Value: 3 Example: 10 |
Snap Execution |
StringN/A | Multiexcerpt include macro |
---|
name | Execution_Detail_Write |
---|
page | SOAP Execute |
---|
|
Default Value: Validate and Execute Example: Execute only |
Troubleshooting
Error | Reason | Resolution |
---|
Batch execution failed | The 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 invalid | Illegal character in scheme name | Please verify Verify the provided URI and parameters that you provide are syntactically correct. |
URL Parse Exception - 403 | The 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.
noteImage 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 RemovedIn 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:
- You We use the URL provided by Salesforce for managing the accounts available in your instance.
- You We use '$' in the HTTP entity field to specify indicate that you we want to use the string coming from the Snap upstream.
- 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
Insert excerpt |
---|
| REST Snap Pack |
---|
| REST Snap Pack |
---|
nopanel | true |
---|
|