Quick-Start.md
... ...
@@ -8,7 +8,7 @@
8 8
9 9
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.
10 10
11
-**Configuring Settings**
11
+####Configuring Settings
12 12
13 13
14 14
... ...
@@ -18,7 +18,7 @@ The Izenda Reports API contains specific settings that alter the behavior of the
18 18
19 19
20 20
21
-**Creating Views**
21
+####Creating Views
22 22
23 23
24 24
... ...
@@ -28,7 +28,7 @@ Some databases contain complex field names that may be confusing to users. In th
28 28
29 29
30 30
31
-**Applying Branding**
31
+####Applying Branding
32 32
33 33
34 34
... ...
@@ -50,7 +50,7 @@ IFRAMES or Frames : The Izenda reports pages may be placed inside an IFRAME or F
50 50
51 51
52 52
53
-**Building Core Reports**
53
+####Building Core Reports
54 54
55 55
56 56
... ...
@@ -60,7 +60,7 @@ The best way to deploy Izenda is to create a small set of base reports that user
60 60
61 61
62 62
63
-**Enforcing Security and User Limitations **
63
+####Enforcing Security and User Limitations
64 64
65 65
66 66
... ...
@@ -68,7 +68,7 @@ The Izenda Reports platform includes a robust and flexible security model which
68 68
69 69
70 70
71
-*Assumptions - These will vary based on your application*
71
+####*Assumptions - These will vary based on your application*
72 72
73 73
* The username is stored in a session variable called "UserName"
74 74
* The users role is stored in a session variable called "Role"
... ...
@@ -78,7 +78,7 @@ The Izenda Reports platform includes a robust and flexible security model which
78 78
79 79
80 80
81
-*Limitations Enforced*
81
+####*Limitations Enforced*
82 82
83 83
* The user is logged In
84 84
* The user can only see records for their ClientID