Integrations - Recent Threads

Docusign fail return of Oauth

Carmine Mele — Tue, 21 Apr 2026 06:10:50 GMT

We are using a DocuSign integration configured and tested successfully in the development environment with a DocuSign developer account.

However, we are encountering issues during the authorization phase when using the authorization link.

The authorization flow redirects correctly to DocuSign, and the login page is displayed, allowing the user to log in successfully. However, after the login, the system does not return the authorization token to the application as expected.

By checking the application logs, we can see the following error during the OAuth callback processing. This error appears multiple times; below is one example:

2026-04-21 05:57:39,619 [http-nio-8080-exec-794] ERROR com.appiancorp.connectedsystems.http.oauth.OAuthServlet - Error processing request to Appian OAuth callback URL. 
com.appiancorp.suiteapi.common.exceptions.AppianException: Failed to decrypt. Only values of type Encrypted Text can be decrypted. (APNX-1-4260-002)

It seems that the OAuth callback is reached, but the token exchange or decryption step is failing.

I'm trying to recreate connected system or new keys on docusing, but without success.

The AUTHORIZE button in the connected system, go, but we have multiple singers and we have to use authorization link in interface

RE: Docusign fail return of Oauth

carlk964556 — Thu, 02 Jul 2026 04:13:12 GMT

This sounds incredibly frustrating. Dealing with OAuth issues, especially when decryption fails after a successful login, is a nightmare. It reminds me of trying to get a complicated feature to work in Snow Rider , only to hit a wall right at the last step. Hope you figure out that decryption problem soon!

RE: SAP Integration throught RFC: Input Parameters Truncated

kapilsharma — Tue, 30 Jun 2026 12:52:48 GMT

Hi jurim077147 ,

This appears to be a metadata mismatch between Appian and SAP, rather than an issue with the a!sapInvoke() expression itself.

Since the integration worked before and only started failing after the SAP team increased the length of some fields (e.g., from CHAR(20) to CHAR(25)), it's likely that Appian is still using the old RFC metadata. As a result, SAP reads the incoming data with incorrect field offsets, causing values from one parameter (e.g., KEY2) to spill into another (KEY1).

I recommend verifying the following:

Confirm the updated parameter lengths and data types in SAP (using SE37/SE11).
Refresh or re-import the SAP RFC/BAPI metadata in Appian so both systems use the same interface definition.
Check whether any structures or additional parameters were also modified, as those changes can also cause field alignment issues.

The behavior you described (where KEY1 contains the first part of its value followed by characters from KEY2) is a typical symptom of an RFC structure definition mismatch between the two systems.

Let me know if that helps.

SAP Integration throught RFC: Input Parameters Truncated

jurim077147 — Wed, 13 Nov 2024 11:12:15 GMT

Hi,

we are using the function a!sapInvoke to integrate with SAP throught RFC. Weeks ago, the integration worked and we received the results expected.

For development requirements, external system add some parameters and change the lenght of some text fields (from 20 to 25).

After those changes, we receive errors on specific fields, but the return message gives a value that doesn't match the one sent.

So, we check with external system and the problem is on all fields.

For example, if we pass the parameter of the below images, external system receive as key1 the value "ABC/AAA/456789001/20ABC". It seems it takes the first 20th char and then take the others from key2.

ICould you help us to understand the nature of the problem, please?

Thanks in advance.

Regards

RefreshVariable is not working

Alexander Flores — Sat, 27 Jun 2026 06:32:05 GMT

Hi, i´m facing a refreshvariable problem, this code call a rule caled rule!slc_obtenerPolizas(idSiniestro: ri!siniestro.idSiniestro)

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:75dca3e9-aa53-49e8-9eab-a2d032d008b2:type=text&text=%20%20local%21refrescarPolizas%3A%20false%2C%0D%0A%20%20%2F%2AREGLA%20QUE%20OBTIENE%20LAS%20POLIZAS%2A%2F%0D%0A%20%20%2F%2AY%20COBERTURAS%2A%2F%0D%0A%20%20local%21polizas%3A%20a%21refreshVariable%28%0D%0A%20%20%20%20value%3A%20rule%21SLC_obtenerPolizas%28idSiniestro%3A%20ri%21siniestro.idSiniestro%29%2C%0D%0A%20%20%20%20refreshOnVarChange%3A%20local%21refrescarPolizas%0D%0A%20%20%29%2C]

rule expression is this:

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:a934894e-1678-40cc-86a6-bc7b0ea99ddc:type=text&text=a%21localVariables%28%0D%0A%20%20local%21polizas%3A%20rule%21SLC_GetObtenerPolizasByDeclaracionID%28idSolicitud%3A%20ri%21idSiniestro%29.data%2C%0D%0A%20%20local%21ramos%3A%20a%21forEach%28%0D%0A%20%20%20%20items%3A%20local%21polizas%2C%0D%0A%20%20%20%20expression%3A%20a%21update%28%0D%0A%20%20%20%20%20%20fv%21item%2C%0D%0A%20%20%20%20%20%20%22ramos%22%2C%0D%0A%20%20%20%20%20%20rule%21SLC_GetObtenerCoberturaByPolizaID%28idPoliza%3A%20fv%21item.idSiniestroPoliza%29.data%0D%0A%20%20%20%20%29%0D%0A%20%20%29%2C%0D%0A%20%20local%21ramos%0D%0A%29]

which call a two api, we cast json into CDT.

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:1aa955cc-a4ce-4d5b-8fb4-bd1b2a5c5fdd:type=text&text=a%21localVariables%28%0D%0A%20%20%2F%2A%201.%20First%2C%20configure%20the%20integration%20object%20to%20return%20successfully%20%2A%2F%0D%0A%20%20local%21integrationResponse%3A%20a%21refreshVariable%28%0D%0A%20%20%20%20value%3A%20rule%21CT_SLC_getCoberturaConsultarxPolizaID%28%0D%0A%20%20%20%20%20%20idPoliza%3A%20ri%21idPoliza%2C%0D%0A%20%20%20%20%20%20usuario%3A%20loggedInUser%28%29%0D%0A%20%20%20%20%29%2C%0D%0A%20%20%20%20refreshAlways%3A%20true%0D%0A%20%20%29%2C]

Even local!refrescarPolizas is changing value by button, my rule rule!SLC_obtenerPolizas is not refreshing.

I tried using unconvetional code like:

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:ac228317-bd0b-492a-95ea-acdf2fe86cef:type=text&text=%20%20local%21polizas%3A%20if%28%0D%0A%20%20%20%20local%21refrescarPolizas%2C%0D%0A%20%20%20%20rule%21SLC_obtenerPolizas%28idSiniestro%3A%20ri%21siniestro.idSiniestro%29%2C%0D%0A%20%20%20%20rule%21SLC_obtenerPolizas%28idSiniestro%3A%20ri%21siniestro.idSiniestro%29%0D%0A%20%20%29%2C]

and it works, however i wanna know why my refreshvariable is not working. Thanks in advance for your reply

RE: RefreshVariable is not working

Shubham Aware — Mon, 29 Jun 2026 11:39:36 GMT

refreshOnVarChange fires only when the watched value actually changes. Setting local!refrescarPolizas to true again won't trigger it.
Fix by toggling, or better, incrementing a counter.

a!save(local!refrescarContador, local!refrescarContador + 1)

RE: RefreshVariable is not working

Stefan Helzle — Sat, 27 Jun 2026 15:51:56 GMT

I covered variable refresh in my recent blog post: https://appian.rocks/2026/05/27/performance-vs-freshness-mastering-arefreshvariable/

RE: Integration with Microsoft Authenticator app to get MFA code

devanshum749680 — Wed, 24 Jun 2026 08:22:44 GMT

I have a similar requirement for step-up authentication during the registration submission process. The scenario is not related to initial login authentication. Instead, the user is already authenticated, and at a specific point in the workflow we need to perform an additional identity verification before displaying confidential information or allowing access to sensitive sections of a form/dashboard.

Has anyone implemented a mid-process step-up authentication mechanism in Appian, where the user's identity is revalidated based on the sensitivity of the data or action being performed?

Please note that I am not looking for solutions related to login authentication or SSO login flows, as this requirement specifically involves step-up authentication within an active user session.

Integration with Microsoft Authenticator app to get MFA code

sudip.das005 — Mon, 16 Jun 2025 13:56:22 GMT

Hi,

Is there any way to integrate with Microsoft authenticator app from Appian to get the current One-time password code?

Thanks,

Sudip

Recommendations for local analytics tools to track field-level user interactions?

humzam8798 — Tue, 16 Jun 2026 18:49:34 GMT

We are looking to implement user interaction tracking within our Appian applications. Specifically, we want to capture granular data like field-level interactions and form engagement.The analytics solution must be local (on-premise / self-hosted).

Has anyone successfully integrated a local analytics or product usage tool with Appian to achieve this? We have looked into Matomo, but found the implementation overhead too high. Inserting integration calls across every field and interface requires too much manual effort and maintenance.

Thank you in advance!

MS Graph: Send email with attachment

Guy — Mon, 08 Jun 2026 16:45:56 GMT

We are trying to send emails with attachments using the MS Graph sendMail API.

We're seeing an issue where the document is not being converted to Base64, see screenshot below.

Is the issue that we're starting with a json and converting to dictionary? This was done because if we define the dictionary directly, the key "@odata.type" is not recognised properly because of the period.

Thanks!

RE: MS Graph: Send email with attachment

Stefan Helzle — Tue, 09 Jun 2026 06:01:30 GMT

You tried to create a JSON string using text operations. Then the reference to the document turns into "[Document:xx]". Now, you try to turn this into a dictionary. How should Appian know what you are referring to?

RE: MS Graph: Send email with attachment

Guy — Mon, 08 Jun 2026 17:52:11 GMT

Amazing that worked with one small change, line 18 should be "contentBytes": toDocument(fv!item)

Thank you v much!

RE: MS Graph: Send email with attachment

Jesús Hormigos — Mon, 08 Jun 2026 17:11:01 GMT

Use the following code in your "attachments" attribute

"attachments": {
      if(
        a!isNullOrEmpty(ri!attached),
        {},
        a!forEach(
          items: ri!attached,
          expression: {
            "@odata.type": "#microsoft.graph.fileAttachment",
            "name": concat(
              document(fv!item, "name"),
              ".",
              document(fv!item, "extension")
            ),
            "contentType": concat(
              "application/",
              document(fv!item, "extension")
            ),
            "contentBytes": fv!item
          }
        )
      )
    }

RE: Add an attachment greater than 3MB to an O365 mail via Graph API

Guy — Mon, 08 Jun 2026 16:48:33 GMT

Appreciate this is a 2 year old post, but if you can share how you sent emails with attachments, and what I'm doing wrong here, I'd really appreciate it!

Add an attachment greater than 3MB to an O365 mail via Graph API

RockyMeadows — Thu, 29 Aug 2024 15:40:27 GMT

we are looking to use the MS Graph API to create and send emails our issue relates to an odd behaviour we are experiencing when attaching large files.

All attachments under 3mb work as expected. Per MS documentation when attaching >3mb we should use the "Attach Large Files" API. Per that process we get a session and then chunk the upload, when we start the upload the API immediate terminates.

Has anyone been able to successfully attach a file > 3MB by breaking into smaller chunks and send an email. A similar plugin MS Graph Utilities uploads something larger files by breaking into chunks into One Drive/SharePoint but is there something similar which attaches it to an email?

Calling WEB API from Integration with in Appian

praveenkumarn0006 — Fri, 29 May 2026 17:14:02 GMT

Hi community,

I have a scenario where i need to Send JSON in a paragraph field from Appian interface, Which should call a WEB API, but as we can't call WEB API directly from interface, I'm calling INTERFACE>INTEGRATIONS>WEB API,

It's not working and I don't see PM is starting which was configured inside a WEB API using a start process for success response or even failure response.

Can someone Suggest me a Better way if we can do this.

Thanks in Advance

RE: Calling WEB API from Integration with in Appian

Stefan Helzle — Fri, 29 May 2026 20:17:00 GMT

Hm ... do what ... and why ... for what purpose ... and what does not work?

https://appian.rocks/2025/02/24/the-5-step-framework-for-asking-effective-questions/

RE: Facing issue with default setting of timer trigger setting time in seconds

Stefan Helzle — Tue, 26 May 2026 06:46:35 GMT

Did you consider to start a process every 5 minutes which then consumes more than one message?

Or, it spawns multiple processes consuming multiple messages?

You just have to make sure to consume each message only once. In such scenarios, I tend to use DB locking tables.

Facing issue with default setting of timer trigger setting time in seconds

akshantr0678 — Mon, 25 May 2026 16:56:55 GMT

we are receiving data via web api in Appian. as the volume is very high, we save the events to database to process them later via a second process model which keeps polling the db for pending events.
The issue is that processing should be in ALMOST real time without overwhelming the Appian environment. to do that, we tried to schedule the polling process every 30 seconds. but the minimum time it takes for repeat configuration is 5 minutes which is of no use to us.

how can we configure a process to run every 30 seconds ?

RE: Facing issue with default setting of timer trigger setting time in seconds

Harsha Sharma — Tue, 26 May 2026 06:44:58 GMT

Instead of timer, have the pending events queried in batches in the process model. For processing have a separate process where you can pass the batch data and complete processing for multiple events in parallel. Loop through the batches and processing sub process by clearing/hiding unnecessary pvs for better memory management.

Not sure, what sort of processing is taking place. If its data related then see if in database itself store procedures/ triggers can help achieve the same instead of Appian process.

RE: Facing issue with default setting of timer trigger setting time in seconds

subhankar-Maantic — Tue, 26 May 2026 04:10:23 GMT

You probably do not need a polling process. At the end of WebAPi process you can trigger the 2nd process and it should have a condition if the previous instance is running do no initiate a 2nd DB query process.

Most efficient solution could be using kafka integration in 26.4

RE: Facing issue with default setting of timer trigger setting time in seconds

shivakanthreddyp0001 — Tue, 26 May 2026 00:23:28 GMT

Hi akshantr0678
Did you look at this transaction manager solution Appian Community

RE: Send Document as Base64 - SOAP Integration

erickjavidb860617 — Tue, 12 May 2026 16:20:43 GMT

Thank you for your response and for sharing your experience.

I’m going to try the database plugin approach first and evaluate how stable it is in our case. As you mentioned, I’ll make sure to clean up the temporary table after each execution.

If that approach becomes difficult to maintain or introduces performance issues, I’ll probably consider either a custom plugin or an intermediate service to handle the XML/Base64 transformation outside of Appian.

Thanks again for the suggestions.

Send Document as Base64 - SOAP Integration

erickjavidb860617 — Fri, 08 May 2026 23:03:21 GMT

Hello everyone,

I hope you are doing well.

I am currently facing an issue while sending a SOAP request through an Appian Integration. The request body contains a document that must be sent as Base64 inside the XML body.

I have been researching possible solutions, and according to the Appian documentation, automatic Base64 conversion only seems to work when using a Data Type (CDT) with automatic XML conversion enabled.

However, in my case, the XML structure required by the service contains specific namespaces and a custom structure, so when I tried using a CDT, the generated XML did not match the expected format and the service returned a 500 status code.

I also found some plugins that convert documents to Base64, but my requirement is only to convert the document temporarily and send it in the request body. I do not need to store the Base64 value in the database.

Another alternative I considered was creating an Appian Web API that returns the Base64 content and then consuming that response in the Integration. However, the main issue is that Appian does not seem to provide a native way to convert a document to Base64 when building a custom SOAP/XML request manually.

Has anyone faced a similar scenario or found a better approach to send documents as Base64 in a custom SOAP/XML request?

Thank you in advance for your help.