Skip to main content
Sign in

Release Notes: September 2022 (WebABA Enterprise)


*This article is no longer being updated. Visit the new Therapy Brands Portal.
Copy & paste this article title into the search bar there.
  • Updated

 Alert! This area is where we outline recent product enhancements and resolved issues to help you stay up to date with the changes happening in WebABA Enterprise. 

The following improvements and bug/defect fixes were made for this release. They will help the user have a better experience with WebABA Enterprise.

Version 8.38.0

 

New Features

  • New controls for the RBT Supervision Tracker (Paid Feature) were added.
    • The emails can now be entirely disabled.
    • Which staff will receive the emails for a Deleted RBT Supervised Appointment can now be determined by Job Title or Department.
    • The frequency in which staff will receive emails can be adjusted.
  • If you would like to make changes to this feature, please reach out to support. 

Product Defect Resolutions

  • In Funding Source and Services Copy function, users were receiving an error of "FAILURE: Report data could not be retrieved due to the following error: Column name or number of supplied values does not match table definition.".
    • This has been resolved, the function will now run without error.

      NOTE: There is an additional defect that is being resolved in a future release. Any notes on the Funding Source being copied will not be copied over and must be entered manually if needed.

  • The External API BillingLedger was not returning accurate data based on the filters supplied.
    • This was due to an issue with the service end date where the stored procedure had always a fixed time equal to 12:00 AM. This ruled out all the valid records for that day.
    • To correct this the timestamp has been fixed to match the end of the end date's day (23:59:59). Now the External API call for BillingLedger will return the correct expected data.
  • The External API BillingLedger was requiring an invalid date range causing the API to not return correct data.
    • This was because there was an unnecessary validation requiring that the Billed Date was inside the Service Date Range. This validation has been removed because the Billed Date would not typically fall within the Service Date Range.
    • Now the External API BillingLedger will return data as expected.
  • Receiving intermittent errors when trying to Export Claims to the Office Ally Clearinghouse.
    • The error was preventing claims from being transmitted however, after waiting a period and trying again, the export would complete without error.
    • A review of the issue determined it appears to be intermittent though errors were found logged regarding library versions. As a result, updated WinSCP library files are being deployed to all customers. 

[Back to Top]

Related articles

Powered by Zendesk