reports

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
reports [2019/01/03 15:54]
admin
reports [2019/01/03 15:55] (current)
admin
Line 52: Line 52:
  
  
-\\ For Fuse+ applicatons. VoiceTrends will automatically use the module name as part of the report on showing the statics on the common call path. It is important to name each module with unique names so that they can be better identified in the VoiceTrends diagnostic flow reports.+===Naming=== 
 +For Fuse+ applicatons. VoiceTrends will automatically use the module name as part of the report on showing the statics on the common call path. It is important to name each module with unique names so that they can be better identified in the VoiceTrends diagnostic flow reports.
  
 +
 +===Branching===
 In addition, VoiceTrends will only differentiate between the //type// of response that the caller (filled, no input, no match) but not the actual //​**value**//​ of the response (such as 1 for yes vs 2 for no). If the value of the response is not private and is needed to be shown in VoiceTrends,​ then each differing response should branch out to a different module (such as a [[:​modules:​call-logs|log]] module), so that the separate paths can be separated out in the report. In addition, VoiceTrends will only differentiate between the //type// of response that the caller (filled, no input, no match) but not the actual //​**value**//​ of the response (such as 1 for yes vs 2 for no). If the value of the response is not private and is needed to be shown in VoiceTrends,​ then each differing response should branch out to a different module (such as a [[:​modules:​call-logs|log]] module), so that the separate paths can be separated out in the report.
  
reports.txt · Last modified: 2019/01/03 15:55 by admin