Package com.pulumi.gcp.diagflow.inputs

Class CxFlowState

  • public final class CxFlowState
extends com.pulumi.resources.ResourceArgs

    • Method Detail

      • advancedSettings

        public java.util.Optional<com.pulumi.core.Output<CxFlowAdvancedSettingsArgs>> advancedSettings()
        Returns:
        Hierarchical advanced settings for this flow. 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.

      • description

        public java.util.Optional<com.pulumi.core.Output<java.lang.String>> description()
        Returns:
        The description of the flow. The maximum length is 500 characters. If exceeded, the request is rejected.

      • displayName

        public java.util.Optional<com.pulumi.core.Output<java.lang.String>> displayName()
        Returns:
        The human-readable name of the flow. ***

      • eventHandlers

        public java.util.Optional<com.pulumi.core.Output<java.util.List<CxFlowEventHandlerArgs>>> eventHandlers()
        Returns:
        A flow's event handlers serve two purposes: They are responsible for handling events (e.g. no match, webhook errors) in the flow. They are inherited by every page's [event handlers][Page.event_handlers], which can be used to handle common events regardless of the current page. Event handlers defined in the page have higher priority than those defined in the flow. Unlike transitionRoutes, these handlers are evaluated on a first-match basis. The first one that matches the event get executed, with the rest being ignored. Structure is documented below.

      • isDefaultStartFlow

        public java.util.Optional<com.pulumi.core.Output<java.lang.Boolean>> isDefaultStartFlow()
        Returns:
        Marks this as the [Default Start Flow](https://cloud.google.com/dialogflow/cx/docs/concept/flow#start) for an agent. When you create an agent, the Default Start Flow is created automatically. The Default Start Flow cannot be deleted; deleting the `gcp.diagflow.CxFlow` resource does nothing to the underlying GCP resources. > Avoid having multiple `gcp.diagflow.CxFlow` resources linked to the same agent with `is_default_start_flow = true` because they will compete to control a single Default Start Flow resource in GCP.

      • languageCode

        public java.util.Optional<com.pulumi.core.Output<java.lang.String>> languageCode()
        Returns:
        The language of the following fields in flow: Flow.event_handlers.trigger_fulfillment.messages Flow.event_handlers.trigger_fulfillment.conditional_cases Flow.transition_routes.trigger_fulfillment.messages Flow.transition_routes.trigger_fulfillment.conditional_cases If not specified, the agent's default language is used. Many languages are supported. Note: languages must be enabled in the agent before they can be used.

      • name

        public java.util.Optional<com.pulumi.core.Output<java.lang.String>> name()
        Returns:
        (Output) The unique identifier of this event handler.

      • nluSettings

        public java.util.Optional<com.pulumi.core.Output<CxFlowNluSettingsArgs>> nluSettings()
        Returns:
        NLU related settings of the flow. Structure is documented below.

      • parent

        public java.util.Optional<com.pulumi.core.Output<java.lang.String>> parent()
        Returns:
        The agent to create a flow for. Format: projects/<Project ID>/locations/<Location ID>/agents/<Agent ID>.

      • transitionRouteGroups

        public java.util.Optional<com.pulumi.core.Output<java.util.List<java.lang.String>>> transitionRouteGroups()
        Returns:
        A flow's transition route group serve two purposes: They are responsible for matching the user's first utterances in the flow. They are inherited by every page's [transition route groups][Page.transition_route_groups]. Transition route groups defined in the page have higher priority than those defined in the flow. Format:projects/<Project ID>/locations/<Location ID>/agents/<Agent ID>/flows/<Flow ID>/transitionRouteGroups/<TransitionRouteGroup ID>.

      • transitionRoutes

        public java.util.Optional<com.pulumi.core.Output<java.util.List<CxFlowTransitionRouteArgs>>> transitionRoutes()
        Returns:
        A flow's transition routes serve two purposes: They are responsible for matching the user's first utterances in the flow. They are inherited by every page's [transition routes][Page.transition_routes] and can support use cases such as the user saying "help" or "can I talk to a human?", which can be handled in a common way regardless of the current page. Transition routes defined in the page have higher priority than those defined in the flow. TransitionRoutes are evalauted in the following order: TransitionRoutes with intent specified. TransitionRoutes with only condition specified. TransitionRoutes with intent specified are inherited by pages in the flow. Structure is documented below.