Data action session handling

Hello,
I am using a custom data action to call a webservice, but I have seen that consequent calls to the data action create new Sessions in my backend.
My webservice returns the jsessionid as a parameter, and I tried to put back that value as header to reuse it in the following call... without success.

Is there a way to maintain the sessionID when calling the same data action from a genesys cloud flow?

Thanks a lot.

Hi Luis,

If the session ID is being returned in the body of the response then you could include it in your output parameters, and then store it in Architect (as a flow variable) and then reuse it in future data action calls. If you want to reuse this session across calls you would need to look at storing it somewhere, like a data table.

I guess the first question is, can you even get this to work in test mode? You should be able to configure a header for this. The challenge you could run into is if the sessionId is being returned in a header we currently don't give you access to it. Here is an idea for this you could vote on:
https://genesyscloud.ideas.aha.io/ideas/OTB-I-242

--Jason

Hello, thanks a lot for the response!!
Indeed I have it working using the session id that comes from my web service and injecting it back to the header in the webservice call.

Thanks lot!