Hi Srikanth, I would handle this in Architect.
My suggestion is to configure the Data Action to return the date value as raw data, without transforming it in the action. Then, inside the Architect loop, parse the returned string by breaking it into month, day and year.
From there, you can validate only the expected formats, ignore ranges or unsupported values, normalize the brackets/spacing when needed, convert the month abbreviation to a number, adjust the year if it comes with two digits, and then rebuild it as a proper DateTime.
After that, you can use ToAudioDate() or ToAudioDateTime() to play the date to the customer.
I would only use a Genesys Cloud Function if this rule becomes more complex or needs to be reused across multiple flows. For this case, keeping the logic in Architect should be simpler and easier to debug.
------------------------------
Att,
Breno Canyggia Ferreira Marreco
------------------------------