Changes in 51233d3: Updated Report Lifecycle (markdown)

				Guides/Report-Lifecycle.md
			
          @@ -11,7 +11,7 @@ The Izenda reports API has a various methods and properties that can be overridd

           This outlines the call structure when accessing the report list page as it pertains to reports and API hooks.

           1. **[[InitializeReporting|http://wiki.izenda.us/FAQ/InitializeReporting]]:** The first call must be to InitializeReporting before other API calls are made. This sets the groundwork for all reporting operations. It is recommended that all pages using Izenda reports call this method in the code-behind.

          -2. **[[GetReportListConfig|/API/CodeSamples/Javascript/GetReportListConfig]] (webServer):** GetReportListConfig is an ajax call launched by the report list that is necessary to be called before the report list can be initialized.

          +2. **[[ReportListConfig|/API/CodeSamples/Javascript/ReportListConfig]] (webServer):** GetReportListConfig is an ajax call launched by the report list that is necessary to be called before the report list can be initialized.

           3. **[[ReportListDataLite|/API/CodeSamples/Javascript/ReportListDataLite]] (webServer):** ReportListDataLite is an ajax call launched after the configuration is obtained by the report list and returns a JSON formatted object to the javascript callback specified.

           4. **[[FilteredListReportsDictionary|http://wiki.izenda.us/FAQ/FilteredListReports]]:** FilteredListReportsDictionary is called upon requesting the report list data above and can be manipulated in global.asax. This will also get the database schema from the cache or cache it if it's not cached.

           5. **[[ListReports|http://wiki.izenda.us/FAQ/ListReports]]:** The ListReports method returns a broader range of reports and can also be manipulated in global.asax. This method performs differently depending on if you use DatabaseAdHocConfig or FileSystemAdHocConfig. This will iterate through each report and perform the following operations:

...	...	@@ -11,7 +11,7 @@ The Izenda reports API has a various methods and properties that can be overridd
11	11	This outlines the call structure when accessing the report list page as it pertains to reports and API hooks.
12	12
13	13	1. [[InitializeReporting\|http://wiki.izenda.us/FAQ/InitializeReporting]]: The first call must be to InitializeReporting before other API calls are made. This sets the groundwork for all reporting operations. It is recommended that all pages using Izenda reports call this method in the code-behind.
14		-2. [[GetReportListConfig\|/API/CodeSamples/Javascript/GetReportListConfig]] (webServer): GetReportListConfig is an ajax call launched by the report list that is necessary to be called before the report list can be initialized.
	14	+2. [[ReportListConfig\|/API/CodeSamples/Javascript/ReportListConfig]] (webServer): GetReportListConfig is an ajax call launched by the report list that is necessary to be called before the report list can be initialized.
15	15	3. [[ReportListDataLite\|/API/CodeSamples/Javascript/ReportListDataLite]] (webServer): ReportListDataLite is an ajax call launched after the configuration is obtained by the report list and returns a JSON formatted object to the javascript callback specified.
16	16	4. [[FilteredListReportsDictionary\|http://wiki.izenda.us/FAQ/FilteredListReports]]: FilteredListReportsDictionary is called upon requesting the report list data above and can be manipulated in global.asax. This will also get the database schema from the cache or cache it if it's not cached.
17	17	5. [[ListReports\|http://wiki.izenda.us/FAQ/ListReports]]: The ListReports method returns a broader range of reports and can also be manipulated in global.asax. This method performs differently depending on if you use DatabaseAdHocConfig or FileSystemAdHocConfig. This will iterate through each report and perform the following operations: