Wildix Integrations Changelog

WiIdix Integrations Changelog: new features, improvements and fixes for Wildix Integrations with third-party software products and web applications: Salesforce, Citrix, Infusionsoft, Zoho etc

Integrations webpage: https://www.wildix.com/integrations/

Other changelogs: https://www.wildix.com/new-releases-and-updates/

Link for sharing: https://wildix.atlassian.net/wiki/x/2h7OAQ

Salesforce integration v. 1.37 Date: 22.03.2024

Fix

[WMS-19567] - int: fixed an issue with Salesforce Lightning integration in which any unsaved data (e.g. text of an email, etc.) was lost upon receiving an incoming call

Documentation: Salesforce Lightning Integration - User Guide - English

Zoho Integration Date: 18.03.2024

Fix

[WMS-19076] - int: fixed an issue, in which after ending a call in Zoho integration, “Dialed number is busy” notification was displayed

Note: The fix is supported starting from WMS Beta 6.06.20240315.1

DocumentationZoho CRM integration with Wildix PBX

Salesforce integration v. 1.36 Date: 06.03.2024

Improvement

[WMS-18543] - int: made updates to Salesforce integration in the view of Google Chrome ending support of third-party cookies 

Important:

With the current update, it is necessary to go to WMS -> PBX -> Integrations -> Cloud integrations and enable the “Salesforce Telephony” integration. Otherwise, users will not be able to log in to the Salesforce integration after the update. For instructions and more details, check the documentation (see the section “Enable Salesforce Telephony in WMS”): 

Fix

[WMS-18925] - int: fixed an issue with Salesforce Lightning Integration in which outgoing calls were logged as incoming

Webhook integration Date: 21.02.2024

New Feature

[WMS-19099] - wim: updated Webhook integration by adding possibility to enable User presence events sending

For details and instructions, see documentation: How to set up Webhook integration

Outlook integration Date: 16.02.2024

Improvement

[WMS-18755] - int: removed the option Use HTTP from the “Outlook to PBX synchronization” window in Outlook integration, which made it impossible to connect to the PBX unless HTTP was manually deactivated  

Note: The improvement is available with the updated Outlook contacts Import app, which you can download in the documentation: Outlook integration for Microsoft Windows

Outlook integration Date: 06.02.2024

Fix

[WMS-19128] - int: fixed an issue with Outlook integration in which contact name during a call was displayed incorrectly due to Outlook contact lookup overwriting internal extension number

Note: The fix is available starting from WIService v. 3.17.6

Documentation: What is WIServiceOutlook integration for Microsoft Windows

Outlook Integration Date: 01.02.2024

Fixes

[WMS-17813] - int: fixed an issue in which caller name lookup via Outlook Integration stopped working and caller number was displayed instead of the caller name

[WMS-18003 ] - int: fixed an issue in which new draft emails were generated after enabling Outlook integration

Note: The fixes are available starting from WIService v. 3.17.4

Documentation: What is WIServiceOutlook integration for Microsoft Windows

HubSpot Integration 3.0.8 Date: 29.01.2024

Fix

[WMS-18612] - int: fixed an issue with HubSpot integration in which incoming group call was logged multiple times, for every user with the call ringing

Limitation: The first agent in the call group queue should be logged into HubSpot integration, as any missed calls are logged to HubSpot on behalf of the agent who is first in the call group queue. If the agent is not logged in, the missed call may not be recorded in HubSpot.

Documentation: HubSpot Integration - User Guide - English

HubSpot Integration 3.0.7 Date: 15.01.2024

Fix

[WMS-18298] - int: fixed an issue in which outgoing calls placed from Deals and Tickets pages in HubSpot didn’t appear on the Calls tab

Documentation: HubSpot Integration - User Guide - English

teams4Wildix Integration Date: 04.01.2024

Fix

[WMS-18502] - wim: fixed an issue in which it was impossible to install MS Teams Presence integration due to an authorization error

teams4Wildix Integration Date: 02.01.2024

New Feature

[WMS-16922] - wda: added possibility to sync user presence status from Collaboration / x-bees to Microsoft Teams

Notes:

  • PBX should be updated to WMS v. 6.05.20231229.4 or higher
  • Cloud Analytics should be activated in WMS -> PBX -> Features
  • Any other calendar integrations (Google Calendar or Microsoft 365) should be deactivated, otherwise Microsoft Teams presence sync won't work
  • Important: If you have previously activated Microsoft Teams Presence, you need to reactivate it for 2-way presence sync

How-to:

  • Go to WMS -> PBX -> Integrations -> Cloud integrations
  • Click Microsoft Teams Presence
  • Click Install and log in to your Microsoft account
  • Once your user status is changed in Collaboration/ x-bees, it is automatically aligned in Microsoft Teams

Documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation.

Salesforce Integration Date: 22.12.2023

Improvements

[WMS-17643] - wim: released a new version of Salesforce integration with x-bees

  • The integration is available in WMS -> PBX -> Integrations -> x-bees tab -> Salesforce Automation and performs logging of calls and meetings between PBX users and Salesforce contacts. If you enable the new integration, the logging is performed via the new integration.
  • Note: Starting from WMS Beta 6.05.20231110.2, x-bees tab in WMS -> PBX -> Integrations is renamed into Cloud integrations. 

Important: At the current development stage, it is not recommended to disable the old version of Salesforce integration yet, as part of the current functionality (e.g. the display of Salesforce contact information on the Info frame in x-bees) may become unavailable.

Documentation: Salesforce Integration with x-bees

[WMS-18677] - wim: added possibility to install HubSpot Automation and Salesforce Automation integrations on PBX with Collaboration licenses 

The integrations perform logging of Collaboration calls and conferences performed to HubSpot or Salesforce, saving the call or meeting record on the relevant contact page in the corresponding CRM. 

Salesforce Lightning Integration v. 1.35.0 Date: 20.12.2023

Fix

[WMS-18141] - int: fixed an issue in which calls were not saved in the Activity section of the relevant contact in Salesforce in some cases

Documentation: Salesforce Lightning Integration - User Guide - English

HubSpot Integration 3.0.6 Date: 13.12.2023

Fix

[WMS-18412] - int: fixed an issue in which there was a notification asking for confirmation to leave the page when user wanted to open another tab or another section on the HubSpot page after completing a call

Limitation: In case the option “Hide the popup after the call is completed” is enabled in Settings, which automatically hides Wildix widget, you may face the notification confirming to leave the page if you proceed to another tab or another section in HubSpot in less than 1-2 seconds after completing the call. 

Documentation: HubSpot Integration - User Guide - English

Salesforce Lightning Integration v. 1.33.0 Date: 07.12.2023

Improvements

[WMS-18051] - int: added possibility to generate DTMF during a call from Salesforce Wildix integration 

[WMS-18203] - int: improved the logic so that when opening contact details, they are opened in the same Salesforce page rather than in a new browser tab

Documentation: Salesforce Lightning Integration - User Guide - English

Outlook integration Date: 28.11.2023

Improvement

[WMS-18517] - int: fixed an issue in which incorrect error message (“Unsupported PBX version” instead of “Collaboration not connected”) was displayed when creating a conference in Outlook Integration, when Collaboration was not connected

Note: The fix is available starting from WIService v. 3.16.8.

Documentation: What is WIServiceOutlook integration for Microsoft Windows

Salesforce Integration Date: 24.11.2023

Fix

[WMS-18547] - int: fixed an issue in which Hold button didn’t work in Salesforce integration in case x-bees Web was selected as an active device

Note: The fix is supported starting from WMS Beta 6.05.20231121.1.

Documentation: Salesforce Lightning Integration - User Guide - English

HubSpot Integration Date: 24.11.2023

Improvement

[WMS-17641] - wim: released a new version of HubSpot integration with x-bees (currently in Beta)

The integration is available in WMS -> PBX -> Integrations -> x-bees -> HubSpot Automation and performs logging of calls and meetings between PBX users and HubSpot contacts. If you enable the new integration, the logging is performed via the new integration.

Important: At the current development stage, it is not recommended to disable the old version of HubSpot integration yet, as part of the current functionality (e.g. the display of HubSpot contact information on the Info frame in x-bees) may become unavailable.

Documentation: How to Set Up HubSpot Integration 

HubSpot Integration 3.0.5 Date: 23.10.2023

Fix

[WMS-18043] - int: fixed an issue in which some calls were not saved on the Activity and Call tabs in HubSpot and there were occasional pop-ups requesting to reinstall the application

Documentation: HubSpot Integration - User Guide - English

teams4Wildix Integration Date: 03.10.2023

Fix

[WMS-18085] - wim: fixed an rare issue in which Microsoft Teams presence sync didn’t work if user’s email contained capital letters

Documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation

HubSpot Integration 3.0.4 Date: 14.09.2023

Fixes

[WMS-17535] - int: fixed an issue in which outgoing call from x-bees and Collaboration was displayed as inbound in HubSpot

[WMS-17656] - int: fixed an issue in which instead of the name, extension of the caller was displayed in call history on the Activity tab in HubSpot

Note: You need to relogin to HubSpot after the update. 

Documentation: HubSpot Integration - User Guide - English

Webhook integration Date: 01.09.2023

New Feature

[WMS-17373] - wda: added possibility to configure Webhook integration with third-party web applications and services for sending call related events

For instructions, see documentation: How to set up Webhook integration

Salesforce Lightning Integration v. 1.32.0 Date: 28.08.2023

Fix

[WMS-17747] - int: fixed an issue in which it wasn’t possible to create a contact without email in Salesforce Lightning integration

Documentation: Salesforce Lightning Integration - User Guide - English

HubSpot Integration 3.0.2 Date: 11.08.2023

Fix

[WMS-17634] - int: fixed an issue in which a call to a contact was not saved to Activity in HubSpot integration in case the phone number included spaces

Documentation: HubSpot Integration - User Guide - English

Datto Autotask Integration Date: 31.07.2023

Fix

[WMS-17683] - int: fixed an issue of Datto Autotask integration not connecting because *.wildixin.com could not be allowed in WIService

Note: The fix is supported starting from WIService v. 3.15.4.

Documentation: What is WIServiceHow to set up Wildix integration with Datto Autotask

Salesforce Lightning Integration v. 1.31.0 Date: 27.07.2022

Fix

[WMS-17618] - int: fixed a rare issue in which there was an error displaying call history in Salesforce Lightning integration 

Documentation: Salesforce Lightning Integration - User Guide - English

HubSpot Integration 3.0.1 Date: 27.07.2023

Improvement

[WMS-17541] - int: made some performance improvements to avoid an issue when calls were not displayed on the Activity tab in some cases if there were multiple HubSpot tabs open

Documentation: HubSpot Integration - User Guide - English

teams4Wildix Integration Date: 11.07.2023

Fix

[WMS-17452] - int: fixed PBX domain validation issue in teams4Wildix integration by adding possibility to a) enter custom PBX domain, that may contain numbers and hyphen; b) use different ports to connect, e.g. :8888

Documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation

HubSpot Integration v 3.0.0 Date: 03.07.2023

Improvement

[WMS-16767] - int: made some improvements to HubSpot integration which include:

  • Added compatibility with x-bees

  • Added OAuth 2.0 authorization to provide a more secure authentication mechanism
    Users who already use the integration need to re-connect with OAuth 2.0 Application ID

Consult HubSpot Integration User Guide for details.

teams4Wildix Integration Date: 18.05.2023

New Feature

[WMS-16406] - wda: added possibility to sync user presence status from Microsoft Teams to Collaboration / x-bees

How-to:

  1. Go to WMS -> PBX -> Integrations
  2. Proceed to the Calendars tab (or to x-bees tab in case of a PBX with x-bees licence)
  3. Click Microsoft Teams Presence
  4. Click Install
  5. Log in to your Microsoft account

Note:

  • Presence sync with Microsoft Teams is part of teams4Wildix integration which requires CLASSOUND license.
  • Currently, the sync is performed in one way, from Microsoft Teams to Collaboration / x-bees. User status sync from Collaboration / x-bees to Microsoft Teams is not supported. 
  • Make sure you don’t have any calendar integrations (Google Calendar or Microsoft 365) enabled, otherwise Microsoft Teams presence sync won't work.

Documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation

Datto Autotask Integration Date: 15.02.2023

Improvement

[WMS-15346] - int: made some improvements to Datto Autotask integration which include:

  • Stability, name lookup and number detection functionality improvements
  • Added a clickable link to user name on the Wildix popup, which opens a separate window with contact information, in case the contact is available in Autotask phonebook 
    Note: To use the feature, pop-ups should be allowed in browser settings 
  • Added relevant alerts in case Collaboration tab is closed and if ClickToCall extension is disconnected

Note: ClickToCall extension v. 0.0.4, available by this LINK

Documentation: How to set up Wildix integration with Datto Autotask

Datto Autotask Integration Date: 23.09.2022

Improvement

[WMS-15117] - int: added the Domain field to Wildix ClickToCall extension -> Datto API variables screen, which allows to indicate any Datto Autotask domain when configuring the integration

Note: ClickToCall extension v. 0.0.2, available by this LINK

Documentation: How to set up Wildix integration with Datto Autotask

Datev Integration v 1.1.16 Date: 09.09.2022

Improvement

[WMS-14688] - int: added support of TLS 1.2 on Datev integration, which fixes Datev connection issues

Documentation: GDrive Link

Datto Autotask Integration Date: 11.08.2022

[WMS-14441] - int: added support of Wildix Collaboration integration with Datto’s Autotask Professional Services Automation (PSA)

Documentation: How to set up Wildix integration with Datto Autotask

teams4Wildix Integration Date: 11.08.2022

[WMS-11916] - int: uploaded Wildix Collaboration to Microsoft Store

Documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation

Salesforce Lightning Integration v. 1.28.0 Date: 07.07.2022

Improvement

[WMS-14401] - int: added two additional fields (“Account” and “Record type”) when creating Contact in Salesforce integration 

  • Note: For correct work of the integration, make sure there is at least one record type set in Salesforce

Documentation: Salesforce Lightning Integration - User Guide - English

SAP Business One Integration Update

Fix

[WMS-14104] - int: fixed an issue with adding a new contact in SAP Business One integration, in which symbol "+" and first digit of the phone number were cut off in the contact form

Download new version of the integration in the Installation Link section of this guide: SAP Business One Integration - User Guide - English

HubSpot Integration Date: 08.06.2022

Fix

[WMS-14326] - int: fixed an issue in which after making a call to a contact in HubSpot integration via “Make a phone call” button, the further outgoing call via Collaboration dropped if user clicked on some menu on a contact page in HubSpot integration

teams4Wildix Integration Date: 03.06.2022

Fix

[WMS-14211] - int: fixed an issue in which it was impossible to use teams4Wildix integration if PBX domain name contained a dash (-)

teams4wildix documentation: teams4Wildix - integration of Microsoft Teams with Wildix PBX - Documentation

HubSpot Integration Date: 17.05.2022

Improvement

[WMS-13997] - int: added support of multiple HubSpot integration tabs, allowing to make calls via Wildix from any of the HubSpot tabs

HubSpot Integration Date: 03.05.2022

Fix

[WMS-13906] - int: fixed some issues, including an error message asking to reinstall the app when user was making a call

  • Note: To get the updated integration version, click on the Reinstall button that appears when making a call > click Install Wildix App.

teams4Wildix Integration Date: 28.01.2022

Fix

[WMS-12777] - sys: fixed occasional one-way audio issue during calls from Microsoft Teams to Wildix devices, leaving PCMA codec as a default one and allowing to edit the list of codecs via teams4Wildix portal

Documentation: teams4Wildix - Instructions for End Customers on MS Phone System Setup

Salesforce Lightning Integration v 1.27.0 Date: 17.01.2022

Fix

[WMS-12824] - int: fixed an issue in which it wasn’t possible to make outgoing calls via Dialpad or load History

Documentation: Salesforce Lightning Integration User Guide

Zoho Integration Date: 20.09.2021

Fix

[WMS-12129] - sys: recovered PhoneBridge public key to fix an issue in which Zoho integration didn’t work on some PBXs 

Documentation: Zoho CRM integration with Wildix PBX

Datev Integration v 1.1.15 Date: 06.08.2021

Fix

[WMS-11247] - int: fixed an issue with outgoing call duration missing if a call was placed via Datev

Documentation: GDrive Link

Salesforce Lightning Integration v 1.26.0 Date: 17.06.2021

Fix

[WMS-11303] - int: fixed an issue with impossibility to log a call activity of a user in Activity tab

Salesforce Lightning Integration v 1.25.0 Date: 21.04.2021

Improvement

[WMS-10811] - int: added Call History option for Lightening version

Salesforce Integration v 1.24.0 Date: 25.03.2021

Fix

[WMS-10830] - int: fixed an issue with Contact name being not displayed if a phone number contained special characters in Lightning and Classic versions

Salesforce Integration v 1.23.0 Date: 25.03.2021

[WMS-10644] - int: fixed an issue with Enter number button being disabled after entering a number that contained special characters in Lightning version

[WMS-10770] - int: visualized the app's version on GUI in Lightning and Classic versions

  • you can check it under Phone menu 

Salesforce Integration v 1.22.0 Date: 23.02.2021

Improvement

[WMS-10542] - app: added a call duration timer to a call dialog window in Lightning and Classic versions

Fix

[WMS-10468] - app: fixed an issue in which a call dialog window disappeared after attended transfer in Lightning and Classic versions