Massive ArchivedDate change for recordings

[DavidST]

Hi everyone,

We want to accomplish a massive ArchivedDate change for over a year of recordings.

Our goal is to modify the ArchivedDate and get the recordings moved to the ARCHIVED storage.

We have been reading Genesys' documentation and forum, so we found out that the recommended steps should be these:

1.- Get the conversationID
2.- Get the recordingID
3.- Modify the ArchivedDate based on the conversationID + recordingID
4.- Wait for Genesys to archive the recording and change the FileState flag.

For step #1 we are getting the conversationIDs through a job query and for steps #2, #3, and #4 we would develop and run microservices with Java SDKs.

We decided to implement microservices for a parallel work due to the large amount of recordings. We also would add memory cache and a queue to make this process resilient.

We are aware of API rate limits, so we plan to integrate the Java SDK's retry logic for rate-limits like John Carnell explains on this video: Developer Drop 6b: Using the Genesys Cloud Java SDK’s retry logic for rate-limits - YouTube

Has anyone tried or implemented something similar?

We would love to hear your feedback or recommendations.

Thanks!

[John_Carnell]

Hi David,

I think the tutorial you are referred to you in your other post is here.

Thanks,
John Carnell
Manager, Developer Engagement

[DavidST]

Hi @John_Carnell , thanks for your answer. We have already integrated this process and it is been working for a few days.

However, I have a quick question. Do you know if it is necessary to modify the fileState body on the recording medata? Tim Smith mention on this post that the filestate should not have been modified, but this answer is from 2017. I wonder if it has changed and we should modify the filestate and archivedate in order to archive a file.

I appreciate your time.

David