-
Recently active
Dear anyone, I am currently trying to execute Box API that uses JWT, But the following issue occurred when executing the Box API to obtain an access token. If someone else has sent about the same issue and it has been resolved, or alternative solutions you may suggest would be highly appreciated. [Error details] *This is written in the body of the HTTP response. "{"error":"invalid_grant","error_description":"Please check the 'box_sub_type' claim. The value for 'box_sub_type' is invalid"}" [Procedure] 1.Obtain a JWT using the createtoken() function of the “Box” Plug-ins. 2.Execute the Box API to obtain Box's Access Token. *An error occurs here. [Already Confirmed] 1.Applications created in Box have been approved by the Box administrator. 2.'box_sub_type' and 'sub' classifications must match. Thank you very much in advance for your assistance. Best reg
Dear Anyone, I am currently trying to execute Box API that uses JWT, But the following issue occurred when executing the Box API to obtain an access token. I get an error stating that the JWT is an invalid value, but when I check with jwt.io I can see that it is a valid value. If someone else has sent a support request asking about the same issue and it has been resolved, or alternative solutions you may suggest would be highly appreciated. [Error details] *This is written in the body of the HTTP response. body: "{"error":"invalid_grant","error_description":"Signature verification failed"}" ・Confirmed JWT in jwt.io Thank you very much in advance for your assistance.
Dear anyone, I am currently trying to execute Box API that uses JWT, I saw an article that said that you need to set "Third-Party Credentials" when executing the Box API. However, the connection is not working properly, so if you know which field to set in the Credentials, please let me know. Thank you very much in advance for your assistance. Best regards,
Hi everyone, I'm trying to load json to db using this Appian smart serivces. My sample json data i have given below. It has multiple dynamics parameter for example user have multiple types of phone number. if it flattens json file then its working without any issue but sub paramters are not working as expected. Added more details below Main Issue while accessing the json sub parameters which is dynamic In smart service Load JSON to a database, "JSON key/Column Name mapping" Field for json fields key i have tried like this Phone.number as well as Phone[].number but while executing Process model considered as "FirstName", "Phone" as column instead of each table column fields like FirstName, PhoneType PhoneNumber. I cant able to navigate inside of sub paramters while mapping json key to table columns name Plugin name: JSON Tools Smart service name: Load JSON to a database my sample appian rule { "FirstName": "First_
I'm using a Google Sheets connected system in Appian with OAuth 2.0 authentication. The integration works initially, but I'm encountering an issue where the connection requires reauthorization almost every hour. Has anyone faced a similar problem with token expiration or session persistence? Is there a recommended way to maintain or refresh the token without requiring manual reauthorization so frequently? Appreciate any suggestions or best practices to resolve this.
I am getting this error on html to pdf converter node - java.lang.Exception: java.lang.IllegalArgumentException: null incompatible with Global antialiasing enable key Following is the html body retrieved from email Best regards,Isac Hi Eunice/Team, All set: Hi team Pls set up both tranches Thanks, Eunice Trader Additional Comments Term Sheet;<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="">schemas.microsoft.com/.../omml" xmlns="">www.w3.org/.../REC-html40"><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><style><!--/* Font Definitions */@font-face {font-family:"Cambria Math"; pa
The requirement is that Process should start on the Inbound email should receive by the process. And We need to show the Inbound Email uploaded into the task automatically, so i have used the "Create EML File From OOBT Poller" plugin which was giving the expected result but the formatting in the Body content is giving in a single line. Please suggest a way to align the email body content Process Model The output file from the pulgin
Can we get the UUID of Groups in Appian via any function or plugins in an expression rule.
In integration if the response is in xml format, how to convert it to appian value and save in a record type
We call the expression rule (ER) "cursor_value_from_previous_call" from the "Cursor" integration. This ER invokes another expression rule, "CursorValue," which extracts the cursor value from the integration's response body. The extracted value is then passed to ER "cursor_value_from_previous_call," which returns the JSON value in the following format: Request Body: { "cursor": { "value": "" }} Value is null for the first call, for other subsequent calls, we pass the value that we have extracted from the first call. Kindly refer the flow diagram below: I am not able to achieve this without using the logic of while loop. For loop is not helping as the variables are immutable. Any insights are highly appreciable.
We recently upgraded an environment to 25.2 and when we use the Create & Read Email Files Utilities from the App Market we are getting an error "An error occurred while creating a note" on the front end and Could not create EML java.lang.IllegalStateException: Error while searching for service [jakarta.activation.spi.MailcapRegistryProvider] in the tomcat logs. Has anyone received these errors or know of a way to fix them. We use this plugin quite a bit to create custom notifications to the users.
Can I call an expression rule from an integration's request body? Note: The response of the expression rule is a JSON body. Method: POST
Hello, I am working on an integration where I need to set a custom value for "boundary". The HTTP request is of Content-Type: multipart form data. The other system expects the boundary value to be "cpi". In Headers, I set Content-Type as "multipart/form-data; boundary=cpi". However, in the HTTP request that Appian generates, Appian seems to be using a random boundary value, and ignoring the value that I have set. HTTP request that I see: I see this data in API trace logs. The integration works through Postman, and I see the correct boundary set. Postman screenshot. Thank you in advance for your help. Regards,Harish
I have an interface that calls 2 different intergrations. There is data that return for both integrations, but it randomly returns null after calling it multiple times. I have inserted where I am calling the integrations. a!localVariables( local!historyData: a!refreshVariable( value: index( rule!GET_incomingRequestHistoryByID(requestId: ri!requestId).result, "body", {} ), refreshOnReferencedVarChange: true() ), local!requestDetails: a!refreshVariable( value: index( rule!GET_allIncomingRequestsByID(refundRequestId: ri!requestId).result, "body", {} ), refreshOnReferencedVarChange: true() ), This is what my error looks like when 1 integration returns as null This is what my local variable looks like when both integrations return data:
Extract data from database tables and populate a PDF form. The PDF should contain editable and fillable dropdown fields that allow users to select values dynamically
Hi, I am doing some research in to the Google Chart Plugin ... https://community.appian.com/b/appmarket/posts/google-charts-component-plug-in?CommentId=209280fe-6dcb-45e6-9bf7-81336dc6e24d Would anyone know if an item on a chart could be stored in to a variable? I can see there is an onSelection parameter, I am curious as to how an item from a chart could be saved down such as an ID to enable further drilldown behaviour? Thanks.
Hello, We need to download .msg files (Outlook mail) from an External System using an integration that receives the document as base64. The current problem is that Appian is able to download that document but without its extension, using the "convert base64 values to Appian documents". I suspect it's because the MIME Type "application/vnd.ms-outlook" is not supported by the integration object as established in the following documentation I found: https://docs.appian.com/suite/help/25.1/Integration_Content_Types.html#document-(auto-detect) https://www.iana.org/assignments/media-types/media-types.xhtml Is there any way to workaround this? Any help is appreciated Thank you!
Hello All, We're calling an integration within a process model that receives a JSON document (approx. 95 MB in size). Using the Load JSON Document To Database plug-in to dump the data directly into a database table. The Process model completes successfully. However, we're capturing the following error in the logs: "Error parsing JSON Content or audit data" Please share your thoughts on this. Thanks In advance Lokesh
Hi All, We have requirement to create cases based on the mails received in one or more mailboxes in Appian. Kindly guide us on use case or plugin which will help us to achieve this solution. In addition, we have to classify mails based on the subject line of the mails.
Hi,We are trying to implement sending and retrieving files from AWS S3 bucket. Is it possible to be implement the same without using any plugin? If yes, how can it be proceeded since AWS S3 is new for us. Any help would be helpful.
Hello Everyone, We are using Appian cloud and we have a requirement to move few CSV files to Appian server folder (/apps/cgdata/folder1). I have to read as well as write files to this location. Which smart service we can use and do we need any particular access for it?
Hello team, CONTEXT: During the process lifecycle, we want to use blob storage for long-term storage of files that have been stored for a long time in Appian. If users want to access these old files, appian will have to make a GET request to blob storage to retrieve this file and persist it for eventual viewing or download. I'm trying to send a file to a container in Azure blob storage through an API with a PUT method and I'm facing some problems. I tested via postman, the same endpoint, with the same settings (headers and query parameters), choosing the binary format for the payload, and uploading the file. I sent the file to the blob storage and called the Get request in Appian to retrieve it. I was able to access the file perfectly in Appian. When I tried the same thing in Appian, the following situations occurred: 1. When I selected the Content-Type: Document (auto-detect) option, the API returned a status of 403 - Forbidden. 2. When I selected the custom option
We upgraded the plugin to 4.1.0 and while using the latest smart service '(SFTP) Get Remote folder Contents' replacing the deprecated smart service "Get Remote Directory Contents over SFTP", we got the below error: "Algorithm negotiation fail: algorithmName=""server_host_key"" jschProposal=""ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256"" serverProposal=""ssh-rsa""" The same smart service (SFTP) Get Remote Folder Contents works fine with the Plugin version 3.0.3. Is there a known resolution to this error?
The article: Integration Object - Appian 23.3 says that if the response body is in JSON format, the maximum size of the response file should be <5MB. In our environment, there are instances when we are getting Integration response when the file size is 7MB and there are instances where we are not getting integration response when the response body is 5.12MB with the error :“Response body size limit exceeded.” Any explanation to this query is much appreciated. Moreover, When a file is encoded in base64, its size increases by approximately 33% compared to the original data size. This made me curious how the maximum limit for JSON body is 5MB and Base64 is 75MB.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
