From d24fdf6d1041ccd8239306fc8315679401bcf81c Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Sat, 6 Jul 2024 12:35:43 +0000 Subject: [PATCH] Update content of files --- data/web/corefork.telegram.org/api/business.html | 1 + .../constructor/businessBotRecipients.html | 2 +- .../constructor/inputBusinessBotRecipients.html | 2 +- 3 files changed, 3 insertions(+), 2 deletions(-) diff --git a/data/web/corefork.telegram.org/api/business.html b/data/web/corefork.telegram.org/api/business.html index dff1c68661..b55ebb142d 100644 --- a/data/web/corefork.telegram.org/api/business.html +++ b/data/web/corefork.telegram.org/api/business.html @@ -326,6 +326,7 @@ Use account.updateConnectedBot »account.getConnectedBots » list all currently connected business bots.

Use account.toggleConnectedBotPaused » to pause or unpause a specific chat, temporarily disconnecting it from all business bots (equivalent to temporarily specifying it in recipients.exclude_users during initial configuration with account.updateConnectedBot »).
Use account.disablePeerConnectedBot » to permanently disconnect a specific chat from all business bots (equivalent to specifying it in recipients.exclude_users during initial configuration with account.updateConnectedBot »); to reconnect of a chat disconnected using this method the user must reconnect the entire bot by invoking account.updateConnectedBot ».

+

Note that invoking the above two methods will also add the peer to the recipients.exclude_users field of the related connectedBot (or to recipients.users, if the inversion recipients.exclude_selected flag is set).

The above two methods should be invoked when pressing the appropriate buttons in the action bar, see here » for more info on the business bot action bar that should be displayed on all peers currently managed by the bot, according to the action bar flags ».

Connecting or disconnecting a business bot or changing the connection settings will emit an updateBotBusinessConnect update to the bot, with the new settings and a connection_id that will be used by the bot to handle updates from and send messages as the user.

According to the specified settings, the bot will start receiving updateBotNewBusinessMessage, updateBotEditBusinessMessage, updateBotDeleteBusinessMessage updates containing messages sent to the connected user via the business connection.

diff --git a/data/web/corefork.telegram.org/constructor/businessBotRecipients.html b/data/web/corefork.telegram.org/constructor/businessBotRecipients.html index 2666bff323..3ed1eb8c72 100644 --- a/data/web/corefork.telegram.org/constructor/businessBotRecipients.html +++ b/data/web/corefork.telegram.org/constructor/businessBotRecipients.html @@ -94,7 +94,7 @@ exclude_selected flags.5?true -If set, then all private chats except the selected ones are chosen. Otherwise, only the selected chats are chosen. +If set, then all private chats except the ones selected by existing_chats, new_chats, contacts, non_contacts and users are chosen.
Note that if this flag is set, any values passed in exclude_users will be merged and moved into users by the server, thus exclude_users will always be empty. users diff --git a/data/web/corefork.telegram.org/constructor/inputBusinessBotRecipients.html b/data/web/corefork.telegram.org/constructor/inputBusinessBotRecipients.html index a7639d6ad3..065917a4a7 100644 --- a/data/web/corefork.telegram.org/constructor/inputBusinessBotRecipients.html +++ b/data/web/corefork.telegram.org/constructor/inputBusinessBotRecipients.html @@ -94,7 +94,7 @@ exclude_selected flags.5?true -If set, then all private chats except the selected ones are chosen. Otherwise, only the selected chats are chosen. +If set, then all private chats except the ones selected by existing_chats, new_chats, contacts, non_contacts and users are chosen.
Note that if this flag is set, any values passed in exclude_users will be merged and moved into users by the server. users