Difference between revisions of "ATC/Current/AdminGuide/Use the Architect flow with an action map"
From Genesys Documentation
m (Text replacement - "Altocloud([. ])" to "Predictive Engagement$1") |
m (Text replacement - "Altocloud," to "Predictive Engagement,") |
||
| Line 50: | Line 50: | ||
|structuredtext=When you are ready to go live with your integration, verify the following items: | |structuredtext=When you are ready to go live with your integration, verify the following items: | ||
| − | *In | + | *In Predictive Engagement, is the action map that uses the Architect flow action {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Activate_inactivate|display text=active}}? |
*In Genesys Cloud: | *In Genesys Cloud: | ||
**Is the Genesys Cloud integration that is assigned to the Architect flow action {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Build_webhooks|anchor=PCConfigure|display text=active}}? | **Is the Genesys Cloud integration that is assigned to the Architect flow action {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Build_webhooks|anchor=PCConfigure|display text=active}}? | ||
Revision as of 15:21, November 17, 2020
This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.
Contents
Prepare action maps to use an Architect flow action.
Prerequisites
- Configure the following permissions in Genesys Cloud:
- Architect > Flow > Search
- Journey > Event Type > View (to configure an action map with an event trigger)
- Journey > Action Map > Add, Delete, Edit, and View
Use the Architect flow action with an action map
Important
You must have the Architect > Flow > Search permission in order to select an Architect flow action for an action map.- Build an action map.
- Under Select action, click Configure.
- Click Architect flow and then click Next
- Select your Architect workflow and click Next.
- Override default variables with user-specific data.
- Select when the Architect flow action will work.
- Click Finish.
Override default variables
Each data action that the Architect flow calls contains variables which are not set by default. These are placeholders you can populate with user-specific data. For specific examples, see:
Go-live checklist
When you are ready to go live with your integration, verify the following items:
- In Predictive Engagement, is the action map that uses the Architect flow action active?
- In Genesys Cloud:
- Is the Genesys Cloud integration that is assigned to the Architect flow action active?
- Are the Genesys Cloud data actions published?
- In Architect, is the workflow saved and published?
Comments or questions about this documentation? Contact us for support!