Genesys Cloud - Developer Community!

Use case:
We need to set recording retention for conversations after it completes, based on a participant data that is only populated at disconnect. We're trying to avoid building automation that deletes/exports recordings via the Recording API. We'd prefer a policy‑driven approach if possible. 

I understand participant data can be set/read during live interactions in Architect and persists across transfers/flows; however, I don't see a way to make a policy directly match on a participant data attribute.

We don't want to use Triggers + Workflow + Recording API to delete recordings. we're trying to avoid it here.

Hi Sesha,

One way you can achieve this while keeping it policy-driven is to map your Participant Data logic to something policies can evaluate typically a wrap-up code. You can set the wrap-up based on your logic at the end of the interaction, and then apply different retention rules in the recording policy using that wrap-up.

Alternatively, if the criteria is known earlier, routing to specific queues and applying policies based on queue can also work.

Hope that helps, and keen to see if others from the community have a different way of approaching this.