Page is the Schema for the Pages API. A Dialogflow CX conversation (session) can be described and visualized as a state machine.
Type
CRD
Group
dialogflowcx.gcp.upbound.io
Version
v1beta1
apiVersion: dialogflowcx.gcp.upbound.io/v1beta1
kind: Page
PageSpec defines the desired state of Page
No description provided.
The fulfillment to call when the session is entering the page. Structure is documented below.
Handlers associated with the page to handle events such as webhook errors, no match or no input. Structure is documented below.
The fulfillment to call when the event occurs. Handling webhook errors with a fulfillment enabled with webhook could cause infinite loop. It is invalid to specify such fulfillment for a handler handling webhooks. Structure is documented below.
The form associated with the page, used for collecting parameters relevant to the page. Structure is documented below.
Parameters to collect from the user. Structure is documented below.
Defines fill behavior for the parameter. Structure is documented below.
The fulfillment to provide the initial prompt that the agent can present to the user in order to fill the parameter. Structure is documented below.
Reference to a Agent in dialogflowcx to populate parent.
Policies for referencing.
Selector for a Agent in dialogflowcx to populate parent.
Policies for selection.
Ordered list of TransitionRouteGroups associated with the page. Transition route groups must be unique within a page. If multiple transition routes within a page scope refer to the same intent, then the precedence order is: page's transition route -> page's transition route group -> flow's transition routes. If multiple transition route groups within a page contain the same intent, then the first group in the ordered list takes precedence. Format:projects//locations//agents//flows//transitionRouteGroups/.
A list of transitions for the transition rules of this page. They route the conversation to another page in the same flow, or another flow. When we are in a certain page, the TransitionRoutes are evalauted in the following order: TransitionRoutes defined in the page with intent specified. TransitionRoutes defined in the transition route groups with intent specified. TransitionRoutes defined in flow with intent specified. TransitionRoutes defined in the transition route groups with intent specified. TransitionRoutes defined in the page with only condition specified. TransitionRoutes defined in the transition route groups with only condition specified. Structure is documented below.
Reference to a Page in dialogflowcx to populate targetPage.
Policies for referencing.
Selector for a Page in dialogflowcx to populate targetPage.
Policies for selection.
The fulfillment to call when the event occurs. Handling webhook errors with a fulfillment enabled with webhook could cause infinite loop. It is invalid to specify such fulfillment for a handler handling webhooks. Structure is documented below.
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
PageStatus defines the observed state of Page.
No description provided.
The fulfillment to call when the session is entering the page. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
A collection of text responses.
Handlers associated with the page to handle events such as webhook errors, no match or no input. Structure is documented below.
The fulfillment to call when the event occurs. Handling webhook errors with a fulfillment enabled with webhook could cause infinite loop. It is invalid to specify such fulfillment for a handler handling webhooks. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
A collection of text responses.
The form associated with the page, used for collecting parameters relevant to the page. Structure is documented below.
Parameters to collect from the user. Structure is documented below.
Defines fill behavior for the parameter. Structure is documented below.
The fulfillment to provide the initial prompt that the agent can present to the user in order to fill the parameter. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
A collection of text responses.
A list of transitions for the transition rules of this page. They route the conversation to another page in the same flow, or another flow. When we are in a certain page, the TransitionRoutes are evalauted in the following order: TransitionRoutes defined in the page with intent specified. TransitionRoutes defined in the transition route groups with intent specified. TransitionRoutes defined in flow with intent specified. TransitionRoutes defined in the transition route groups with intent specified. TransitionRoutes defined in the page with only condition specified. TransitionRoutes defined in the transition route groups with only condition specified. Structure is documented below.
The fulfillment to call when the event occurs. Handling webhook errors with a fulfillment enabled with webhook could cause infinite loop. It is invalid to specify such fulfillment for a handler handling webhooks. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
A collection of text responses.
Conditions of the resource.
page
apiVersion: dialogflowcx.gcp.upbound.io/v1beta1
kind: Page
metadata:
annotations:
meta.upbound.io/example-id: dialogflowcx/v1beta1/page
labels:
testing.upbound.io/example-name: page
name: page
spec:
forProvider:
displayName: MyPage
entryFulfillment:
- messages:
- text:
- text:
- Welcome to page
form:
- parameters:
- displayName: param1
entityType: projects/-/locations/-/agents/-/entityTypes/sys.date
fillBehavior:
- initialPromptFulfillment:
- messages:
- text:
- text:
- Please provide param1
redact: true
required: true
parentSelector:
matchLabels:
testing.upbound.io/example-name: page
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.