Removing the Facebook, WhatsApp, or Telegram Message Buttons from the Actions Dashboard in Creatio

In Creatio. 7.18.3 there’s a new feature where the Facebook, WhatsApp, and Telegram message buttons are added to the Actions Dashboard, allowing you to resume a message started with a contact in one of these mediums. However, these buttons show even if you’ve not setup or are using these message mediums, which might confuse users. This post will outline how to remove one, or all, of these buttons from the actions dashboard.

To remove one of these buttons, or all of them, you need to create a replacing view model so we can override the actions dashboard. To do this, in the configuration click Add, then select Replacing view model:

When it opens, select “SectionActionsDashboard” as the Parent object:

Now, simply paste in the following code:

define("SectionActionsDashboard", [], function() {
	return {
		diff: [
				"operation": "remove",
				"name": "FacebookMessageTab"
				"operation": "remove",
				"name": "TelegramMessageTab"
				"operation": "remove",
				"name": "WhatsAppMessageTab"

Note, you can optionally just add one or more of the remove operations listed in that code if you wanted to only remove some of the buttons but not all. Once saved, the buttons will no longer appear in the actions dashboard.


Ryan Farley

Ryan Farley is the Director of Development for Customer FX and creator of He's been blogging regularly about SalesLogix, now Infor CRM, since 2001 and believes in sharing with the community. His new passion for CRM is Creatio, formerly bpm'online. He loves C#, Javascript, web development, open source, and Linux. He also loves his hobby as an amateur filmmaker.


  1. Is it possible to Removing the Facebook, WhatsApp, or Telegram Message Buttons on custom sections only?

    • This is not at all tested, but you would do something like:

      1) Add an attribute:
      “AreSocialActionsVisible”: {
      “dataValueType”: Terrasoft.DataValueType.BOOLEAN,
      “value”: true

      Modify the diff so the visible of the tabs are bound to the attribute:
      “operation”: “merge”,
      “name”: “FacebookMessageTab”,
      “values”: {
      “visible”: { “bindTo”: “AreSocialActionsVisible” }

      3) Set the attribute in the init based on the current bound entity:
      init: function() {
      // hide for Case entity
      var isNotCaseEntity = (this.$entitySchemaName != “Case”);
      this.set(“AreSocialActionsVisible”, isNotCaseEntity);


Submit a Comment

Your email address will not be published. Required fields are marked *

Subscribe To Our Newsletter

Join our mailing list to receive the latest Infor CRM (Saleslogix) and Creatio (bpm'online) news and product updates!

You have Successfully Subscribed!