Keep up to date with the Symphony Framework by subscribing to the mailing list.

Check out the new Symphony Framework Academy! It’s the home for information and tutorials to help you get the most from the Symphony Framework! Click on the Academy option below.

Symphony Framework Release Notes

Symphony Framework Version 3.2.5.0.


Change set: 41561


Additional data added to the Symphony Framework sample database.

Change set: 41562


Added the product images to the Symphony Framework sample installer.

Change set: 41563


Added the lock master example files to the Symphony Framework sample installer.

Change set: 41564


Modify the example configuration settings for the Symphony Bridge console and service servers.

Ensure that the Symphony Bridger Console server re-creates the authentication files. Ensure that when the program closes that all domains are closed correctly.

Ensure that the Symphony Bridger Service server re-creates the authentication files. Ensure that when the program closes that all domains are closed correctly.

Modified the ApplicationController class to accept and expose the original Client Guid to enable seamless authentication when a new application domain is created due to the current domain being in operation.

Modified the ApplicationManager class to utilize the original client Guid. Implemented a method to correctly close down all current domains.

The SymphonyBridgeService now creates log files based on the client Id and the original ID if a busy application domain is encountered and a new “cloned” domain is created.

Added encryption to the authentication class so that stored username/password combinations are encrypted in the file.

Correctly send back to the client the right client guid.

The username/password authentication details are scrapped on the client along with the connection “string” after the first connection attempt. The authentication details are now stored encrypted on the server. If using the Azure Service bus Relay configuration the authentication file MUST be shared between the services. You can use xfServer to ensure that all servers point to the same data files. Authentication failures will occur if this is not configured correctly.

Change set: 41565


Fix an issue relating to Change Method processing. When a change method used the FieldValidDetails() and FieldErrorDetails() methods of the data object the framework was then incorrectly clearing the error information.