Difference between revisions of "ATC/Current/AdminGuide/MonitorArchFlows"

From Genesys Documentation
Jump to: navigation, search
(Published)
 
(Published)
Line 4: Line 4:
 
|TocName=Monitor
 
|TocName=Monitor
 
|Context=Monitor an action map that uses an Architect flow action to evaluate how well it's working.
 
|Context=Monitor an action map that uses an Architect flow action to evaluate how well it's working.
 +
|Dimension=
 +
|UseCase=
 
|ComingSoon=No
 
|ComingSoon=No
 
|Platform=PureEngage, PureConnect, PureCloud
 
|Platform=PureEngage, PureConnect, PureCloud
 +
|Role=
 +
|Application=
 
|Prereq='''Prerequisites'''
 
|Prereq='''Prerequisites'''
  
Line 12: Line 16:
 
**'''Journey '''>''' Action Map '''> '''View''' permission (to see action maps in the report)
 
**'''Journey '''>''' Action Map '''> '''View''' permission (to see action maps in the report)
 
|Section={{Section
 
|Section={{Section
−
|sectionHeading=Monitor an Architect flow actions performance
+
|sectionHeading=Monitor an Architect flow action's performance
 
|anchor=MonitorArchFlow
 
|anchor=MonitorArchFlow
 
|alignment=Vertical
 
|alignment=Vertical
 +
|Media=
 +
|image=
 
|structuredtext=Use the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_Map_Performance}} to monitor your Architect flow action's performance. When you create an action map that uses an Architect flow action, the metric names have different meanings.<font color="#ff0000"></font>
 
|structuredtext=Use the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_Map_Performance}} to monitor your Architect flow action's performance. When you create an action map that uses an Architect flow action, the metric names have different meanings.<font color="#ff0000"></font>
 
{{{!}} class="wikitable" style="width: 1205px;"
 
{{{!}} class="wikitable" style="width: 1205px;"
Line 50: Line 56:
 
{{!}} style="width: 961.047px;"{{!}}Not applicable.
 
{{!}} style="width: 961.047px;"{{!}}Not applicable.
 
{{!}}}
 
{{!}}}
 +
|structuredtextwide=
 +
|FAQHeading=
 
|Status=No
 
|Status=No
 
}}
 
}}
 
}}
 
}}

Revision as of 19:58, April 14, 2020

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

Monitor an action map that uses an Architect flow action to evaluate how well it's working.

Prerequisites

Monitor an Architect flow action's performance

Use the Action map performance to monitor your Architect flow action's performance. When you create an action map that uses an Architect flow action, the metric names have different meanings.

Metric Description
Web Actions Qualified Number of visitors who matched a segment, activity, or outcome score that triggered the action map.
Web Actions Offered Not applicable.
Web Actions Accepted Number of times the Architect flow connected with the third-party product is initiated.
Web Actions Started Not applicable.
Web Actions Engaged Not applicable.
Web Actions Rejected Number of times PureCloud rejected the Architect flow's request because the request was wrong. This can happen because of two possible scenarios:
  • The Architect flow no longer exists.
  • The data required to launch the Architect flow has not been provided.
  • The action map is firing intensively and exceeding the PureCloud rate limits (more than 15 requests/second). Requests will not be retried once the throttling threshold is exceeded.
Web Actions Errored Number of times the web action request resulted in an error.
Web Actions Timed out Not applicable.
Retrieved from "https://all.docs.genesys.com/ATC/Current/AdminGuide/MonitorArchFlows (2025-06-22 15:43:46)"
Comments or questions about this documentation? Contact us for support!