User Guide
API DOCSVOICE GATEWAYHELPSECURITY
Current Version
Current Version
  • Welcome
  • What's New
  • 🚀GETTING STARTED
    • Login
    • Concepts and Glossary
    • Language Models
      • Syntphony NLP
      • Other NLP and LLM Connectors
      • FAQs
    • Build a Virtual Agent
      • Overview
      • From Scratch
      • By Importing
      • Pre-Built Templates
      • Training task
    • Testing
      • Automated Test
      • Advanced Request
      • Simulate Dialog
      • View Logs
    • Create and manage profiles
  • 💬BUILD DIALOGS
    • Flows
    • Dialog Cells
      • Intent
      • Entity
      • Answer
      • Input
      • Jump
      • End
      • Service
      • Rest Connector
      • Code
      • Rule
        • Variable answers using Code and Rule cells
        • Enable and disable flows using Rule Cells
    • Data Masking of Personal Identificable Information
    • Dynamic Content and Contexts
    • Voice Agent
    • Multilingual Agent (beta)
  • ✨GENERATIVE AI
    • AI features
    • Assist Answer (beta)
    • Examples Generator
    • Knowledge AI
    • Prompt cell
      • Prompt crafting
      • Practical examples
    • Rephrase Answer
    • Zero-Shot LLM
  • 🌐CHANNELS
    • Channels
      • WhatsApp (by Infobip)
      • Facebook Messenger
      • Microsoft Teams
      • Integrating Existing Channels
    • Webchat Plugin
  • ⚙️CONFIGURATIONS
    • Parameters
    • Advanced Resources
    • Other Options
      • Intent Navigator
  • 📊ANALYTICS & INSIGHTS
    • Dashboards
      • Overview
      • Funnel charts
      • User messages
      • Conversations
      • Reports
    • External Analytics Platforms
  • API DOCS
    • Overview
    • API Guidelines
      • Conversation API
      • Cloner API
      • EVG Connector
      • Management API
        • Admin API
          • Bot Admin
          • Environment
          • Organization
          • User
          • Notification
        • Instance API
          • Knowledge AI
          • Knowledge AI NLP
          • Answer
          • Automated Tests
          • Bot
          • Broker
          • Channel
          • Dashboard
          • Dialog Manager
          • Entity
          • Generative Service
          • Intent
          • Parameters
          • Tag
          • Technical Log
          • Training
          • Transactional Service
          • Rest Connector
          • Wait Input
          • Websnippet
      • Webhooks
    • Infrastructure Guidelines
      • Syntphony CAI server Installation guide
      • Maintenance Methods
      • Supported/verified third-party software
    • Data Structure
      • Admin Data Structure
      • Environment Data Structure
    • Voice Gateway
      • Genesys Cloud CX
Powered by GitBook
On this page
  • Manually toggling your flows
  • Branching paths
  • Automatically toggling your flows with your API

Was this helpful?

  1. BUILD DIALOGS
  2. Dialog Cells
  3. Rule

Enable and disable flows using Rule Cells

PreviousVariable answers using Code and Rule cellsNextData Masking of Personal Identificable Information

Last updated 8 months ago

Was this helpful?

Another good use of Rule cells is to branch, enable or disable specific flows or part of flows. See the scenarios below to better understand:

: when you want to branch, in a single flow, which path each customer will follow, without having to edit your whole flow structure.

: when you want your flow to be available only for a specific group of users

: to switch on/off a flow (seasonal or promotional flows, for example).

For these scenarios, we can combine the use of Code, Service and Rule cells. Let's break down each case below.

Manually toggling your flows

You may want to manually disable a flow during a specific period. Rather than updating your flows, by adding or removing cells, or even changing their connections, we recommend the use of a Rule cell with a custom variable.

Add a right before your branching paths, or at the beginning of your virtual agent in your Welcome flow, if you want to use this same variable in several places, with a availability variable, such as:

hiddenContext.yourVariable = false;

Or true if you want to enable it:

hiddenContext.yourVariable = true;

See in the image below how the flow was built to branch between a path for a transactional or an informational flow. In this scenario it was used (true) to enable the transactional flow and (false) to disable it:

You may use any number of variables for any number of paths you want to possibly block by different parameters.

Branching paths

hiddenContext.yourVariable == true

This will enter into the branching path you want to access only periodically. If the specified variable is false, you'll fallback into a not expected answer, so you might also want to add a fallback rule (yourVariable == false) and add an answer cell with a message about this functionality unavailability.

You may also use the virtual agent parameter, or even an environment parameter, rather than a Code cell, to toggle which path will be taken bot-wide or environment-wide.

Automatically toggling your flows with your API

Open a with the following evaluation:

If you want to custom a time frame, such as disabling a few operations between 0am and 5am, for example, have a user-specific flow, or any more advanced branching path for flows based on an external variable, you may instead implement your own API and use a , setting a variable as true or false immediately before executing the Rule Cell and evaluating it.

💬
Rule Cell
Service Cell
Code Cell
Case 1
Case 2
Case 3