The following is a complete list of changes made between iSymphony 3.1 beta 1 and iSymphony 3.1 beta 2. If you are upgrading from iSymphony 3.0.x, please see the changelog for iSymphony 3.1 Beta 1 as well.

Performance Improvements:

• Greatly improved the performance of the Call and Transfer actions, decreasing login times in environments with many users and extensions.

Resolved Bugs:

• Resolved a bug allowing users to temporarily remove the All Extensions group from the system, if they had editor permission to it.
• Resolved a bug preventing the system from properly checking the Owned by User permission exception.
• Resolved a bug preventing the last button for each user in the Users widget from being displayed.
• Added identifiers to PBX objects in the Exceptions list in the permission editor. This allows you to search by extension number or queue/parking lot/conference room identifier, in addition to the display name.
• Resolved a bug that would corrupt the configuration of any new core servers added, thereby preventing iSymphony from starting the next time. 
• Re-added queues as a valid exception type to the Login an Agent permission, and enforced this permission for queues as well as extensions.
• Resolved a bug that would display a harmless error dialog several seconds after logging into the Administration interface. 
• Resolved a bug preventing the Policy selection from opening in certain operating system/browser combinations.
• Resolved a bug causing the incorrect type of PBX objects to appear in the Exceptions list in the permission editor. 
• Resolved a bug that would prevent the client interface from correctly determining whether a chat session already existed between the logged in user and another user in some circumstances. This would prevent the logged in user from starting a chat session with other users.
• Fixed a bug causing the Exceptions list to be cut off for the last permission of each category in the permissions editor.
• Fixed a bug preventing the Set selected to feature in the permissions editor from working properly for permissions that were currently defined as Inherit.
• Added translation keys for a number of missing texts in the client and administration interfaces.
• Fixed a bug causing the Penalty column in the Queue Agents table to report the value of Calls Taken instead. 

Other Improvements and Changes:

Known Issues

The following issues are known to the development team to exist in iSymphony 3.1 beta 2, and are scheduled to be fixed before the final release of iSymphony 3.1 stable. Before reporting an issue to us, please check this list to determine whether we are already aware of the problem. In addition, consider whether these issue might impact your use of iSymphony before upgrading. 

• When the remote agent disconnects, it does not clean up its state properly and will fail to reconnect. To reconnect the remote agent, you will need to restart the main iSymphony server. 
• In some circumstances, an IllegalStateException is thrown when attempting to place a call. 
• If another user is on a call when you log in, the middle row of their user box will have a white background, rather than the correct color for the call they are currently on. This will resolve itself as soon as the color changes.
• Hiding notifications from the notification tray fails, and eventually causes an error dialog to appear.
• When using the remote agent, information about all voicemails in the system is sent from the agent to the server every time a new voicemail is added, rather than information for just the new voicemail. Depending on how many voicemails are in the system, this can potentially greatly increase the amount of traffic between the remote agent and the main iSymphony server, and in extreme cases can saturate the network interface on the PBX and affect call quality. For this reason, we do not recommend using the remote agent when a large number of voicemails are stored on your system. 
• When attempting to remove an existing core server, an IllegalArgumentException is thrown. 
• When creating a new core server, an IllegalStateException is logged to the log files. 
• Incoming chats no longer trigger a desktop notification. 
• When multiple permissions in the same category are selected in the permission editor, deselecting one will cause the others in that category to disappear. 
• The sorting of subjects in the permission editor is random.
• If no license is installed, or the installed license does not support permissions, the permission editor will allow you to make changes. Attempting to save those changes will display an error dialog and fail. 
• The word "extensions" is misspelled in the tool tip for the extension login button in the Queue widget.