Class: Google::Apis::DialogflowV3::GoogleCloudDialogflowCxV3TransitionCoverageTransitionNode

Inherits:
Object
  • Object
show all
Includes:
Core::Hashable, Core::JsonObjectSupport
Defined in:
lib/google/apis/dialogflow_v3/classes.rb,
lib/google/apis/dialogflow_v3/representations.rb,
lib/google/apis/dialogflow_v3/representations.rb

Overview

The source or target of a transition.

Instance Attribute Summary collapse

Instance Method Summary collapse

Constructor Details

#initialize(**args) ⇒ GoogleCloudDialogflowCxV3TransitionCoverageTransitionNode

Returns a new instance of GoogleCloudDialogflowCxV3TransitionCoverageTransitionNode.



7787
7788
7789
 
# File 'lib/google/apis/dialogflow_v3/classes.rb', line 7787

def initialize(**args)
   update!(**args)
end

Instance Attribute Details

#flow ⇒ Google::Apis::DialogflowV3::GoogleCloudDialogflowCxV3Flow

Flows represents the conversation flows when you build your chatbot agent. A flow consists of many pages connected by the transition routes. Conversations always start with the built-in Start Flow (with an all-0 ID). Transition routes can direct the conversation session from the current flow (parent flow) to another flow (sub flow). When the sub flow is finished, Dialogflow will bring the session back to the parent flow, where the sub flow is started. Usually, when a transition route is followed by a matched intent, the intent will be "consumed". This means the intent won't activate more transition routes. However, when the followed transition route moves the conversation session into a different flow, the matched intent can be carried over and to be consumed in the target flow. Corresponds to the JSON property flow

Returns:



7769
7770
7771
 
# File 'lib/google/apis/dialogflow_v3/classes.rb', line 7769

def flow
  @flow
end

#page ⇒ Google::Apis::DialogflowV3::GoogleCloudDialogflowCxV3Page

A Dialogflow CX conversation (session) can be described and visualized as a state machine. The states of a CX session are represented by pages. For each flow, you define many pages, where your combined pages can handle a complete conversation on the topics the flow is designed for. At any given moment, exactly one page is the current page, the current page is considered active, and the flow associated with that page is considered active. Every flow has a special start page. When a flow initially becomes active, the start page page becomes the current page. For each conversational turn, the current page will either stay the same or transition to another page. You configure each page to collect information from the end-user that is relevant for the conversational state represented by the page. For more information, see the Page guide. Corresponds to the JSON property page

Returns:



7785
7786
7787
 
# File 'lib/google/apis/dialogflow_v3/classes.rb', line 7785

def page
  @page
end

Instance Method Details

#update!(**args) ⇒ Object

Update properties of this object



7792
7793
7794
7795
 
# File 'lib/google/apis/dialogflow_v3/classes.rb', line 7792

def update!(**args)
  @flow = args[:flow] if args.key?(:flow)
  @page = args[:page] if args.key?(:page)
end