Genesys Cloud - Developer Community!

Hello dear Community,

We have a couple of Secure Flows for managing CC payments integrated with a paygate.

They are working perfectly, but we still have some doubts on the "call secure data actions": in Architect, based on the official documentation Call Secure Data action - Genesys Cloud Resource Center , it seems that the failure outputs should be there also for this kind of action; but actually these outputs are not in the secure flow capabilities, and we can map only the success outputs.

So we can get some details by the paygate when the action takes the succesful exit path, but not when it takes the failure one

Although, If we test the secure data action within the data action tester in the ORG we can clearly see the full response in case of failure.

We have some option in our mind, and we would like to share them here:

• does the PCI DSS toggle button that should be required to the Customer Support plays any role in this situation? 
• does anybody is in our same boots and found another way?
• are we misunderstanding something?
• at first we put our focus on the response template, but then we understood that the problem is that the response 400/500/422 from a paygate does represent a failure exit path, so every configuration in the success template is not bringing anything more. 

Have a nice day,

Lorenzo

Hi Lorenzo,

I believe this is expected behaviour in Genesys Cloud Secure Flows where only success outputs are exposed and failure responses (like 400/500/422) aren't available for mapping.

From what you've described, you're on the right track  those HTTP responses follow the failure path, and the response template won't help in that case.

The PCI DSS / secure toggle is required to use the action in secure flows, but it doesn't change this behaviour.

There's also an idea in the Genesys Ideas portal that seems closely related to this limitation says in development :
https://genesyscloud.ideas.aha.io/ideas/INB-I-1498

It's about allowing access to data action error messages in voice flows, which would help surface failure details instead of only handling generic errors.

Someone from the community might be able to add more to this or share if they've found a workaround.

------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------

Just to add, failure paths do exist in call flows (including Secure Flows), but failure outputs aren't available for mapping like they are in non-call flow types.

So you can detect that the action failed, but you can't access or use the failure response details in Architect.

The idea shared above is essentially for the same reason to allow access to data action error messages in voice/call flows, which isn't currently supported.

Hope this helps.

Hello Phaneendra,

thank you very much for your answers.

I agree that it seems the expected behaviour; even if the documentation is reporting differently (maybe somebody from Genesys will read here and could adapt the material accordingly). 
I would say that the Idea won't change this situation, if the assumption above is correct.

Let's see if others feedback will come! 

BR

Lorenzo