Release 2.6.3

Issues fixed

Issue with invalid XML character in Event parameter (ticket: 4617)
Fixed an issue where an invalid XML character in a parameter value for an Event caused a runtime exception in the style of:

ArgumentException: '', hexadecimal value 0x1A, is an invalid character.

With this fix, any invalid XML character in an Event parameter will be replaced with a space.

Wrong extension parameter name in Automation
Fixed an issue where the PowerShell Automation submitted Unload jobs with a wrong name for the parameter passing the ExtensionUsageID for the Runtime to identify the selected Unloader

Fix null reference exception when viewing history for a Test Area
Fixed an issue where the history tab for a Test Area failed with a null reference exception, if the history include changes to the readiness state for the area

Treat blank-only field in CSV files as null value for nullable data types other than Char (ticket: 4623)
The new BulkDataLoaders introduced in 2.5 changed the behavior when loading CSV files. Before 2.5, any field in the file targeting a metadata field of a nullable data type other than Char where treated as a null value when the value in the CSV file was an empty string or a string containing only spaces.

With 2.5, only empty strings were treated as null. Space-only fields from the CSV files were parsed to their corresponding data type, which of course failed.

This issue is now fixed so space-only fields are also treated as null values in this case.