We use the CSV Generator Snap to supply CSV documents:

The raw output from the CSV Formatter Snap is as follows:

Notice how the double-quotes used in the first line of the input CSV data is escaped in the output document.

The CSV Formatter Snap formats the input data and produces an output in the line feeds for Windows style. We selected the Newline Property with CR+LF to give the line feeds in Windows format. We also leave the Quote character field unchanged as '"'. This tells the Snap that all special characters have to be placed in quotes in the CSV output.

We use the File Writer Snap to create a file using the output. Successful execution of the Pipeline displays the following output:

Download this Pipeline.

For the purposes of this example, we are picking up CSV data from a CSV Generator Snap. You can also supply this data using a combination of File Reader and CSV Parser Snaps.

The CSV Generator Snap contains transaction details, as shown below:

We copy the output of the CSV Generator Snap and connect each copy to a Filter Snap, where we filter out transactions based on whether they are worth more or less than $40:

We now add a 'Bill_Type' binary header property to each set of filtered outputs, so each document is tagged appropriately:

We now have two records, one containing all transactions that are worth less than or equal to $40, and another containing all transactions over $40. We now write each of these files to the SLDB using the File Writer Snap, configuring it to include this classification of transactions in the filename. We do this by using the expression $Bill_Type+".csv" in the File name property.

You can now see that two new files were created in the project: $Small.csv and $Large.csv:

Download this Pipeline.

For the example to work, the Pipeline triggered by the Task should lead to an error. We shall route the error output to an error view. We shall then use the error view to manipulate the Status header of the error document. Once this is done, the parent Task sends the updated error output back to ServiceNow, and we should see the updated status code in the ServiceNow Administration interface.

We need to perform the following tasks:

1. Create a Pipeline that accepts CSV data, generates an error, and manipulates the error data to update the status code.
2. Create a Triggered Task that can trigger the Pipeline created in Step 1.
3. Configure ServiceNow to send and receive CSV data from the Triggered Task created in Step 2.

Let us look at each of these tasks in some detail:

Creating a Pipeline to accept CSV and manipulate error document data

This Pipeline is structured as shown in the screenshot above. Let us now look at its constituents:

Creating a Triggered Task that sends CSV data into the TriggeredTask_CSVFormatter_Example Pipeline

To create a Triggered Task:

1. Click the  icon at the SnapLogic Designer toolbar. This displays the Create Task popup. Configure the Task as shown below:
   
   
   
   

Your Task is now configured. You now need to configure your ServiceNow account to send CSV data to this Task.

Configuring ServiceNow to send and receive CSV data from the Triggered Task

To configure ServiceNow to send and receive CSV data from the Triggered Task created in Step 2:

1. Log into your ServiceNow account and open the pane on the left of the page.
2. Search for the string outbound in the Filter field displayed in the top-left section of the page. From the filtered list of options displayed, click REST Messages under the System Web Services section.
   
   
   
   This displays the REST Messages page.
   
   

3. Click New to create a new REST message and configure the message as shown below:
   
   

   Note
   In the Endpoint field, paste the link to the Triggered Task we created in Step 2, above and append the bearer token associated with the Task.

   
   

   
   
   
4. Click Submit to save your changes. This creates the REST call. You now need to configure the call with the data you want to send. To do so, click the REST call. This displays the details of the REST call. 
   
   
   
   
5. Scroll down to the HTTP Methods section and click on the Default Get method created automatically for the call. This displays the call's details:
   
   
   
   
6. You need to send a POST call to the Task, so that you can provide the content that must be processed as a result of the call. To do so, click the HTTP Method field and, from the drop-down list displayed, select POST. Once you make this selection, the Content field appears at the bottom of the page. 
7. Enter the content you want to use for the call:
   
   
   
   
8. Click Test. This triggers the SnapLogic URL endpoint (This is the Task we created earlier in this example.) and displays the output of the Pipeline in the HTTP Status field: 603, as configured using the Mapper Snap, above.
   
   
   
   

You can similarly use the CSV Formatter Snap to update binary header values associated with any input document.

Download this Pipeline.