March 2018

• New method bizproc.workflow.instance.list was added to retrieve a list of launched Workflows.
  
  
• New method bizproc.workflow.terminate - stops an active Workflow.
  
  
• New method bizproc.workflow.start - launches a Workflow.
  
  
• New method bizproc.workflow.template.list - returns a list of Workflow templates, installed on the site.
  
  
• New method lists_element_get_file_url was added for getting a path to files for elements of universal lists.
  
  
• Important! Length of OAuth 2.0 authorization tokens was increased to 70 symbols 
  
  
• An error in the method crm.product.property.get was corrected. Due to this error, values of "List" property type were not returned.
  
  
• Events for product properties (no description, get the list of method names at events).
  
  
• REST methods were added for Face Identification.

February 2018

• The following fields: EVENT_MESSAGE_UPDATE and EVENT_MESSAGE_DELETE were added to the methods imbot.register and imbot.update to enable subscription to events that update and delete messages.
• The following fields: EVENT_MESSAGE_UPDATE and EVENT_MESSAGE_DELETE were added to the methods imbot.register and imbot.update to enable subscription to events that update and delete messages.

• New chatbot type with with advanced privileges (supervisor) was added. It is the chatbot that has access to all messages in chats, where it is a participant (to all chats, if it was invited with the access to history, and to new chats, if the access to history is not available to it).

  To create a chatbot with advanced privileges, specify type S in the TYPE field in the imbot.register method.

  Please be advised, if not required by the logic of your app, it is recommended for the chatbot to respond to the user messages only if this chatbot is mentioned. It can be checked via the TO_USER_ID field, which will be passed into the event.

  Another addition were the handlers that trace message edits and deletions (available for the chatbot of this type).

• The following new fields ENTITY_TYPE and ENTITY_ID were added to the method im.chat.add. These fields are used to perform quick search and identification of a chat in the following events: EVENT_MESSAGE_ADD, EVENT_MESSAGE_UPDATE, EVENT_MESSAGE_DELETE.
• Method imbot.update no longer supports updates of the TYPE and OPENLINE fields.
• New method is added: im.chat.get. It uses ENTITY_TYPE and ENTITY_ID to receive chat ID.

• The following fields CHAT_ENTITY_TYPE and CHAT_ENTITY_ID were added to these events: EVENT_MESSAGE_ADD, EVENT_MESSAGE_UPDATE, EVENT_MESSAGE_DELETE to identify a chat (you can specify these fields at the moment of creation).

• The field TO_USER_ID is added to the following events: EVENT_MESSAGE_ADD, EVENT_MESSAGE_UPDATE. This field will contain the ID of the mentioned user. Thanks to this addition, in case of the 'S' type bot you will be able to understand, whether to respond or not to respond.
• Update for imbot.register and imbot.update: if all your event handlers will input the same address, instead of specifying EVENT_MESSAGE_ADD, EVENT_MESSAGE_UPDATE, EVENT_MESSAGE_DELETE, EVENT_WELCOME_MESSAGE, EVENT_BOT_DELETE - you can specify only EVENT_HANDLER - its value will be automatically written into all the event handlers.

• Method im.chat.add was supplemented by a new OWNER_ID field, via which you can specify the chat owner.

• The following methods were added to the Working with Chats (Bot API) section:

  • imbot.chat.add - create chat on behalf of chatbot;
  • imbot.chat.get - get chat ID;
  • imbot.chat.setOwner - change chat owner on behalf of chatbot.

• Parameter BOT_ID was added to all the Working with Chats (Bot API) methods.

December 2017

• New error code MAX_COUNT_ERROR was added to the method imbot.register - it notifies that the maximum number of registered bots was reached for one application.
• Now, maximum quantity of bots for single application is 5.