Skip to main content

App Connect 1.5.8 is now available


ByrneReese
Community Manager
Forum|alt.badge.img+3

We're excited to announce the release of App Connect 1.5.8, available now! This update brings several key improvements and fixes designed to enhance your experience and streamline your workflow.

What's New?

One of the most significant changes in this release addresses an issue for Bullhorn users who observed notes stuck with a "Pending" action. App Connect will now more accurately differentiate between calls in the process of being logged and those for which logging is complete. If logging isn't complete, the system will periodically check for all assets to be ready to complete the process. This means more reliable note logging and less manual intervention for you.

We've also implemented a number of smaller, yet impactful, fixes:

  • Improved CRM Connection Status: We've resolved an issue where users might see a "disconnected" message from their CRM while settings showed a "connected" status. App Connect now displays the correct connection status, preventing confusion.

  • Reduced Unnecessary Messages: We're beginning to suppress some "everything is operating properly" messages that would occasionally obscure UI elements. This provides a cleaner and less disruptive user experience.

  • Updated Setting Copy: The text for the setting that controls the visibility of the App Connect badge and click-to-dial has been updated for better clarity.

  • Resolved UI Blocking Error: We've fixed a rare HTML error message that could briefly block the entire App Connect UI.

  • Redtail Disposition Fix: A disposition issue reported by our Redtail customers has been resolved.

  • Enhanced Session Stability: We've worked to make user sessions more stable, reducing the need for frequent re-logins.

These updates reflect our ongoing commitment to providing you with a seamless and efficient App Connect experience.

We encourage all users to update to App Connect 1.5.8 to take advantage of these improvements. If you have any questions or feedback, please don't hesitate to reach out to our support team!

Did this thread help you find an answer to your question?

5 replies

  • Participating Frequently
  • 5 replies
  • July 30, 2025

@ByrneReese I think we’ve come across a bug in this version, or may be a longer standing issue which we have only just identified.

When inbound calls to our main number from a Bullhorn candidate/contact are received, transferred to a call queue, and then missed or sent to voicemail, the call continues to be logged am my username (as the admin).  App Connect should log the call as RingCentral API user if it does not know who to assign the call. Continuing to log the call as myself is misleading and causes confusion.

Additionally, it would be helpful in App Connect to have the option to be able to capture the below information within Bullhorn:

  • Inbound calls: the number dialled by the caller
  • Outbound calls: The caller ID (the number the caller used to dial out from)

We are running the latest App Connect 1.5.8 with server side logging enabled.


Embbnux
Community Manager
Forum|alt.badge.img+1
  • Community Manager
  • 43 replies
  • August 1, 2025

Hi ​@Rian212539066 Now App Connect server will use admin (who enable server side logging)’s session token firstly if the admin session token not expired. If it is expired, it will use bullhorn API username in server side logging setting.

To have a quick fix, you can disable server side logging in your admin account. Then disconnect Bullhorn in App Connect and re-connect with your Bullhorn API user. Then enable server side logging again. 


  • Participating Frequently
  • 5 replies
  • August 5, 2025

Hi ​@Embbnux Thanks for the response on this. I’m afraid the quick fix is not a viable solution for us as it would mean permanently running my Bullhorn session as the API user.

It would be great if the Created by could be displayed as the actual API username rather than the admin who initiated the connection the Bullhorn in this instance.


ByrneReese
Community Manager
Forum|alt.badge.img+3
  • Author
  • Product Manager
  • 349 replies
  • August 5, 2025

@Rian212539066 The latest version of App Connect allows you to independently specify the admin credentials you will use when logging calls. App Connect will also try to assign the owner of the Bullhorn Note to the agent/recruiter who made the call. Check this documentation out:

https://ringcentral.github.io/rc-unified-crm-extension/crm/bullhorn/#bullhorn-and-server-side-call-logging


Embbnux
Community Manager
Forum|alt.badge.img+1
  • Community Manager
  • 43 replies
  • August 7, 2025
Rian212539066 wrote:

Hi ​@Embbnux Thanks for the response on this. I’m afraid the quick fix is not a viable solution for us as it would mean permanently running my Bullhorn session as the API user.

It would be great if the Created by could be displayed as the actual API username rather than the admin who initiated the connection the Bullhorn in this instance.

Hi ​@Rian212539066 For quick fix, you can use another Chrome/Browser profile to login bullhorn with API user, and authorize App Connect with API user to setup server side logging. So it will not effect your bullhorn session in your main browser profile.
 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings