Difference between revisions of "ATC/Current/AdminGuide/Use the Architect flow with an action map"

From Genesys Documentation
Jump to: navigation, search
(Published)
(Published)
 
(One intermediate revision by the same user not shown)
Line 9: Line 9:
 
|Prereq='''Prerequisites'''
 
|Prereq='''Prerequisites'''
  
−
*[https://help.mypurecloud.com/articles/?p=195191 Configure the following permissions in Genesys Cloud CX:]
+
* [https://help.mypurecloud.com/articles/?p=195191 Configure the following permissions in Genesys Cloud CX:]
 
**'''Architect''' > '''Flow''' > '''Search''' (to select an Architect flow action for an action map)
 
**'''Architect''' > '''Flow''' > '''Search''' (to select an Architect flow action for an action map)
 
**'''Journey''' > '''Event Type''' > '''View'''  (to configure an action map with an event trigger)
 
**'''Journey''' > '''Event Type''' > '''View'''  (to configure an action map with an event trigger)
Line 24: Line 24:
 
|anchor=InboundMessage
 
|anchor=InboundMessage
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=Using the inbound message flow action, you can route the messages to a custom [https://help.mypurecloud.com/articles/inbound-message-flows/ flow] or to trigger a [https://help.mypurecloud.com/articles/about-bots/ bot flow]. Using the bot flow, you can create different workflows for different customer behaviours. This removes the requirement to have a single architect flow for all types of customers.
+
|structuredtext=The advanced orchestration flow action enables you to route interactions to a custom [https://help.mypurecloud.com/articles/inbound-message-flows/ flow] or to trigger a [https://help.mypurecloud.com/articles/about-bots/ bot flow]. You can route the messages to different workflows using the bot flow. This functionality removes the requirement to have a single architect flow for all types of customers.
  
−
#Prepare an [https://help.mypurecloud.com/articles/add-inbound-message-flow/ inbound message flow] or a [https://help.mypurecloud.com/articles/use-architect-to-create-a-bot-for-an-inbound-flow/ bot flow] and create an {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_maps|display text=action map}} to use the inbound message flow.
+
#Prepare an [https://help.mypurecloud.com/articles/add-inbound-message-flow/ inbound message flow] or a [https://help.mypurecloud.com/articles/use-architect-to-create-a-bot-for-an-inbound-flow/ bot flow] and create an {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_maps|display text=action map}} to use the inbound message flow.
 
#In the Set up an Action pane, click '''Configure Trigger Type'''.
 
#In the Set up an Action pane, click '''Configure Trigger Type'''.
 
#Select the advanced orchestration action and then click '''Inbound message flow'''.
 
#Select the advanced orchestration action and then click '''Inbound message flow'''.
−
#Select an inbound message flow to which you need the information routed.
+
#Select the required inbound message flow to route the information.
 
#Click '''Done'''.
 
#Click '''Done'''.
 
|Status=No
 
|Status=No
Line 36: Line 36:
 
|anchor=ArchFlowActionMap
 
|anchor=ArchFlowActionMap
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=# Prepare an {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=AboutArchFlows|display text=Architect flow}}, create an {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_maps|display text=action map}} to use the Architect flow.
+
|structuredtext=#Prepare an {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=AboutArchFlows|display text=Architect flow}}, create an {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_maps|display text=action map}} to use the Architect flow.
−
# In the Set up an Action pane, click '''Configure Trigger Type'''.
+
#In the Set up an Action pane, click '''Configure Trigger Type'''.
−
# Select the advanced orchestration action and then click '''Architect flow'''.
+
#Select the advanced orchestration action then click '''Architect flow'''.
−
# Select the Architect flow to use with this action map. For more information about creating flows, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=BuildArchFlows}}.  
+
#Select the Architect flow to use with this action map. For more information about creating flows, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=BuildArchFlows}}.
−
# Override the default variables. Each data action that the Architect flow calls contains variables that are not set by default. These variables are placeholders that you can populate with visitor-specific data. For more information, see, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=AFSFOverride|display text=Overrides for Salesforce Lead Creation and Campaign Attribution integration}}.
+
#Override the default variables. Each data action that the Architect flow calls contains variables that are not set by default. These variables are placeholders that you can populate with visitor-specific data. For more information, see, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=AFSFOverride|display text=Overrides for Salesforce Lead Creation and Campaign Attribution integration}}.
−
# Specify when to activate the Architect flow action and the time period during which to use it.
+
#Specify when to activate the Architect flow action and the time period during which to use it.
 
#*'''Activation time'''
 
#*'''Activation time'''
 
#**'''Immediately:''' Activate the Architect flow action as soon as a visitor arrives on your website.
 
#**'''Immediately:''' Activate the Architect flow action as soon as a visitor arrives on your website.
 
#**'''On return to site:''' Activate the Architect flow action when a visitor returns to your website.
 
#**'''On return to site:''' Activate the Architect flow action when a visitor returns to your website.
 
#*'''Time range:''' Time period to use the Architect flow action. To use the Architect flow action indefinitely, don't specify an end date.
 
#*'''Time range:''' Time period to use the Architect flow action. To use the Architect flow action indefinitely, don't specify an end date.
−
# Click '''Finish'''.
+
#Click '''Finish'''.
 
{{NoteFormat|Action maps configured to trigger an Architect flow on visitor activity alone trigger as many times per session as the visitor activity occurs. For all other trigger conditions, the Architect flow only triggers once per session when the conditions are first satisfied.|}}<br />
 
{{NoteFormat|Action maps configured to trigger an Architect flow on visitor activity alone trigger as many times per session as the visitor activity occurs. For all other trigger conditions, the Architect flow only triggers once per session when the conditions are first satisfied.|}}<br />
 
|Status=No
 
|Status=No

Latest revision as of 10:38, March 31, 2022

This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.

Configure an action map to use an advanced orchestration flow action.

Prerequisites

Using the advanced orchestration flow action, you can route interactions to a specified bot or queue or to a third-party system based on the behaviour of the visitor.

Configure an action map to use an inbound web message flow

The advanced orchestration flow action enables you to route interactions to a custom flow or to trigger a bot flow. You can route the messages to different workflows using the bot flow. This functionality removes the requirement to have a single architect flow for all types of customers.

  1. Prepare an inbound message flow or a bot flow and create an action map to use the inbound message flow.
  2. In the Set up an Action pane, click Configure Trigger Type.
  3. Select the advanced orchestration action and then click Inbound message flow.
  4. Select the required inbound message flow to route the information.
  5. Click Done.

Configure an action map to use an Architect flow

  1. Prepare an Architect flow, create an action map to use the Architect flow.
  2. In the Set up an Action pane, click Configure Trigger Type.
  3. Select the advanced orchestration action then click Architect flow.
  4. Select the Architect flow to use with this action map. For more information about creating flows, see Prepare Architect components.
  5. Override the default variables. Each data action that the Architect flow calls contains variables that are not set by default. These variables are placeholders that you can populate with visitor-specific data. For more information, see, Overrides for Salesforce Lead Creation and Campaign Attribution integration.
  6. Specify when to activate the Architect flow action and the time period during which to use it.
    • Activation time
      • Immediately: Activate the Architect flow action as soon as a visitor arrives on your website.
      • On return to site: Activate the Architect flow action when a visitor returns to your website.
    • Time range: Time period to use the Architect flow action. To use the Architect flow action indefinitely, don't specify an end date.
  7. Click Finish.
Important
Action maps configured to trigger an Architect flow on visitor activity alone trigger as many times per session as the visitor activity occurs. For all other trigger conditions, the Architect flow only triggers once per session when the conditions are first satisfied.

Go-live checklist

When you are ready to go live with your integration, verify the following items:

  • In Genesys Predictive Engagement, is the action map that uses the Architect flow action active?
  • In Genesys Cloud CX:
    • Is the Genesys Cloud CX integration assigned to the Architect flow action active?
    • Are the Genesys Cloud CX data actions published?
  • In Architect, is the workflow saved and published?
Retrieved from "https://all.docs.genesys.com/ATC/Current/AdminGuide/Use_the_Architect_flow_with_an_action_map (2024-11-09 07:44:34)"
Comments or questions about this documentation? Contact us for support!