+2Hi Team,
The scenario: Nintex workflow generate PDF and API integration with POS Digicert, email to signer and then the completed signed PDF need to be downloaded from API Integration.
Issue: Tested with Postman - download binary or download Base64 both are working fine for result return. However in Nintex it comes as truncated?
Please advise any solution or alternative way to fix the case. Thanks.
Regards
Catherine
Best answer by Simon Muntz
Hi
The issue is the Xtension itself, not the way you are using it.
You may be better off creating your own Xtenstion that just downloads the file.
Another thing to consider with NWC tools is that you need to ask yourself, “Who owns this endpoint and is my data secure”? It sounds like you are downloading signed documents. Doesn’t sound like something I would like to be passing to an unknown source.
Here is a fixed version of the decode endpoint. The issue is that the file downloaded is called base64decodedfile.bin, and the only way to change the name would be to store the file in google drive and use Nintex's rename a file action to rename the file.
{
"swagger": "2.0",
"info": {
"title": "Definiti Tools",
"version": "1.0.0",
"description": "Decode Base64 and return file"
},
"host": "nwctools.azurewebsites.net",
"schemes": ["https"],
"x-ntx-render-version": 2,
"paths": {
"/api/v1.0/base64decodefile": {
"post": {
"summary": "Decode Base64 File",
"consumes": ["application/json"],
"produces": ["application/octet-stream"],
"parameters": [
{
"in": "body",
"name": "body",
"required": true,
"schema": {
"type": "object",
"properties": {
"content": {
"type": "string"
}
},
"required": ["content"]
}
}
],
"responses": {
"200": {
"description": "Binary file output",
"schema": {
"type": "file"
}
}
}
}
}
}
}
+23Hi
Welcome to the community.
It appears that you are downloading a base64 string.
You will need to do 1 of 2 things.
Firstly, you could try the Decode Base64 string action from the NWC toolkit Xtension from the Nintex Gallery. This will convert your string into a file and store it in a file variable.
https://gallery.nintex.com/t/toolkit-for-nwc
Or you could create your own Xtension that interacts with your API and downloads the file into a file variable.
https://help.nintex.com/en-US/xtensions/
The reason you see the return truncated is that the logging feature can only display a limited number of characters.
If you want to see larger outputs, I recommend putting the output into the body of an email and sending it to yourself.
+2Hi Simon,
I did try using decode Base64 string however it prompt the message as per screenshot. Please advise.
If is related access token it is working fine in Nintex no problem.
Thanks.
+23Hi
The issue is the Xtension itself, not the way you are using it.
You may be better off creating your own Xtenstion that just downloads the file.
Another thing to consider with NWC tools is that you need to ask yourself, “Who owns this endpoint and is my data secure”? It sounds like you are downloading signed documents. Doesn’t sound like something I would like to be passing to an unknown source.
Here is a fixed version of the decode endpoint. The issue is that the file downloaded is called base64decodedfile.bin, and the only way to change the name would be to store the file in google drive and use Nintex's rename a file action to rename the file.
{
"swagger": "2.0",
"info": {
"title": "Definiti Tools",
"version": "1.0.0",
"description": "Decode Base64 and return file"
},
"host": "nwctools.azurewebsites.net",
"schemes": ["https"],
"x-ntx-render-version": 2,
"paths": {
"/api/v1.0/base64decodefile": {
"post": {
"summary": "Decode Base64 File",
"consumes": ["application/json"],
"produces": ["application/octet-stream"],
"parameters": [
{
"in": "body",
"name": "body",
"required": true,
"schema": {
"type": "object",
"properties": {
"content": {
"type": "string"
}
},
"required": ["content"]
}
}
],
"responses": {
"200": {
"description": "Binary file output",
"schema": {
"type": "file"
}
}
}
}
}
}
}
+2Hi Simon,
Yes we are trying downloading the signed document from API integration and upload to Sharepoint via Nintex workflow - using web call service. Can advise solution for download binary or download as file?
Meanwhile, we will also trying from create xtension and continue testing.
Thanks.
+23Hi
If you are not worried about security, you could use the Xtension I posted above to output a file called base64decodedfile.bin, upload that to SharePoint and then use the SharePoint rename file action to rename the file.
I personally would try to use an Xtension that downloads the file directly from the API.
+2Hi Simon,
Thanks for the advise. We managed to use xtension to downloads files.
+23Hi
That is great news.
If you have time, could you please mark my response above as the correct answer?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.