Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. 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.
Hello,
As shown in the screenshot below, I am able to get a ASP.NET_SessionId in HTTP Response instead of getting it in Result. In such a case how do I save it in a global variable and use it as a header input for another integration to fetch data from the other system API.
Discussion posts and replies are publicly visible
Not sure what you mean with a "global variable". Something like this does not exist in Appian.
But, to make things simple, you wrap the integration that returns this ID into an expression rule that extracts just that ID. Then you call this expression to populate the value of the session header in the other integration.
Thank you Stefan, can you share an example of how do i need to define an expression if name of the integration is 'integration1' and the value I need to extract from http response is ASP.NET_SessionId which I could use in 'integration2'
The return value when calling the integration is a dictionary. You will find the headers inside the result item.
Hello Stefan, In my case the value I am trying to capture/save (ie. Cookie: ASP.NET_SessionId) highlighted in screenshot resides in Integration 'HTTP Response' and not in the Result body Directory . In such case is there a way save it into a local variable so it could be used as a header to another Integration
Duplicate of
Thank you Mathieu. Yes that is similar issue to what we are facing. I wonder if there is any workaround we can do within Appian to solve this. The vendor of the system we are trying to integrate with has denied to make any changes to the result body to make the desired cookie available in it thus we have limited options.