Integration

Did not get your question clearly. Can you explain more about what are you trying to ask and what is the integration doing? 

When an integration is configured to convert a binary response body to an Appian document, this field specifies the document name and/or extension. It is recommended to provide an extension at design time in order to ensure its accuracy.

If this field contains period(s), the document extension will be set to everything after the last period and the document name will be set to everything before the last period. So profilePicture.jpg would set the document name to profilePicture and the extension to jpg.

If this field doesn’t contain a period, the document name will be set to the entire field value and Appian will try to infer an extension from the response using the Content-Disposition and Content-Type HTTP headers. So profilePicture would set the document name to profilePicture and the extension would be inferred.

Note: This field is only shown when Response Body Parsing is set to Convert binary to Appian document.

Actually, I would like to know if the input of the integration takes .PDF extension file and stores in certain folder in appian.Will the extension changes ??

When you upload a document in Appian and pass it to integration via Rule Input, then that is already stored on Appian inside a folder. Now when you pass it in a integration, it is not stored again rather it just used, And no, the extension does not changes. 

Appian automatically converts the document in base64 when passing it to the API. 

Thanks for the info puneets0004

We are getting a report in pdf format from external system. NOw using the option binary to appian document in the appian integration convert the pdf into what format?

It will stay a PDF document.