I want to know how to implement "Convert base64 values to Appian documents" without using an integration object.
I have implemented a process that retrieves attachment information from an external database via HTTP connection and converts it into an Appian document.The process is as follows:
1. On the interface, execute an API request (an integration object) without "Convert base64 values to Appian documents", obtain information on 10 attachments, and store it in "local!fileList."
2. Perform a check: "If any of attachments 1 to 10 is not null, then the result is true; if it is null, then the result is false" and store the result in "local!notNullFile".
3. Press the "Get File (ファイル取得)" button. If the 10 file information items are judged to be false in "2.", nothing will be done. Only if the result is true will an API request be made with "Convert base64 values to Appian documents" enabled.
4. When the request in "3." is made, an API request is made again within the integration without "Convert base64 values to Appian documents". Using the file name and extension information obtained, the file is converted to an Appian document and stored in "local!file1" (to "local!file10") in the interface.
5. Display as a file download link on the interface.
In the current process, attachment information is obtained once in "1.", but then obtained again in "4.".Because the information obtained on the interface cannot be used in an integrated manner, it is difficult to reuse the information in "1." in "4.", so it is unavoidable that the file information is obtained again in "4.".
However, this would be a double effort.I am wondering if it is possible to "Convert base64 values to Appian documents" without integration object (without making an API request) and store it in "local!file1" (to "local!file10") in the interface.
Discussion posts and replies are publicly visible
Hi misak0001 ,
Yes it is possible to Convert base64 values to Appian documents within the Appian without using integrations. But in order to do that, you need to store the Base64 values into database.On UI, use a startProcess() function to trigger the process model where you will use the "Get Base 64 documents from database" smart service to generate the document and store it in Appian. This smart service is part of the plugin so you can leverage that plugin and then use onsuccess parameter to pass the docId to UI and then later on pass it into the downloadDocumentLink() function to download the document.Also you can refer this thread on community: How to convert Base 64 format to document?Let me know if that's helpful.
Personally, I would go for the OOTB way with integrations. Depending on the size of the document this could be problematic if you're keeping it in the PV of a process.
Thank you for your answer.If I need to execute a Sql Statement in the database, does that mean I can't use the "Get Base 64 documents from database" smart service for file information retrieved from the database through the integration object?So does that mean I need to access the database directly to use this smart service, without using the integration object?