How to schedule workflow execution? | Genesys Cloud - Main
| Genesys |
remove preview |
|
| How to schedule workflow execution? | Genesys Cloud - Main |
| Hi, any ideas how to schedule workflow execution?I have created a process that schedules abandoned calls as callbacks. But every morning I need to clear yesterd |
| View this on Genesys > |
|
|
For the above community discussions, i have solution from Genesys.
Automated to purge CVV data from Genesys Cloud Data Tables
Problem Statement:
By using the standard Genesys Cloud Trigger service, the solution overcomes the lack of flexibility in accessing and validating Participant Data to satisfy complex business logic before execution.
Solution Abstract:
"This prototype introduces an automated remediation engine to remove CVV data from Genesys Cloud Data Tables using native features. The process is initiated by an email to a dedicated service address and managed through queue-based routing. The workflow uses an agentless outbound email action for continuity and a wait duration timer for daily task scheduling. Admins can control the process via the GCAB Data Table. Key advantages include bypassing trigger limitations, consolidated management, flexible configurations, and a zero-footprint architecture that utilizes existing Genesys Cloud subscriptions without additional costs."
A Solution Overview
This prototype introduces a self-contained, fully automated remediation engine designed to purge CVV data from Genesys Cloud Data Tables. The solution is built entirely on native "out-of-the-box" features, achieving complex batch processing without the overhead or security risks of external middleware.
Workflow Execution Logic
- Recursive Initiation: The process is triggered by an email sent to a dedicated service address. Using standard queue-based routing, the interaction is delivered to a memberless queue, where the In-Queue Flow acts as the automation engine.
- Autonomous Iteration: To ensure continuity, the flow leverages an Agentless Outbound Email action. This creates a "new thread" for subsequent runs, allowing the process to persist across new interaction IDs.
- Internalized Scheduling: Daily task frequency is managed via a Wait Duration timer within the In-Queue flow. This keeps the entire lifecycle-from scheduling to execution-within the Genesys Cloud.
- Process Control: Admin control is maintained through the GCAB Data Table. By updating the process status to "STOP", the flow will break the recursive loop and terminate the batch cycle.
Technical Summary
|
Component
|
Technical Detail
|
|
Service Email
|
RunBatchProcesses@gcagentdev.nationwide.com
|
|
Primary Queue
|
Run Batch Processes (Memberless/Unstaffed)
|
|
Logic Engine
|
Self-Trigger IQ (In-Queue Flow)
|
|
Control Plane
|
GCAB (Genesys Cloud Data Table)
|
|
Trigger Mechanism
|
Agentless Outbound Email (Recursive Loop)
|
Core Advantages
- Bypasses Trigger Limitations: By avoiding the standard Genesys Cloud Trigger service, the solution overcomes the lack of flexibility in accessing and validating Participant Data to satisfy complex business logic before execution.
- Consolidated Management: A single, unified workflow can be configured to sequence and process multiple distinct batch jobs.
- Flexible With Configurations: Adjusting the execution frequency is as simple as updating a "Wait" timer, requiring no code changes or external deployments.
- Zero-Footprint Architecture: By eliminating external system involvement (e.g., AWS Lambda or Azure Functions), the solution reduces security surface area and architectural complexity.
- Cost-Efficient: Utilizes existing Genesys Cloud subscriptions without incurring additional third-party compute or storage costs.
#Unsure/Other------------------------------
Logan Supparayan
Technology Architect
------------------------------