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

From Genesys Documentation
Jump to: navigation, search
(Published)
(Published)
 
(17 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
{{Article
 
{{Article
 
|Standalone=No
 
|Standalone=No
−
|DisplayName=Prepare Predictive Engagement components
+
|DisplayName=Use action maps to trigger an advanced orchestration flow
−
|TocName=Prepare Predictive Engagement
+
|TocName=Configure an advanced orchestration flow action
−
|Context=Prepare action maps to use an Architect flow action.
+
|Context=Configure an action map to use an advanced orchestration flow action.
 +
|Dimension=ArchFlow
 
|ComingSoon=No
 
|ComingSoon=No
 
|Platform=PureConnect, GenesysCloud, GenesysEngage-cloud
 
|Platform=PureConnect, GenesysCloud, GenesysEngage-cloud
 
|Prereq='''Prerequisites'''
 
|Prereq='''Prerequisites'''
  
−
*[https://help.mypurecloud.com/articles/?p=195191 Configure the following permissions in Genesys Cloud:]
+
* [https://help.mypurecloud.com/articles/?p=195191 Configure the following permissions in Genesys Cloud CX:]
−
**'''Architect''' > '''Flow''' > '''Search'''
+
**'''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)
 
**'''Journey''' > '''Action Map''' > '''Add''', '''Delete''', '''Edit''', and '''View'''
 
**'''Journey''' > '''Action Map''' > '''Add''', '''Delete''', '''Edit''', and '''View'''
 
|Section={{Section
 
|Section={{Section
−
|sectionHeading=Use the Architect flow action with an action map
+
|anchor=AdvancedOrchestration
−
|anchor=ArchFlowActionMap
 
 
|alignment=Horizontal
 
|alignment=Horizontal
 
|Media=Image
 
|Media=Image
−
|image=AFIconBLUE.png
+
|image=ArchFlowAction.png
−
|structuredtext={{NoteFormat|You must have the '''Architect''' > '''Flow''' > '''Search''' permission in order to select an Architect flow action for an action map.|}}
+
|structuredtext=Using the advanced orchestration flow action, you can route interactions to a [[ATC/Current/AdminGuide/Use the Architect flow with an action map#InboundMessage|specified bot or queue]] or to a [[ATC/Current/AdminGuide/Use the Architect flow with an action map#ArchFlowActionMap|third-party system]] based on the behaviour of the visitor. <br />
 +
|Status=No
 +
}}{{Section
 +
|sectionHeading=Configure an action map to use an inbound web message flow
 +
|anchor=InboundMessage
 +
|alignment=Vertical
 +
|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.
  
−
#{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_maps|display text=Build an action map}}.
+
#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.
−
#Under '''Select action''', click '''Configure'''.
+
#In the Set up an Action pane, click '''Configure Trigger Type'''.
−
#Click '''Architect flow''' and then click '''Next'''
+
#Select the advanced orchestration action and then click '''Inbound message flow'''.
−
#Select your Architect workflow and click '''Next'''.
+
#Select the required inbound message flow to route the information.
−
#{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Use_the_Architect_flow_with_an_action_map|anchor=OverrideDefaultVariables|display text=Override default variables}} with user-specific data.
+
#Click '''Done'''.
−
#Select when the Architect flow action will work.
 
−
#Click '''Finish'''.
 
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
−
|sectionHeading=Override default variables
+
|sectionHeading=Configure an action map to use an Architect flow
−
|anchor=OverrideDefaultVariables
+
|anchor=ArchFlowActionMap
−
|alignment=Horizontal
+
|alignment=Vertical
−
|Media=Image
+
|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.
−
|image=OverrideDefault.png
+
#In the Set up an Action pane, click '''Configure Trigger Type'''.
−
|structuredtext=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:
+
#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}}.
−
*{{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.
 +
#*'''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.
 +
#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 />
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 46: Line 57:
 
|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 Predictive Engagement, is the action map that uses the Architect flow action {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Activate_inactivate|display text=active}}?
+
*In {{MintyDocsProduct}}, is the action map that uses the Architect flow action {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Maintain|anchor=ChangeStatus|display text=active}}?
−
*In Genesys Cloud:
+
*In Genesys Cloud CX:
−
**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 CX integration assigned to the Architect flow action {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=PreparePCArchFlows|anchor=PCConfigure|display text=active}}?
−
**Are the Genesys Cloud data actions published?
+
**Are the Genesys Cloud CX data actions published?
 
*In Architect, is the workflow {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=BuildArchFlows|anchor=AFWorkflow|display text=saved and published}}?
 
*In Architect, is the workflow {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=BuildArchFlows|anchor=AFWorkflow|display text=saved and published}}?
 
|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-10-06 17:22:38)"
Comments or questions about this documentation? Contact us for support!