Hi there, I have a Secure Flow that is authorising payments through a Payment Service Provider, the last step is that it needs to call an API to confirm the payment result.
I have three products, A, B & C ... A & B are in Production, and this API call is working absolutely fine. For Product C it consistently fails when called from the IVR Flow, but is successful from the Data Action Test Page.
None of the data being passed is PII, or PCI, so I have spooled all data fields out to Participant Data (in Test) and then use that data to test the Data Action - It Works.
I have spooled out data for Products A & B, and have compared side by side and it matches where it should match and does not where it shouldn't (references, payment amounts.
Are there any known problems between a Flow and a Data Action that it may be worth being aware of? I note for instance that there was a problem with Blank FIelds, but this was back in 2017 and a fix was being prepared.
Is that still around, is there anything else ?? Can anyone suggest anything ??
So I have identified what is causing my problem, and it feels like a Genesys Bug to me.
Within my API there are 30 odd variables - 2 of them specifically, and sticking with my example description, are specific to Product A & B, but are never used in Product C ... as such those two fields are not mandatory.
In order to simplify maintenance, we have one Data Action pointing to this API, and regardless of whether I add data for these two fields, or ignore them, the Data Action and API work perfectly.
We then have a generic Secure Flow for Payments, as such within this flow for Products A & B these two fields are populated with values, but for Product C they are never set, and I guess could be interpreted as never even initialised, so have null content.
It appears that it was these two variables are the cause of my problem ... I have added some logic to set them to a value of "1" when I know I am working with Product C, and all is then fine.
Can anyone confirm that they have seen similar issues?
In particular, can anyone at Genesys confirm whether this is known/expected behaviour, also whilst I can understand why there can be no compile/setup warning, as to all intents and purposes the variable is there and works, why is there no Logging or Error Messaging available that can highlight this sort of runtime error to avoid people spending so much time debugging.
Are the problematic inputs strings? If so, try testing this again in the Data Action Test UI, but make sure that you do not touch the two problematic inputs at all. If they are untouched the test will effectively send "null", however if you set a value and delete it the test will send "" (Empty string), which can lead to different results.
Feel free to create a support ticket in parallel for this. If it is a bug that will help us track it and prioritize the issue, and may be needed depending on what type of debugging is required to isolate the issue.