![]() It is mapped into the "text" field of the "WriteTextToFile" function. This field contains the entirety of file. Here we are mapping the "Content" field from the tree. Since there is no layout, the only output is the "ResponseInfo" section of the tree. This is crucial for some servers to not get an error back. We are, however, using the "Headers" section and we have mapped the constant */* into the value for Accept. The UrlParameters also appears, but it is being ignored in this case since we are not using parameters. It is only here to force the parent "Input" node to appear. In the example above, RestClient1 has been set up to Get a file The headers collection has a value of Accept. ![]() ![]() The benefit of this approach is that it can process files directly from the server and is closer in practice to how a local text file is processed. Another possibility would be to parse this text string using one of the text parsers available in the product. This would result in a copy of the file from the server and would be mostly suited as a step in a workflow. For example, it can be directly written to a text file using the "WriteToTextFile" function. This text string can then be processed as any other text value in Centerprise. This field contains the contents of the file as a text string. Instead, data would come from the "Content" field of the "ResponseInfo" object. In these cases, there would be no output layout since the file is not being parsed. A common usage would be to download the contents of a text file for further processing. The Centerprise REST Client can be used to download other data besides XML and JSON. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |