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

From Genesys Documentation
Jump to: navigation, search
(Published)
(Published)
Line 12: Line 12:
 
**'''Journey''' > '''Event Type''' > '''View''' permission (to configure an action map with an event trigger)
 
**'''Journey''' > '''Event Type''' > '''View''' permission (to configure an action map with an event trigger)
 
**'''Journey''' > '''Action Map''' > '''Add''', '''Delete''', '''Edit''', and '''View''' permissions
 
**'''Journey''' > '''Action Map''' > '''Add''', '''Delete''', '''Edit''', and '''View''' permissions
* Use {{Link-AnywhereElse|product=ATC|version=Current|manual=SDK|topic=Record|display text=ac('record')}} to send {{MINTYDOCSPRODUCT}} data about the events you want to track.
+
*The {{MINTYDOCSPRODUCT}} {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=tracking snippet must be deployed}} on the website you want to track. This enables you to trigger the action map based on pageview events.
 +
*To trigger an action map based on other events, use {{Link-AnywhereElse|product=ATC|version=Current|manual=SDK|topic=Record|display text=ac('record')}} to send {{MINTYDOCSPRODUCT}} data about events you want to track.
 
|Section={{Section
 
|Section={{Section
 
|sectionHeading=Use the Architect flow action with an action map
 
|sectionHeading=Use the Architect flow action with an action map
Line 28: Line 29:
 
#Select {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_actions_and_action_maps|anchor=ConfigOrg|display text=when the Architect flow action will work}}.
 
#Select {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_actions_and_action_maps|anchor=ConfigOrg|display text=when the Architect flow action will work}}.
 
#Click '''Finish'''.
 
#Click '''Finish'''.
 +
|structuredtextwide=
 +
|FAQHeading=
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 38: Line 41:
  
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=AFSFOverride|display text=Overrides for Salesforce Lead Creation and Campaign Attribution integration}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=AFSFOverride|display text=Overrides for Salesforce Lead Creation and Campaign Attribution integration}}
 +
|structuredtextwide=
 +
|FAQHeading=
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 52: Line 57:
 
**Are the PureCloud data actions published?
 
**Are the PureCloud 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}}?
 +
|structuredtextwide=
 +
|FAQHeading=
 
|Status=No
 
|Status=No
 
}}
 
}}
 
}}
 
}}

Revision as of 13:41, May 27, 2020

Prepare action maps to use an Architect flow action.

Prerequisites

  • Configure the following permissions in PureCloud:
    • Architect > Flow > Search permission
    • Journey > Event Type > View permission (to configure an action map with an event trigger)
    • Journey > Action Map > Add, Delete, Edit, and View permissions
  • The Genesys Predictive Engagement tracking snippet must be deployed on the website you want to track. This enables you to trigger the action map based on pageview events.
  • To trigger an action map based on other events, use ac('record') to send Genesys Predictive Engagement data about events you want to track.

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.
  1. Build an action map.
  2. Under Select action, click Configure.
  3. Click Architect flow and then click Next
  4. Select your Architect workflow and click Next.
  5. Override default variables with user-specific data.
  6. Select when the Architect flow action will work.
  7. 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 Altocloud, is the action map that uses the Architect flow action active?
  • In PureCloud:
    • Is the PureCloud integration that is assigned to the Architect flow action active?
    • Are the PureCloud data actions published?
  • In Architect, is the workflow saved and published?
Comments or questions about this documentation? Contact us for support!