Changes in c71bc4a: Updated Getting Started (markdown)

				Integration/Tutorials/Getting-Started.md
			
          @@ -1,21 +1,23 @@

          -#**Integration Quick Start Guide**

          +#Integration Quick Start Guide

           [[_TOC_]]

          +##Introduction

          +

           Izenda reports includes a flexible API that can be configured to integrate with your application. This guide covers most of the basic elements that are needed to apply branding and security to the majority of applications. Before beginning make sure that Izenda Reports can properly connect to your database when setup as a stand-alone virtual directory. 

           ###Izenda Reports Quick Setup

           To integrate Izenda into your own website, you will first need a development environment, such as Visual Studio. Once you have a development environment, you can get our website template from [here](http://www.izenda.com/Site/DownloadComplete.aspx?msgId=0). Once you have followed the steps there, return here and find out more about how you can get started using Izenda Reports.

          -###Configuring Settings

          +###[[Configuring Settings|Integration/Tutorials/Customizing-Izenda-Settings]]

           The Izenda Reports API contains specific settings that alter the behavior of the tool on a per-user basis. Settings can be applied through the Settings.aspx page or via a CustomAdHocConfig class which is normally found in the Global.asax file. Examples of important settings include the license key or the user name. 

          -###Creating Views

          +###[[Creating Views|Integration/Tutorials/Views]]

          -Some databases contain complex field names that may be confusing to users. In these situations it may be necessary to create reporting views that simplify the data model for the user. Users can be limited to specific views using the "Visible DataSources" setting. See the [[Views]] article for more details. 

          +Some databases contain complex field names that may be confusing to users. In these situations it may be necessary to create reporting views that simplify the data model for the user. Users can be limited to specific views using the "Visible DataSources" setting.

          -###Applying Branding

          +###[[Applying Branding|Integration/Tutorials/Appearance]]

           There are a few different ways to apply your branding, logo or header controls to Izenda Reports. 

          @@ -25,15 +27,17 @@ Master Pages : If you already have an ASP.NET master page, you can apply it to R

           IFRAMES or Frames : The Izenda reports pages may be placed inside an IFRAME or FRAME. This would need to be done for ReportDesigner.aspx, ReportList.aspx, and ReportViewer.aspx. 

          -###Building Core Reports

          +###[[Building Core Reports]]

           The best way to deploy Izenda is to create a small set of base reports that user can then customize. Ideally initial reports should contain the most relevant data sources and fields. It may be beneficial to add summaries and charts to them as well. See the training section for details on how to create various types of reports. 

          -###Enforcing Security and User Limitations

          +###[[Enforcing Security and User Limitations|Integration/Tutorials/Security]]

          +

          +The Izenda Reports platform includes a robust and flexible security model which inherits rich security credentials from your application. This example covers how to apply security for most common scenarios by using the ''PostLogin()'' to pass user credentials to the Izenda API. This method is normally found in the [CustomAdHocConfig](Integration/Tutorials/Adding-Code) class in the Global.asax file. 

          -The Izenda Reports platform includes a robust and flexible security model which inherits rich security credentials from your application. This example covers how to apply security for most common scenarios by using the PostLogin() to pass user credentials to the Izenda API. This method is normally found in the [CustomAdHocConfig](http://wiki.izenda.us/Adding-Code) class in the Global.asax file. 

          +###Assumptions

          -###*Assumptions - These will vary based on your application*

          +These will vary based on your application

             * The username is stored in a session variable called "UserName"

             * The users role is stored in a session variable called "Role" 

          @@ -41,7 +45,7 @@ The Izenda Reports platform includes a robust and flexible security model which 

             * The database contains tables and views with a field named "ClientID"

             * Reports will be created and saved to a category called "Admin Reports" 

          -###*Limitations Enforced*

          +###Limitations Enforced

             * The user is logged In

             * The user can only see records for their ClientID

          @@ -49,7 +53,7 @@ The Izenda Reports platform includes a robust and flexible security model which 

             * Non-admins will not be able to overwrite reports

             * Non-admins will not see the "Admin Reports" and "Sensitive Reports" categories in their report list 

          -*Basic Login Security - Place in PostLogin() or InitializeReporting() method of CustomAdHocConfig which is normally found in Global.asax.*

          +*Basic Login Security - Place in the ``PostLogin()`` or ``InitializeReporting()`` method of ``CustomAdHocConfig`` which is normally found in **Global.asax**.*

           ``` c#

           //Pass User Credentials

...	...	@@ -1,21 +1,23 @@
1		-#Integration Quick Start Guide
	1	+#Integration Quick Start Guide
2	2
3	3	[[_TOC_]]
4	4
	5	+##Introduction
	6	+
5	7	Izenda reports includes a flexible API that can be configured to integrate with your application. This guide covers most of the basic elements that are needed to apply branding and security to the majority of applications. Before beginning make sure that Izenda Reports can properly connect to your database when setup as a stand-alone virtual directory.
6	8
7	9	###Izenda Reports Quick Setup
8	10	To integrate Izenda into your own website, you will first need a development environment, such as Visual Studio. Once you have a development environment, you can get our website template from [here](http://www.izenda.com/Site/DownloadComplete.aspx?msgId=0). Once you have followed the steps there, return here and find out more about how you can get started using Izenda Reports.
9	11
10		-###Configuring Settings
	12	+###[[Configuring Settings\|Integration/Tutorials/Customizing-Izenda-Settings]]
11	13
12	14	The Izenda Reports API contains specific settings that alter the behavior of the tool on a per-user basis. Settings can be applied through the Settings.aspx page or via a CustomAdHocConfig class which is normally found in the Global.asax file. Examples of important settings include the license key or the user name.
13	15
14		-###Creating Views
	16	+###[[Creating Views\|Integration/Tutorials/Views]]
15	17
16		-Some databases contain complex field names that may be confusing to users. In these situations it may be necessary to create reporting views that simplify the data model for the user. Users can be limited to specific views using the "Visible DataSources" setting. See the [[Views]] article for more details.
	18	+Some databases contain complex field names that may be confusing to users. In these situations it may be necessary to create reporting views that simplify the data model for the user. Users can be limited to specific views using the "Visible DataSources" setting.
17	19
18		-###Applying Branding
	20	+###[[Applying Branding\|Integration/Tutorials/Appearance]]
19	21
20	22	There are a few different ways to apply your branding, logo or header controls to Izenda Reports.
21	23
...	...	@@ -25,15 +27,17 @@ Master Pages : If you already have an ASP.NET master page, you can apply it to R
25	27
26	28	IFRAMES or Frames : The Izenda reports pages may be placed inside an IFRAME or FRAME. This would need to be done for ReportDesigner.aspx, ReportList.aspx, and ReportViewer.aspx.
27	29
28		-###Building Core Reports
	30	+###[[Building Core Reports]]
29	31
30	32	The best way to deploy Izenda is to create a small set of base reports that user can then customize. Ideally initial reports should contain the most relevant data sources and fields. It may be beneficial to add summaries and charts to them as well. See the training section for details on how to create various types of reports.
31	33
32		-###Enforcing Security and User Limitations
	34	+###[[Enforcing Security and User Limitations\|Integration/Tutorials/Security]]
	35	+
	36	+The Izenda Reports platform includes a robust and flexible security model which inherits rich security credentials from your application. This example covers how to apply security for most common scenarios by using the ''PostLogin()'' to pass user credentials to the Izenda API. This method is normally found in the [CustomAdHocConfig](Integration/Tutorials/Adding-Code) class in the Global.asax file.
33	37
34		-The Izenda Reports platform includes a robust and flexible security model which inherits rich security credentials from your application. This example covers how to apply security for most common scenarios by using the PostLogin() to pass user credentials to the Izenda API. This method is normally found in the [CustomAdHocConfig](http://wiki.izenda.us/Adding-Code) class in the Global.asax file.
	38	+###Assumptions
35	39
36		-###Assumptions - These will vary based on your application
	40	+These will vary based on your application
37	41
38	42	* The username is stored in a session variable called "UserName"
39	43	* The users role is stored in a session variable called "Role"
...	...	@@ -41,7 +45,7 @@ The Izenda Reports platform includes a robust and flexible security model which
41	45	* The database contains tables and views with a field named "ClientID"
42	46	* Reports will be created and saved to a category called "Admin Reports"
43	47
44		-###Limitations Enforced
	48	+###Limitations Enforced
45	49
46	50	* The user is logged In
47	51	* The user can only see records for their ClientID
...	...	@@ -49,7 +53,7 @@ The Izenda Reports platform includes a robust and flexible security model which
49	53	* Non-admins will not be able to overwrite reports
50	54	* Non-admins will not see the "Admin Reports" and "Sensitive Reports" categories in their report list
51	55
52		-Basic Login Security - Place in PostLogin() or InitializeReporting() method of CustomAdHocConfig which is normally found in Global.asax.
	56	+Basic Login Security - Place in the ``PostLogin()`` or ``InitializeReporting()`` method of ``CustomAdHocConfig`` which is normally found in Global.asax.
53	57
54	58	``` c#
55	59	//Pass User Credentials