Provides the following two smart services that are database agnostic and supports dynamic queries.
The download package has been updated to include this documentation
The documentation for this was accidentally excluded from the latest release.It's attached below. This should answer many questions as to how to operate the plugin successfully.PDF
Hi Jorge, can you please share all the values you set as input? Do you also have something logged in the stdOut when you tested it and got that error? That error is a generic one and most of the times indicates that the inputs of the SS have been wrongly mapped.
Still persists "An error occurred in executing an Activity Class."... What can I do?
JNDI is the datasource name (Example: jdbc/AppianBusinessDS) - You can find the datasource name under admin console>>Datasources or in the datastore object , you can find the datasource name
What is JNDI name??
In the end I got this working too. Thought I'd post and perhaps save someone else a little frustration. This really is a good plugin, would benefit from a few examples.
The node inputs on the Get Base64 Document from Database
Afraid I'm not using the counterpart smart service to create a document from the base64 entry. Sorry - my use case is for one way only. Have you checked the STDOUT log file to see if anything is being trapped there ?
Finally... this worked perfectly. I was struggling with how the sql married with the inputs and how to pass it the document.
If you have a similar example for retrieving the base64 and saving as a file that will complete the round trip. Right now I'm fetching and though it all looks good and I'm getting no errors... no file is being written.
Many Thanks, Dave
If this helps, this is how I'm using the Insert Document as Base 64 smart service
The insert SQL command is structured so that each entry mirrors the layout of the MySQL database
="INSERT INTO MONITORING_dp_config VALUES (:publisher,:name,:documentId,:description,:configid,:isuieditallowed)"
each value in the insert is then populated via the relevant input node entry - the input names are exact matches for the insert statement. When you pass the documentId of the document you want to store as Base64 the Smart Service will look for that document and convert it accordingly.
Hope this helps you out.
Hi Ben, Reaching out trying to get help with consuming the services. When you get a minute can you please post an example of the sql and node inputs for the two services. It just needs a little bit of guidance to be easy to consume. Appreciate any help you can provide.
If anybody has used this can you please post some examples of the sql and node inputs for the two services. It just needs a little bit of guidance to be easy to consume.
I was able to convert a txt file into a Base64 encoded string in the database, however when I tried to convert a pdf file into Base64 the smart service did not work. Did anyone face a similar issue?
Thanks Ben Dudley
Hi arjunm497, It should be compatible. There haven't been any recent changes that would affect the functionality.
© 2020 Appian. All rights reserved.