In this article
...
Type | Format | Number of Views | Compatible Upstream and Downstream Snaps | Description |
---|---|---|---|---|
Input | Document |
|
| The resource details as a JSON document. |
Output | Document |
|
| Details of the updated resource record. Level of detail varies according to the configuration of the Response Type field. |
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. The available options are:
Learn more about Error handling in Pipelines. |
Snap Settings
Info |
---|
|
Field Name | Field Type | Description | ||
---|---|---|---|---|
Label* Default Value: Coupa Coupa Update | String | The name for the Snap. We recommend you update the Snap name, if there is more than one of the same Snap in your Pipeline. | ||
Response Type Default Value: all all | Dropdown list | Specify the level of detail required in the Snap's output. You can configure this keeping in mind the available memory and likely processing time that it would take to execute this Snap. Available options are:
See API Return Formats for more details | ||
API Path* Default Value: N/A | String/Expression | The API name associated with the target resource. Select the target resource from the suggestions in the field. Suggestions vary based on the account.
| ||
Mark Exported Default Value: Not selected | Checkbox | Select this checkbox to export the resource record after the update. This is only applicable to transactional resources such as contracts.
| ||
Snap execution Default Value: Execute only | Dropdown list | Select one of the three modes in which the Snap executes. Available options are:
|
...
Example
Fetching and Updating Inactive Records
...