Changes in 6e83fcf: Updated Release Notes (markdown)

				Release-Notes.md
			
          @@ -10,7 +10,7 @@

           |FB:21959|Data|Data Sources|Feature - Addition of MySQL Stored Procedure support. The only stored procedures supported at this time MUST be formatted a specific way for Izenda to be able to use them. The connection string must use the MULTI_STATEMENTS=1 identifier. The procedures themselves must use the following syntax: DELIMITER $$ BEGIN DROP TABLE IF EXISTS `[SprocName]_spResult`; /* Izenda-specific code */ CREATE TEMPORARY TABLE `[SprocName]_spResult` AS /* Izenda-specific code */ [The normal sproc body goes here] SELECT * FROM `[SprocName]_spResult`; /* Izenda-specific code */ END$$ DELIMITER ; where [SprocName] is the exact name of your stored procedure without the brackets. Functionally, these work just like MSSQL stored procedures as far as Izenda is concerned. The processes for including them in VisibleDataSources, working with constraints, passing parameters as filters, etc are the same. Be sure to change the DELIMITER to something other than the semicolon or else MySQL will not correctly compile the stored procedure.|

           |FB:22093|API|Cache|Feature - Add support to allow 'InvalidateSchemaCache' to be executed across entire webfarm. New setting implemented, activated through a single setting. If there are two machines "server1" and "server2" in webfarm, for both servers, use the following setting in InitializeReporting:AdHocSettings.WebFarmNodesRsUrls = new string[] { "http://server1/rs.aspx", "http://server2/rs.aspx" }; When invalidate schema cache is used it works across all machines.|

           |FB:19135|API|Session State|Feature - Added IDataStorage interface to allow customization of the storage mechanisms for sessions. Izenda can be configured to use a custom class that implements this interface. Sample use:// This code should be placed before any Izenda calls.AdHocContext.Storage = new CustomSessionStorage(); A code sample was created to illustrate the concepts. Code Sample available [here](http://wiki.izenda.us/Release-Notes/sessionsample.txt)|

          -|FB:19705|Report Design|Filters|Feature – Add Filter Alias Prior to this new feature filters must be named the same as the column name or Field Alias set in code. Now to alias filters there are 2 options 1 – Use AdHocSettings.FilterAliases to set the alias for how column names are displayed in the filter selection drop down from code. 2 – User can change the filter name using the new Description field. This can be accessed in the Report designer from the filter tab or from the viewer by clicking the gear icon in the filter. The logic of applying aliases is the following (from the highest priority to the lowest): 1) Defined by the user alias - Description property of the filter 2) AdHocSettings.FilterAliases 3) AdHocSettings.FieldAliases 4) Column name. More information can be found [here](http://wiki.izenda.us/Guides/ReportDesign/5.0-Filters-tab)|

          +|FB:19705|Report Design|Filters|Feature – Add Filter Alias. Prior to this new feature filters must be named the same as the column name or Field Alias set in code. Now to alias filters there are 2 options 1 – Use AdHocSettings.FilterAliases to set the alias for how column names are displayed in the filter selection drop down from code. 2 – User can change the filter name using the new Description field. This can be accessed in the Report designer from the filter tab or from the viewer by clicking the gear icon in the filter. The logic of applying aliases is the following (from the highest priority to the lowest): 1) Defined by the user alias - Description property of the filter 2) AdHocSettings.FilterAliases 3) AdHocSettings.FieldAliases 4) Column name. More information can be found [here](http://wiki.izenda.us/Guides/ReportDesign/5.0-Filters-tab)|

           |FB:19756|API|Caching|Feature - Cache Interface Added the first phase of cache changes to allow easy customization of the caching mechanism(s) used in Izenda. A new cache interface (IPermanentDataCache) was implemented for two Izenda data caches. RenderedResultsCache: the Fusion(HTML) cache DatabaseSchemaCache: used to cache the schema information. With these changes, any caching provider can be used by implementing the IPermanentDataCache interface in a custom class and configuring Izenda to use the custom class. AdHoc.Cache.DataCache.IPermanentDataCache is called "permanent" because for these caches we do not use the "storage" expiration approach. The expiration policy of all objects in the cache can be controlled by custom code. - Custom caches can be specified using AdHocContext.Caches property. Currently DataCacheRepository contain only two caches - RenderedResultsCache and DatabaseSchemaCache but we will expand this list to more different caches. Having one repository will make adding them easier in the future. Here is how you can apply custom class for DB cache: AdHocContext.Caches.DatabaseSchemaCache = new CustomDbSchemaCache(); And here is the same for Fusion cache: AdHocContext.Caches.RenderedResultsCache = new CustomHtmlCache(); Be sure to do this before all other Izenda calls. A sample Redis cache for DB Schema has been created for reference. This was implemented using Redis. Code Sample available [here](http://wiki.izenda.us/Release-Notes/CacheSample.txt)|

           |FB:19815|Instant Reports|New BETA Page|Feature - The new Instant Report Designer page is being released as a *BETA* version in the Izenda 6.10.0.1 release. This beta release is made available to allow a broad user base to evaluate and give us feedback on the future of the Report Designer, but is not recommended for production use at this stage. This is not a fully supported feature however and any product defects will be noted, but not slated for immediately scheduled work.Please review documentation [here](http://wiki.izenda.us/Guides/Instant-Reports-v2-BETA)|

           |FB:21663|Printing|PDF Support In Azure|Addition of new PDF engine - EVO. Provides Azure support via cloud service. There is a known issue with HTML charts and EVO printing that is scheduled for resolution in 6.10.0.2. Learn more on this configuring the cloud service [here](http://wiki.izenda.us/API/CodeSamples/PdfPrintMode#PdfPrintMode)|

...	...	@@ -10,7 +10,7 @@
10	10	\|FB:21959\|Data\|Data Sources\|Feature - Addition of MySQL Stored Procedure support. The only stored procedures supported at this time MUST be formatted a specific way for Izenda to be able to use them. The connection string must use the MULTI_STATEMENTS=1 identifier. The procedures themselves must use the following syntax: DELIMITER $$ BEGIN DROP TABLE IF EXISTS `[SprocName]_spResult`; /* Izenda-specific code / CREATE TEMPORARY TABLE `[SprocName]_spResult` AS / Izenda-specific code / [The normal sproc body goes here] SELECT FROM `[SprocName]_spResult`; /* Izenda-specific code */ END$$ DELIMITER ; where [SprocName] is the exact name of your stored procedure without the brackets. Functionally, these work just like MSSQL stored procedures as far as Izenda is concerned. The processes for including them in VisibleDataSources, working with constraints, passing parameters as filters, etc are the same. Be sure to change the DELIMITER to something other than the semicolon or else MySQL will not correctly compile the stored procedure.\|
11	11	\|FB:22093\|API\|Cache\|Feature - Add support to allow 'InvalidateSchemaCache' to be executed across entire webfarm. New setting implemented, activated through a single setting. If there are two machines "server1" and "server2" in webfarm, for both servers, use the following setting in InitializeReporting:AdHocSettings.WebFarmNodesRsUrls = new string[] { "http://server1/rs.aspx", "http://server2/rs.aspx" }; When invalidate schema cache is used it works across all machines.\|
12	12	\|FB:19135\|API\|Session State\|Feature - Added IDataStorage interface to allow customization of the storage mechanisms for sessions. Izenda can be configured to use a custom class that implements this interface. Sample use:// This code should be placed before any Izenda calls.AdHocContext.Storage = new CustomSessionStorage(); A code sample was created to illustrate the concepts. Code Sample available [here](http://wiki.izenda.us/Release-Notes/sessionsample.txt)\|
13		-\|FB:19705\|Report Design\|Filters\|Feature – Add Filter Alias Prior to this new feature filters must be named the same as the column name or Field Alias set in code. Now to alias filters there are 2 options 1 – Use AdHocSettings.FilterAliases to set the alias for how column names are displayed in the filter selection drop down from code. 2 – User can change the filter name using the new Description field. This can be accessed in the Report designer from the filter tab or from the viewer by clicking the gear icon in the filter. The logic of applying aliases is the following (from the highest priority to the lowest): 1) Defined by the user alias - Description property of the filter 2) AdHocSettings.FilterAliases 3) AdHocSettings.FieldAliases 4) Column name. More information can be found [here](http://wiki.izenda.us/Guides/ReportDesign/5.0-Filters-tab)\|
	13	+\|FB:19705\|Report Design\|Filters\|Feature – Add Filter Alias. Prior to this new feature filters must be named the same as the column name or Field Alias set in code. Now to alias filters there are 2 options 1 – Use AdHocSettings.FilterAliases to set the alias for how column names are displayed in the filter selection drop down from code. 2 – User can change the filter name using the new Description field. This can be accessed in the Report designer from the filter tab or from the viewer by clicking the gear icon in the filter. The logic of applying aliases is the following (from the highest priority to the lowest): 1) Defined by the user alias - Description property of the filter 2) AdHocSettings.FilterAliases 3) AdHocSettings.FieldAliases 4) Column name. More information can be found [here](http://wiki.izenda.us/Guides/ReportDesign/5.0-Filters-tab)\|
14	14	\|FB:19756\|API\|Caching\|Feature - Cache Interface Added the first phase of cache changes to allow easy customization of the caching mechanism(s) used in Izenda. A new cache interface (IPermanentDataCache) was implemented for two Izenda data caches. RenderedResultsCache: the Fusion(HTML) cache DatabaseSchemaCache: used to cache the schema information. With these changes, any caching provider can be used by implementing the IPermanentDataCache interface in a custom class and configuring Izenda to use the custom class. AdHoc.Cache.DataCache.IPermanentDataCache is called "permanent" because for these caches we do not use the "storage" expiration approach. The expiration policy of all objects in the cache can be controlled by custom code. - Custom caches can be specified using AdHocContext.Caches property. Currently DataCacheRepository contain only two caches - RenderedResultsCache and DatabaseSchemaCache but we will expand this list to more different caches. Having one repository will make adding them easier in the future. Here is how you can apply custom class for DB cache: AdHocContext.Caches.DatabaseSchemaCache = new CustomDbSchemaCache(); And here is the same for Fusion cache: AdHocContext.Caches.RenderedResultsCache = new CustomHtmlCache(); Be sure to do this before all other Izenda calls. A sample Redis cache for DB Schema has been created for reference. This was implemented using Redis. Code Sample available [here](http://wiki.izenda.us/Release-Notes/CacheSample.txt)\|
15	15	\|FB:19815\|Instant Reports\|New BETA Page\|Feature - The new Instant Report Designer page is being released as a BETA version in the Izenda 6.10.0.1 release. This beta release is made available to allow a broad user base to evaluate and give us feedback on the future of the Report Designer, but is not recommended for production use at this stage. This is not a fully supported feature however and any product defects will be noted, but not slated for immediately scheduled work.Please review documentation [here](http://wiki.izenda.us/Guides/Instant-Reports-v2-BETA)\|
16	16	\|FB:21663\|Printing\|PDF Support In Azure\|Addition of new PDF engine - EVO. Provides Azure support via cloud service. There is a known issue with HTML charts and EVO printing that is scheduled for resolution in 6.10.0.2. Learn more on this configuring the cloud service [here](http://wiki.izenda.us/API/CodeSamples/PdfPrintMode#PdfPrintMode)\|