Difference between revisions of "ATC/Current/AdminGuide/MonitorArchFlows"
From Genesys Documentation
m (Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2") |
(Published) |
||
| Line 5: | Line 5: | ||
|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. | ||
|ComingSoon=No | |ComingSoon=No | ||
| − | |Platform=GenesysEngage-cloud | + | |Platform=PureConnect, GenesysCloud, GenesysEngage-cloud |
|Prereq='''Prerequisites''' | |Prereq='''Prerequisites''' | ||
*[https://help.mypurecloud.com/articles/altocloud-permissions-overview Configure the following permissions in Genesys Cloud:] | *[https://help.mypurecloud.com/articles/altocloud-permissions-overview Configure the following permissions in Genesys Cloud:] | ||
| − | **'''Journey '''> ''' Report''' > '''View''' | + | **'''Journey '''> ''' Report''' > '''View''' |
**'''Journey '''>''' Action Map '''> '''View''' (to see action maps in the report) | **'''Journey '''>''' Action Map '''> '''View''' (to see action maps in the report) | ||
|Section={{Section | |Section={{Section | ||
| Line 15: | Line 15: | ||
|anchor=MonitorArchFlow | |anchor=MonitorArchFlow | ||
|alignment=Vertical | |alignment=Vertical | ||
| − | |||
| − | |||
|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 31: | Line 29: | ||
{{!}}- | {{!}}- | ||
{{!}} style="width: 219.953px;"{{!}}'''Web Actions Accepted''' | {{!}} style="width: 219.953px;"{{!}}'''Web Actions Accepted''' | ||
| − | {{!}} style="width: 961.047px;"{{!}}Number of times the Architect flow connected with the third-party product | + | {{!}} style="width: 961.047px;"{{!}}Number of times that the Architect flow connected with the third-party product starts. |
{{!}}- | {{!}}- | ||
{{!}} style="width: 219.953px;"{{!}}'''Web Actions Started''' | {{!}} style="width: 219.953px;"{{!}}'''Web Actions Started''' | ||
| Line 40: | Line 38: | ||
{{!}}- | {{!}}- | ||
{{!}} style="width: 219.953px;"{{!}}'''Web Actions Rejected''' | {{!}} style="width: 219.953px;"{{!}}'''Web Actions Rejected''' | ||
| − | {{!}} style="width: 961.047px;"{{!}}Number of times Genesys Cloud rejected the Architect flow's request because the request was wrong. | + | {{!}} style="width: 961.047px;"{{!}}Number of times that Genesys Cloud rejected the Architect flow's request because the request was wrong. The rejection can occur in the following scenarios: |
| − | * | + | *Architect flow no longer exists. |
| − | * | + | *Data required to launch the Architect flow wasn't provided. |
| − | * | + | *Action map is firing intensively and exceeding the Genesys Cloud rate limits (more than 15 requests/second). Requests aren't retried once the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_actions_and_action_maps|anchor=Throttling|display text=throttling}} threshold is exceeded. |
{{!}}- | {{!}}- | ||
{{!}} style="width: 219.953px;"{{!}}'''Web Actions Errored''' | {{!}} style="width: 219.953px;"{{!}}'''Web Actions Errored''' | ||
| Line 52: | Line 50: | ||
{{!}} style="width: 961.047px;"{{!}}Not applicable. | {{!}} style="width: 961.047px;"{{!}}Not applicable. | ||
{{!}}} | {{!}}} | ||
| − | |||
| − | |||
|Status=No | |Status=No | ||
}} | }} | ||
}} | }} | ||
Revision as of 14:02, October 29, 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
- Configure the following permissions in Genesys Cloud:
- Journey > Report > View
- Journey > Action Map > View (to see action maps in the report)
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 that the Architect flow connected with the third-party product starts. |
| Web Actions Started | Not applicable. |
| Web Actions Engaged | Not applicable. |
| Web Actions Rejected | Number of times that Genesys Cloud rejected the Architect flow's request because the request was wrong. The rejection can occur in the following scenarios:
|
| Web Actions Errored | Number of times the web action request resulted in an error. |
| Web Actions Timed out | Not applicable. |
Comments or questions about this documentation? Contact us for support!