Difference between revisions of "ATC/Current/AdminGuide/PreparePCArchFlows"
From Genesys Documentation
(Published) |
(Published) |
||
Line 4: | Line 4: | ||
|TocName=Prepare Genesys Cloud | |TocName=Prepare Genesys Cloud | ||
|Context=Prepare a Genesys Cloud integration and data actions for use with an Architect flow action. | |Context=Prepare a Genesys Cloud integration and data actions for use with an Architect flow action. | ||
+ | |Dimension=ArchFlow | ||
|ComingSoon=No | |ComingSoon=No | ||
|Platform=PureConnect, GenesysCloud, GenesysEngage-cloud | |Platform=PureConnect, GenesysCloud, GenesysEngage-cloud |
Revision as of 14:52, April 14, 2021
This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.
Prepare a Genesys Cloud integration and data actions for use with an Architect flow action.
Prerequisites
- Configure the following permissions in Genesys Cloud:
- Integrations > Integration > Add, Delete, Edit, View
- Integrations> Action > Add, Delete, Edit, Execute, View
Prepare a Genesys Cloud integration
Before you configure an action map to use an Architect flow action, install and configure an integration in Genesys Cloud:
When you first install a Genesys Cloud integration, it has an active status. The integration must remain active for a Genesys Predictive Engagement Architect flow action to use it. To verify the status, check the setting of the Status toggle on the main Integrations page.Prepare the Genesys Cloud data actions
- Import the necessary data actions for your integration:
- Associate the data actions with your integration and configure them. The configuration options for the data action are specific to the data action itself. For more information about possible configuration options, see Data actions on the About Integrations page.
- Save and publish your data actions.
Important
When you use predefined data actions as part of a Predictive Engagement solution, do not modify them.Tip
Your Genesys Cloud organization can have 15 requests per second per data action. If you anticipate a higher volume of requests, contact Professional Services.Comments or questions about this documentation? Contact us for support!