Events - Revision history

Admin at 13:53, 18 November 2019

2019-11-18T13:53:42Z

Admin at 13:53, 18 November 2019

2019-11-18T13:53:32Z

Admin at 13:53, 18 November 2019

2019-11-18T13:53:14Z

Admin at 13:51, 18 November 2019

2019-11-18T13:51:26Z

Admin at 13:51, 18 November 2019

2019-11-18T13:51:19Z

Admin at 13:50, 18 November 2019

2019-11-18T13:50:45Z

Admin: Created page with "Event are entry points for the flow. They can only be created using the "Create Event" button. Event.png:300px:http://wiki.wisevoice.ai Events received from API calls can..."

2019-11-18T13:50:14Z

Created page with "Event are entry points for the flow. They can only be created using the "Create Event" button. Event.png:300px:http://wiki.wisevoice.ai Events received from API calls can..."

New page

Event are entry points for the flow. They can only be created using the "Create Event" button.
[[Event.png:300px:http://wiki.wisevoice.ai]]
Events received from API calls can also contain custom data that will be inserted in the user's session.
Events can either start a new conversation or interrupt an existing conversation.
For example inside a conversation we can use a service to launch an UiPath job. When the job is finished it will trigger an UiPath event passing it the result data. By connecting a message to the UiPath event we can display the results of the job in the ongoing conversation.

The Event types supported at the moment are:
*Start - triggered when the user opens the chat or calls the virtual agent
*REST - triggered via API called by the business logic server
*UiPath - triggered by a UiPath component
*Consecutive error number exceeded - triggered when the agent passes a predefined number of consecutive unrecognized intents from the user input
*Time - triggered at a certain date and time; also supports recurring events
*Time from start - triggered after an interval from the first user interaction (e.g. one day after the first interaction); also supports recurring events and setting an hour of day
*Inactivity - triggered after an interval from the last user interaction (e.g. one day after the first interaction); also supports recurring events and setting an hour of day
*Call Finished -triggered when a sip call was finished

← Older revision		Revision as of 13:53, 18 November 2019
Line 6:		Line 6:
	For example inside a conversation we can use a service to launch an UiPath job. When the job is finished it will trigger an UiPath event passing it the result data. By connecting a message to the UiPath event we can display the results of the job in the ongoing conversation.		For example inside a conversation we can use a service to launch an UiPath job. When the job is finished it will trigger an UiPath event passing it the result data. By connecting a message to the UiPath event we can display the results of the job in the ongoing conversation.

−	[[File:Event.png\|~~300px~~]]	+	[[File:Event.png\|600px]]

← Older revision		Revision as of 13:53, 18 November 2019
Line 6:		Line 6:
	For example inside a conversation we can use a service to launch an UiPath job. When the job is finished it will trigger an UiPath event passing it the result data. By connecting a message to the UiPath event we can display the results of the job in the ongoing conversation.		For example inside a conversation we can use a service to launch an UiPath job. When the job is finished it will trigger an UiPath event passing it the result data. By connecting a message to the UiPath event we can display the results of the job in the ongoing conversation.

−	[[Event.png\|300px]]	+	[[File:Event.png\|300px]]

← Older revision		Revision as of 13:53, 18 November 2019
Line 6:		Line 6:
	For example inside a conversation we can use a service to launch an UiPath job. When the job is finished it will trigger an UiPath event passing it the result data. By connecting a message to the UiPath event we can display the results of the job in the ongoing conversation.		For example inside a conversation we can use a service to launch an UiPath job. When the job is finished it will trigger an UiPath event passing it the result data. By connecting a message to the UiPath event we can display the results of the job in the ongoing conversation.

−	[[~~Events~~.png\|300px~~\|link=http://wiki.wisevoice.ai~~]]	+	[[Event.png\|300px]]

← Older revision		Revision as of 13:51, 18 November 2019
Line 6:		Line 6:
	For example inside a conversation we can use a service to launch an UiPath job. When the job is finished it will trigger an UiPath event passing it the result data. By connecting a message to the UiPath event we can display the results of the job in the ongoing conversation.		For example inside a conversation we can use a service to launch an UiPath job. When the job is finished it will trigger an UiPath event passing it the result data. By connecting a message to the UiPath event we can display the results of the job in the ongoing conversation.

−	[[~~Event~~.png\|300px\|link=http://wiki.wisevoice.ai]]	+	[[Events.png\|300px\|link=http://wiki.wisevoice.ai]]

← Older revision		Revision as of 13:51, 18 November 2019
Line 6:		Line 6:
	For example inside a conversation we can use a service to launch an UiPath job. When the job is finished it will trigger an UiPath event passing it the result data. By connecting a message to the UiPath event we can display the results of the job in the ongoing conversation.		For example inside a conversation we can use a service to launch an UiPath job. When the job is finished it will trigger an UiPath event passing it the result data. By connecting a message to the UiPath event we can display the results of the job in the ongoing conversation.

−	[[Event.png\|300px\|http://wiki.wisevoice.ai]]	+	[[Event.png\|300px\|link=http://wiki.wisevoice.ai]]

@@ Line 1: / Line 1: @@
 Event are entry points for the flow. They can only be created using the "Create Event" button.
-[[Event.png:300px:http://wiki.wisevoice.ai]]
 Events received from API calls can also contain custom data that will be inserted in the user's session.
 Events can either start a new conversation or interrupt an existing conversation.
 For example inside a conversation we can use a service to launch an UiPath job. When the job is finished it will trigger an UiPath event passing it the result data. By connecting a message to the UiPath event we can display the results of the job in the ongoing conversation.
 The Event types supported at the moment are: