Share:
This plug-in contains functions that can perform the following:
This listing currently represents version 2.3.0 of the plug-in. The functions included are as follows:
Example Use:
Hi Stefan, did you ever find a solution? We're trying to do the same thing with Azure Storage API SAS, which also provides a base64 encoded key.
Hi Ed,
Please try with just the id of the document; this documentId will be used in the class to load the document by the Id
I am having some issue using the sha1hashdocument function. I can get a value with sha1hash(todocument(43763)) but is not the correct hash value.
What am I missing?
usage (where 43763 is the appian document id):
sha1hashdocument(todocument(43763))
getting the following error:
Expression evaluation error at function 'sha1hashdocument': The passed parameter(s) are of the wrong type. Received the type com.appiancorp.common.xml.JaxbConversionException: JAXB was not able to produce a value for typed value TypedValue[it=13,v=43763] as java class java.lang.Long.
Hi Eliot, this plugin was of great help when integrating to the Azure Service Bus. Now we need to talk to Azure Cosmos DB and they found, annoyingly, another way of building auth tokens The key itself is base64 encoded and must be decoded before usage. See https://docs.microsoft.com/de-de/rest/api/cosmos-db/access-control-on-cosmosdb-resources?redirectedfrom=MSDN. I did not find a way to do that in Appian. Any ideas? I almost don't dare to ask if you can add another function to the plugin.
Any chance of updating this to use scsField so the key can be stored in the Third Party Credentials store?
This is a very useful plugin and we have used some of its functions for creation of a Shared Access Signature token required for REST API Intergation with Azure Service Bus. Much appreciate Appian's support with this Plugin