Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Hi Community,
I was exploring a scenario, where when user loads records summary page, I want write some data into Records /enitty.
I tried to create a web API which writes records, an integration to connect the web API, call that integration from local variable inside the interface. But this doesn't seem to be working.
When I tested web api from integration object , I am getting below details as response but its not writing the data
Any work around or other approach to achieve this?
Thanks in advance
Discussion posts and replies are publicly visible
Use-case aside, have you tested this with a manual button that triggers the integration->API loop back? It looks like the error you're receiving might not be related to the automatic call on page load.
Jesse Knight On testing web API object, its writing data successfully
But when I try to trigger it from Integration object I created, Its not writing any data and response as below
confused where I am going wrong?
Seems like an authentication issue.
The html block in they body looks like the start of an html page rather than Appian's bad authentication response. Navigating to the URL of the API shows that the user has 2 options to login - one SAML and one manual. In an environment like this, I've seen the full response of the session-authentication-based API call is the selection page rather than authentication via either mechanism. Ironically , this setup likely works smoothly in a production-like environment where SAML is the only easily accessible login option.
For longer-term use cases with loopback integrations (e.g. configurable API performance testing in lower environments), I've only been able to make the integration usable in all circumstances by using an API key. Just keep in mind that using an API key tied to an anonymous service account generally violates / circumvents the intent of Appian's core security construct that a user is only able to see / do what is defined by the group security hierarchies. It's akin to the common (but almost always incorrect in regulated environments) practice of "Run as whoever designed the process model" checkbox in PM's.