SmartbotPro
  • Smartbot Pro – messenger marketing tool
  • Most important
  • Mini-course
    • Registration and personal account
    • Initial scripting tools
    • Creating the first script
    • Users and collection of information
    • Applications, variables and managers
    • Data validation
    • Collection of applications for a webinar within Telegram
    • Testing unpublished scripts
    • Newsletters
    • Template "Test with a set of points"
    • Statistics
    • Interface hacks
  • Beginning of work
    • Registration in the service
    • More about scripts
    • How to add messenger
      • Adding Telegram
        • Adding a bot to a group chat in Telegram
      • Adding ВК
      • Adding Viber
      • Connecting a channel to a script
      • Linking a social network account
  • Scripts
    • Basics
      • Create a script
      • Script templates
      • Editor interface
      • Publishing a script
      • Script testing
      • How the script is chosen
    • Script events
      • Message from user
      • No appropriate script
      • First message
      • VK Events
      • Webhook
    • Actions
      • Send a message
        • Buttons
      • Process message
      • Extract data
      • Change context
      • Write to statistics
      • Send Notification
      • Switching to another script
      • Working with the user
      • Set variable
      • Scheduled transitions
      • Run SmartQuery
    • Conditions
      • Condition
      • Condition with options
      • Conditions of VKontakte
    • Variables
      • Special Variables
      • User variables
      • Global variables
      • Variable %ref%
    • Acceptance of payment
    • Telegram bot menu
    • Integrations
      • Google-таблицы
      • http request
      • amoCRM
      • Get Course
      • Yukassa for receiving payments
    • Reactions
  • Newsletters
  • Settings
    • Projects
    • Cabinets
  • Information sections
    • Statistics
    • Users
  • SmartQuery
    • Introduction
    • Language syntax
    • Function Reference
  • The documents
    • Privacy Policy
    • Terms of service
    • Subscription and rates
Powered by GitBook
On this page
  1. Mini-course

Testing unpublished scripts

PreviousCollection of applications for a webinar within TelegramNextNewsletters

Last updated 2 years ago

You can test different changes in the project without fear of breaking existing logic.

For example, you have several thousand customers using a bot. You need to make changes, but in a way that doesn't break the current script. For this, there is a draft and a clean draft of the project - the published and unpublished versions.

Pay attention to script cards:

On the notes with yellow dies, the status is written: “not published”, “there are unpublished changes”.

Below is written about inclusion in the published and unpublished versions of the project. This is done so that you can test new features of the bot when the previous one is already active.

Let's look at an example. I can change the message that the bot sends to the user in response to /star. Previously, the first line was written: "Hello!" I changed those words to "How do you do?"

If I write /start to the bot, I will see a new message:

To understand why this happens, let's look at the project settings. Now everything is clear:

Since I am a confirmed bot admin, I communicate with the unpublished version of the project. If you change this setting, the bot will respond to me in the same way as other users. You can also turn off a specific script in the published or unpublished versions: