Because the API proved incredibly cost inneffective to use. Not well documented, limited in capabilities, not designed for manageable code base and ease of maintenance. I spent a month working with the API, scrapped it and went with the Scheduled reports and overtook the amount of progress I had made in eight business hours.
I have to create code that is as simple and as manageable as possible, because at the end of my work I drop it off for other people to maintain and upgrade. The API didn't support either of those goals.
Consuming the reports that Genesys pumps out natively via email, for consumption in Azure Synapse -- now THAT is creamy code. Super fast to develop, super easy to implement, syncs with other technologies I'm using at this job site where knowledge in one enhances understanding in the others. I can drop this code in a first-year's lap and they'll be running with it in an hour or two. This is code that gets me follow-on contracts.
My only challenge is what I listed above -- I need probably three different reports to deliver, and it's easier in Azure Logic Apps if the subject line on each is different. I'm cheating using the To field instead, including fake emails that I can pivot off of to route different payloads to different parts of the Azure Synapse code. But I'm concerned that long term Genesys or my client are going to see bad email addresses and their email servers could shut down the run. The Subject Line doesn't attract that kind of scrutiny.
Update -- this has already been shut down, presumably by the pure.cloud email server. I've changed my destination address to the format destination+Genesys_Agent_Call_History(at)state_customer.gov instead of having a fake email address. That runs for the moment, but so did the fake email address. Pure.cloud should not get a bad-email-address from this version, so hopefully it will keep running into the future.
One other question -- is there a way to make the Auto-disable at 100 days go away?
------------------------------
John Edwards
------------------------------
Original Message:
Sent: 07-04-2025 00:11
From: Benjamin Giosis-Stone
Subject: Changing the Subject Line for a Scheduled Report
Can I ask why you would use this scheduled email approach instead of using the api?
------------------------------
Benjamin Giosis-Stone
Original Message:
Sent: 07-03-2025 12:26
From: John Edwards
Subject: Changing the Subject Line for a Scheduled Report
Thank you Sam. Thought that's where I had posted it.
This is a biggie for those of us doing automated data mining. I can use Azure Logic Apps to monitor an email address for arrivals and route each to a separate flow of execution pretty easily if there is something in the properties of the email that I can pivot on. Subject Line is the logical choice.
In the meantime I'm going to have to get pretty creative.
------------------------------
John Edwards
Original Message:
Sent: 07-03-2025 12:18
From: Samuel Jillard
Subject: Changing the Subject Line for a Scheduled Report
Hi John,
Welcome to the community. Currently it is not possible to change the subject of the emails only the name of the export. But it seems like a really good idea. I would definitely recommend raising this on the Genesys Cloud Product Ideas Lab with your use case, so it can be considered by the Product Management team.
I am also going to move this to the Genesys Cloud Reporting and Analytics Community to get the best eyes on it and hopefully someone can provide information on how they have got around this or possible alternatives
------------------------------
Sam Jillard
Online Community Manager/Moderator
Genesys - Employees
Original Message:
Sent: 07-03-2025 11:22
From: John Edwards
Subject: Changing the Subject Line for a Scheduled Report
First post ever!
I'm the analytics guy that needs to pull data from our new Genesys system into Azure databases for additional reporting needs. I have a tried and true capture method from other systems that depends upon receiving an attachment in an email sent to our official address.
Genesys supports this! Good news. But I need to pivot based on the subject line in the email, and I need three different reports emailed to the same location. Is there a way to modify the email's subject line? It can be static for a particular report, but I need each different schedule to have a different subject line.
J.
#Reporting/Analytics
------------------------------
John Edwards
------------------------------