Warning! You are viewing an older version of Alpaca Guides. View the latest
Alpaca
Release Notes
Last Updated: 01/18/2021 The ECG team is pleased to announce the release version 8.0.7 of Alpaca.
This version includes support for the R22 version of the BroadWorks API.
8.0.7
- Released 01/18/2021
What's Changed
- Updated the Communigate Pro connector to use their currently supported CLI. This is a replacement to the SOAP API they previously supported.
8.0.6
- Released 12/18/2020
What's Fixed
- Fixed bug in User Replace info card that caused the Voice Messaging status to always report as Inactive.
- Improved error message in Reset Sip Authentication Task when an invalid User Agent is provided.
- Fixed error in Communigate tools when checking Communigate status.
What's Changed
- Added Reset Alpaca Password flow back into the UI.
8.0.5
- Released 11/20/2020
What's Fixed
- Fixed bug that could cause the AccessDevice object to parse incorrectly from BroadWorks XML.
- Fixed bug that caused null properties on users (email, department, etc) to be stored in the Alpaca database incorrectly. Note that this fix will prevent the bug from happening again but will not fix items that have already been affected. Items that have been previously been affected will self correct whenver they are updated in BroadWorks.
- Fixed bug that caused fields on an Alpaca User that were set to a value to become set to null when updating through the settings panel.
- Fixed UI bug that could cause table columns to re-size to 0 pixels.
What's New
- First iteration of the Additional Information panel implementation.
- Includes additional information panel for the Task page as well as the User Replace wizard.
8.0.4
- Released 10/23/2020
What's Fixed
- Fixed issue with users receiving the incorrect default Client Configuration if not overridden in a configuration file. Default Client Configuration is now in the application-prod.yml and can be easily modified.
- Fixed Device Migration bug that ignored the subtype (if configured).
- Fixed a bug that prevented downloading the task logs.
- Fixed a bug in User Delete that could cause an error if the user was using the system default domain.
8.0.3
- Released 10/14/2020
What's Fixed
- Fixed issue with Alpaca not being able to create a new user during Single Sign-On login.
- Fixed issue with Alpaca not correctly displaying errors that occur during Single Sign-On login.
8.0.2
- Released 10/14/2020
What's Fixed
- Fixed issues with incorrect permissions on Group to Enterprise Migration, User Migration, and User Collection Migration.
- Fixed bug in Group to Enterprise Migration and User Collection Migration that caused only the first 20 users to be displayed and searchable.
- Fixed bug in Group To Enterprise Migration that could cause the Group to not be split correctly if that option is selected.
- Improved the speed at which User Collection Migration Requirement checks are performed.
- Added check to Single Sign On user creation to verify that the email being registered with is not already in use. Added clear and concise error message if this occurs.
- Fixed error that could occur while performing the IP Fencing check during login.
- Fixed places where connections to BroadWorks were not being closed correctly.
8.0.1
- Released 09/22/2020
What's New
- Added configuration
requireDomainOnCredentialAdd
. When enabled, Alpaca requires User's to put their full BroadWorks usernameusername@domain
when adding credentials.
What's Fixed
- [AL-2001] Fixed issues with the User Profile panel not saving values correctly. Fixed issue with the department field being empty if not departments available.
- [AL-2002] Fixed error that occurred when attempting to submit a Bulk User Upload.
- Fixed problem with BroadWorks Password Reset not being behind the correct license.
- [AL-1886] When an error occurs during migration requirements/encumbrances, the error is now passed up instead of just being logged.
- Fixed possible error during database migration.
- [AL-2017] Fixed possible AlpacaStore bug that could cause files to being missing.
- [AL-1480] Fixed possible error when creating an XLSX report.
8.0.0
- Released 09/15/2020
What's New
- Added support for Single Sign On utilizing OAuth/OAuth2 or SAML2. See here. This feature requires the Advanced Provisioning license.
- Added User Web Self Care Portal. BroadWorks Users can now login and manage all of their BroadWorks service settings. Admins can limit what services can viewed and modified by BroadWorks Users. See here. This feature requires the Advanced Provisioning license.
- Added support for recurring tasks. Reports and export tasks can now be scheduled to occur daily, weekly, monthly, annually, or with a custom schedule.
- Added a Group level Access Device Endpoints table to monitor device registration status as well as the last time the device retrieved its configuration.
- Added support for IP fencing which allows limiting a login to Alpaca to a specific IP space based on BroadWorks login type. See here.
What's Changed
- Moved from Java 8 to Java 11 for the Alpaca Server.
- Updated the Web UI with a new redesign with a goal to improve data on larger displays.
- Default roles are now designated on a per BroadWorks login type basis.
- For developers, libraries all have unique package names. For those using the core package all classes now live in
co.ecg.alpaca.core
. - Logging implementation has been changed to Logback. Configuration can be updated in the
logback-spring.xml
file within the config directory.
What's Fixed
- Fixed issue with incorrectly labeling a failure to connect with WEBDAV to a profile server as a Times Ten alert.
- BroadWorks requests now use DNS to failover to alternative IP addresses when the initial address fails.
- BroadWorks requests that fail due to no response now return a custom error message rather than NULL.
- Fixed issues with some reports replacing ID values with memory references.
- Phone numbers in a bulk provisioning spreadsheet now support more than 10 digits.
- Fixed issues with LogFileTokens sometimes remaining open following task completion.
- Fixed temporary licensing polling data being retained for longer than intended.