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.
Hierarchical advanced settings for this page. The settings exposed at the lower level overrides the settings exposed at the higher level. Hierarchy: Agent->Flow->Page->Fulfillment/Parameter. Structure is documented below.
Define behaviors for DTMF (dual tone multi frequency). DTMF settings does not override each other. DTMF settings set at different levels define DTMF detections running in parallel. Exposed at the following levels:
The fulfillment to call when the session is entering the page. Structure is documented below.
Conditional cases for this fulfillment. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example:
Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example:
Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. 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.
Conditional cases for this fulfillment. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example:
Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example:
Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. 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.
Hierarchical advanced settings for this parameter. The settings exposed at the lower level overrides the settings exposed at the higher level. Hierarchy: Agent->Flow->Page->Fulfillment/Parameter. Structure is documented below.
Define behaviors for DTMF (dual tone multi frequency). DTMF settings does not override each other. DTMF settings set at different levels define DTMF detections running in parallel. Exposed at the following levels:
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.
Conditional cases for this fulfillment. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example:
Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example:
Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. Structure is documented below.
The handlers for parameter-level events, used to provide reprompt for the parameter or transition to a different page/flow. The supported events are:
Reference to a Agent in dialogflowcx to populate targetFlow.
Policies for referencing.
Selector for a Agent in dialogflowcx to populate targetFlow.
Policies for selection.
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 condition is satisfied. At least one of triggerFulfillment and target must be specified. When both are defined, triggerFulfillment is executed first. Structure is documented below.
Conditional cases for this fulfillment. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example:
Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example:
Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. Structure is documented below.
Reference to a Webhook in dialogflowcx to populate webhook.
Policies for referencing.
Selector for a Webhook in dialogflowcx to populate webhook.
Policies for selection.
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 condition is satisfied. At least one of triggerFulfillment and target must be specified. When both are defined, triggerFulfillment is executed first. Structure is documented below.
Conditional cases for this fulfillment. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example:
Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example:
Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. Structure is documented below.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
Hierarchical advanced settings for this page. The settings exposed at the lower level overrides the settings exposed at the higher level. Hierarchy: Agent->Flow->Page->Fulfillment/Parameter. Structure is documented below.
Define behaviors for DTMF (dual tone multi frequency). DTMF settings does not override each other. DTMF settings set at different levels define DTMF detections running in parallel. Exposed at the following levels:
The fulfillment to call when the session is entering the page. Structure is documented below.
Conditional cases for this fulfillment. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example:
Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example:
Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. 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.
Conditional cases for this fulfillment. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example:
Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example:
Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. 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.
Hierarchical advanced settings for this parameter. The settings exposed at the lower level overrides the settings exposed at the higher level. Hierarchy: Agent->Flow->Page->Fulfillment/Parameter. Structure is documented below.
Define behaviors for DTMF (dual tone multi frequency). DTMF settings does not override each other. DTMF settings set at different levels define DTMF detections running in parallel. Exposed at the following levels:
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.
Conditional cases for this fulfillment. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example:
Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example:
Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. Structure is documented below.
The handlers for parameter-level events, used to provide reprompt for the parameter or transition to a different page/flow. The supported events are:
Reference to a Agent in dialogflowcx to populate targetFlow.
Policies for referencing.
Selector for a Agent in dialogflowcx to populate targetFlow.
Policies for selection.
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 condition is satisfied. At least one of triggerFulfillment and target must be specified. When both are defined, triggerFulfillment is executed first. Structure is documented below.
Conditional cases for this fulfillment. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example:
Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example:
Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. Structure is documented below.
Reference to a Webhook in dialogflowcx to populate webhook.
Policies for referencing.
Selector for a Webhook in dialogflowcx to populate webhook.
Policies for selection.
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 condition is satisfied. At least one of triggerFulfillment and target must be specified. When both are defined, triggerFulfillment is executed first. Structure is documented below.
Conditional cases for this fulfillment. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example:
Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example:
Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. Structure is documented below.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
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.
Hierarchical advanced settings for this page. The settings exposed at the lower level overrides the settings exposed at the higher level. Hierarchy: Agent->Flow->Page->Fulfillment/Parameter. Structure is documented below.
Define behaviors for DTMF (dual tone multi frequency). DTMF settings does not override each other. DTMF settings set at different levels define DTMF detections running in parallel. Exposed at the following levels:
The fulfillment to call when the session is entering the page. Structure is documented below.
Conditional cases for this fulfillment. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example:
Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example:
A text or ssml response that is preferentially used for TTS output audio synthesis, as described in the comment on the ResponseMessage message. Structure is documented below.
Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. Structure is documented below.
A collection of text responses.
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.
Conditional cases for this fulfillment. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example:
Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example:
A text or ssml response that is preferentially used for TTS output audio synthesis, as described in the comment on the ResponseMessage message. Structure is documented below.
Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. Structure is documented below.
A collection of text responses.
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.
Hierarchical advanced settings for this parameter. The settings exposed at the lower level overrides the settings exposed at the higher level. Hierarchy: Agent->Flow->Page->Fulfillment/Parameter. Structure is documented below.
Define behaviors for DTMF (dual tone multi frequency). DTMF settings does not override each other. DTMF settings set at different levels define DTMF detections running in parallel. Exposed at the following levels:
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.
Conditional cases for this fulfillment. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example:
Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example:
A text or ssml response that is preferentially used for TTS output audio synthesis, as described in the comment on the ResponseMessage message. Structure is documented below.
Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. Structure is documented below.
A collection of text responses.
A collection of text responses.
The handlers for parameter-level events, used to provide reprompt for the parameter or transition to a different page/flow. The supported events are:
The fulfillment to call when the condition is satisfied. At least one of triggerFulfillment and target must be specified. When both are defined, triggerFulfillment is executed first. Structure is documented below.
Conditional cases for this fulfillment. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example:
Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example:
A text or ssml response that is preferentially used for TTS output audio synthesis, as described in the comment on the ResponseMessage message. Structure is documented below.
Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. Structure is documented below.
A collection of text responses.
A collection of text responses.
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.
The fulfillment to call when the condition is satisfied. At least one of triggerFulfillment and target must be specified. When both are defined, triggerFulfillment is executed first. Structure is documented below.
Conditional cases for this fulfillment. Structure is documented below.
The list of rich message responses to present to the user. Structure is documented below.
Indicates that the conversation succeeded, i.e., the bot handled the issue that the customer talked to it about. Dialogflow only uses this to determine which conversations should be counted as successful and doesn't process the metadata in this message in any way. Note that Dialogflow also considers conversations that get to the conversation end page as successful even if they don't return ConversationSuccess. You may set this, for example:
Indicates that the conversation should be handed off to a live agent. Dialogflow only uses this to determine which conversations were handed off to a human agent for measurement purposes. What else to do with this signal is up to you and your handoff procedures. You may set this, for example:
A text or ssml response that is preferentially used for TTS output audio synthesis, as described in the comment on the ResponseMessage message. Structure is documented below.
Specifies an audio clip to be played by the client as part of the response. Structure is documented below.
Represents the signal that telles the client to transfer the phone call connected to the agent to a third-party endpoint. Structure is documented below.
A collection of text responses.
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.