Changes in 4980bcc: Updated 14.0 Izenda FORMS (markdown)

				Guides/ReportDesign/14.0-Izenda-FORMS.md
			
          @@ -68,26 +68,29 @@ After choosing relevant fields and adjusting formats in the ‘Fields’ tab, cl

           The form designer has two modes:  ‘Editor’ and ‘Source.’ Izenda’s form designer functions in the same manner as any browser based text editor when in ‘Editor’ mode. In this interface you can see a preview of rendered HTML and any user can make a quick customization or change. Changes made in ‘Editor’ mode are automatically parsed into HTML.

          -![forms1](http://wiki.izenda.us/Guides/ReportDesign/14.0-Izenda-FORMS/design_form.png)

          +###Source View

          +

          +![forms1](http://wiki.izenda.us/Guides/ReportDesign/14.0-Izenda-FORMS/design_form_source.png)

          +

          +**Source** mode accepts HTML directly.  If you are designing a new form from scratch, most HTML designers will find it is best to build new projects using a web design tool like Expressions and then simply paste the source code into Izenda FORMS in **Source** mode.  The user should not attempt to build a complex report using **Editor** mode, because the parsing engine will add additional unnecessary complexity as the report complexity increases, and any HTML added into **Editor** mode will display as text rather than as the markup that it actually was meant to be.

          +

          +###Editor View

           ![forms2](http://wiki.izenda.us/Guides/ReportDesign/14.0-Izenda-FORMS/design_form_editor.png)

          -‘Source’ mode accepts HTML directly.  If you are designing a new form from scratch, most HTML designers will find it is best to build new projects using a web design tool like Expressions and then simply paste the source code into Izenda FORMS in ‘Source’ mode.  The user should not attempt to build a complex report using ‘Editor’ mode, because the parsing engine will add additional unnecessary complexity as the report complexity increases.

          +**Editor** mode allows you to insert text only. Any markup that is entered here will be translated into a form that will not be interpreted by the browser. You can see this if you paste HTML into the **Editor** mode box and then click **Source**. However, if you are editing in **Source** mode and click the **Editor** mode button, you will see that the HTML is parsed into what will be displayed in your report. The I9 form above is generated in such a way.

          -Again, it is best practice to build an Izenda FORMS report in ‘Source’ mode by hand or by using an external web design tool to generate HTML. Once this HTML is pasted into the tool while in ‘Source’ mode, you can easily switch to ‘Editor’ mode to tweak the output.

          +Again, it is best practice to build an Izenda FORMS report in **Source** mode by hand or by using an external web design tool to generate HTML. Once this HTML is pasted into the tool while in **Source** mode, you can easily switch to **Editor** mode to fine-tune the output.

           **Video Tutorial:** http://blog.izenda.com/quick-tutorial-making-the-most-of-your-toolbar-options/

          -![forms3](http://wiki.izenda.us/FAQ/FAQ/forms3.png)

          -

           ### Adding Fields

          -Fields are inserted into a form using square brackets. 

          +Fields are inserted into a form using square brackets. The name within the square brackets should correspond to either the actual name of the field or the alias you gave the field. Either one will work, although there are times when you should use one over the other, as we will describe below.

           **Example:**  

          -``[Field Name or Alias HERE]``

          -If you want to display the field 'ShipCountry', then at the appropriate place in the form, you would place the ``[ShipCountry]`` tag.

          +If you want to display the field 'ShipCountry', then at the appropriate place in the form, you would place the ``[ShipCountry]`` tag. You could also place ``[Ship Country]`` in your form if you aliased the ``[ShipCountry]`` as such. The alias is the exact text in the "Description" text box on the [[Fields tab|http://wiki.izenda.us/Guides/ReportDesign/4.0-fields-tab]].

           **Video Tutorial:** http://blog.izenda.com/quick-tip-adding-and-modifying-fields/

          @@ -95,9 +98,9 @@ If you want to display the field 'ShipCountry', then at the appropriate place in

           ### Nesting Reports and Forms

          -By using double square brackets, you can call another form or report.  If you have a form called City Data in the Sub-reports folder, you would type ``[[Subreports/City Data]]`` in order to drop that form into the form you are building.  This works whether the called report is a form or a non-form report.

          +As described earlier, we can specify fields by using either one or two square brackets. We covered the single square bracket above. Now we will cover a double square bracket. By using double square brackets, you can call another form or report.  If you have a form called City Data in the Subreports folder, you would type ``[[Subreports/City Data]]`` into your form to embed that form into your report.  This works regardless of whether the embedded report is a form or a non-form report.

          -Caution is recommended when designing nested sub-reports and forms.  When you call a report from inside of a master report, you are essentially using a query to run another query (and by result, all queries that might be contained within that nested query).  It is thus possible to build a chain of nested reports that can cause severe performance issues.  

          +Caution is recommended when designing nested sub-reports and forms.  When you call a report from inside of a master report, you are essentially using a query to run another query (and by extension, all queries that might be contained within that nested query).  It is thus possible to build a chain of nested reports that can cause severe performance issues.  

           The flexibility of nesting reports and forms is most desirable for many small cases, in which sub-reports only exhibit a very small performance hit. Complex or multi-level nested reports may experience significant performance issues; in these cases it is best to find a way to achieve your goal without using sub-reports.

          @@ -105,7 +108,7 @@ The flexibility of nesting reports and forms is most desirable for many small ca

           If you have content that you want to repeat within a form, you don’t need to use a nested sub-form.   By enclosing this content with the ``[repeater]`` tag, the forms engine will repeat that content until it is exhausted. 

          -In this example, we would generate a table with 1+n rows.  The first row is static and displays text in two cells.  The second row is within a repeater, which means that it will generate _**n**_ times where _**n**_ is the number of valid ``[PersonID]`` entries.  This repeater has a nested repeater in the second cell, which will populate all valid ``[Name]`` for each ``[PersonID]``.  

          +In this example, we would create a report with 1+n rows.  The first row is static and displays text in two cells with the text "Person" and "Certs".  The second row is within a repeater, which means that it will generate _**n**_ times where _**n**_ is the number of valid ``[PersonID]`` entries.  This repeater has a nested repeater in the second cell, which will populate all valid ``[Name]`` for each ``[PersonID]``.

           ```html

           <table>

          @@ -122,9 +125,9 @@ In this example, we would generate a table with 1+n rows.  The first row is stat

           </table>

           ```

          -All of these count against the Records display limit. If you have four ``[PersonID]`` and each has three ``[Name]`` entries, then the form would count as 12 records.  This means that if you set it to only display 10 records, the form would not completely generate.

          +All of these count against the Records display limit. If you have four ``[PersonID]`` records and each ``[PersonID]`` has three ``[Name]`` entries, then the form would count as 12 records.  This means that if you set it to only display 10 records, the form would not display completely.

          -You can only nest one set of repeaters at a time.  This is a correct use:

          +**Limitations:** You can only nest one set of repeaters at a time.  This is a correct use:

           ```html

           [repeater]

          @@ -140,7 +143,7 @@ You can only nest one set of repeaters at a time.  This is a correct use:

           [/repeater]

           ```

          -**And this is an incorrect use:**

          +And this is an incorrect use:

           ```html

           [repeater]

          @@ -156,7 +159,12 @@ You can only nest one set of repeaters at a time.  This is a correct use:

           [/repeater]

           ```

          -**Video tutorials**

          +##Tutorial

          +

          +We will go over a fairly complex FORMs report using the concepts described above. We also have a couple of **Video tutorials**

           * http://blog.izenda.com/quick-tutorial-how-to-use-the-repeater-tag/ 

          -* http://screencast.com/t/6RwYd7sKKKh (alternate)

          \ No newline at end of file

          +* http://screencast.com/t/6RwYd7sKKKh (alternate)

          +* http://blog.izenda.com/quick-tutorial-making-the-most-of-your-toolbar-options/

          +

          +

...	...	@@ -68,26 +68,29 @@ After choosing relevant fields and adjusting formats in the ‘Fields’ tab, cl
68	68
69	69	The form designer has two modes: ‘Editor’ and ‘Source.’ Izenda’s form designer functions in the same manner as any browser based text editor when in ‘Editor’ mode. In this interface you can see a preview of rendered HTML and any user can make a quick customization or change. Changes made in ‘Editor’ mode are automatically parsed into HTML.
70	70
71		-![forms1](http://wiki.izenda.us/Guides/ReportDesign/14.0-Izenda-FORMS/design_form.png)
	71	+###Source View
	72	+
	73	+![forms1](http://wiki.izenda.us/Guides/ReportDesign/14.0-Izenda-FORMS/design_form_source.png)
	74	+
	75	+Source mode accepts HTML directly. If you are designing a new form from scratch, most HTML designers will find it is best to build new projects using a web design tool like Expressions and then simply paste the source code into Izenda FORMS in Source mode. The user should not attempt to build a complex report using Editor mode, because the parsing engine will add additional unnecessary complexity as the report complexity increases, and any HTML added into Editor mode will display as text rather than as the markup that it actually was meant to be.
	76	+
	77	+###Editor View
72	78
73	79	![forms2](http://wiki.izenda.us/Guides/ReportDesign/14.0-Izenda-FORMS/design_form_editor.png)
74	80
75		-‘Source’ mode accepts HTML directly. If you are designing a new form from scratch, most HTML designers will find it is best to build new projects using a web design tool like Expressions and then simply paste the source code into Izenda FORMS in ‘Source’ mode. The user should not attempt to build a complex report using ‘Editor’ mode, because the parsing engine will add additional unnecessary complexity as the report complexity increases.
	81	+Editor mode allows you to insert text only. Any markup that is entered here will be translated into a form that will not be interpreted by the browser. You can see this if you paste HTML into the Editor mode box and then click Source. However, if you are editing in Source mode and click the Editor mode button, you will see that the HTML is parsed into what will be displayed in your report. The I9 form above is generated in such a way.
76	82
77		-Again, it is best practice to build an Izenda FORMS report in ‘Source’ mode by hand or by using an external web design tool to generate HTML. Once this HTML is pasted into the tool while in ‘Source’ mode, you can easily switch to ‘Editor’ mode to tweak the output.
	83	+Again, it is best practice to build an Izenda FORMS report in Source mode by hand or by using an external web design tool to generate HTML. Once this HTML is pasted into the tool while in Source mode, you can easily switch to Editor mode to fine-tune the output.
78	84
79	85	Video Tutorial: http://blog.izenda.com/quick-tutorial-making-the-most-of-your-toolbar-options/
80	86
81		-![forms3](http://wiki.izenda.us/FAQ/FAQ/forms3.png)
82		-
83	87	### Adding Fields
84	88
85		-Fields are inserted into a form using square brackets.
	89	+Fields are inserted into a form using square brackets. The name within the square brackets should correspond to either the actual name of the field or the alias you gave the field. Either one will work, although there are times when you should use one over the other, as we will describe below.
86	90
87	91	Example:
88		-``[Field Name or Alias HERE]``
89	92
90		-If you want to display the field 'ShipCountry', then at the appropriate place in the form, you would place the ``[ShipCountry]`` tag.
	93	+If you want to display the field 'ShipCountry', then at the appropriate place in the form, you would place the ``[ShipCountry]`` tag. You could also place ``[Ship Country]`` in your form if you aliased the ``[ShipCountry]`` as such. The alias is the exact text in the "Description" text box on the [[Fields tab\|http://wiki.izenda.us/Guides/ReportDesign/4.0-fields-tab]].
91	94
92	95	Video Tutorial: http://blog.izenda.com/quick-tip-adding-and-modifying-fields/
93	96
...	...	@@ -95,9 +98,9 @@ If you want to display the field 'ShipCountry', then at the appropriate place in
95	98
96	99	### Nesting Reports and Forms
97	100
98		-By using double square brackets, you can call another form or report. If you have a form called City Data in the Sub-reports folder, you would type ``[[Subreports/City Data]]`` in order to drop that form into the form you are building. This works whether the called report is a form or a non-form report.
	101	+As described earlier, we can specify fields by using either one or two square brackets. We covered the single square bracket above. Now we will cover a double square bracket. By using double square brackets, you can call another form or report. If you have a form called City Data in the Subreports folder, you would type ``[[Subreports/City Data]]`` into your form to embed that form into your report. This works regardless of whether the embedded report is a form or a non-form report.
99	102
100		-Caution is recommended when designing nested sub-reports and forms. When you call a report from inside of a master report, you are essentially using a query to run another query (and by result, all queries that might be contained within that nested query). It is thus possible to build a chain of nested reports that can cause severe performance issues.
	103	+Caution is recommended when designing nested sub-reports and forms. When you call a report from inside of a master report, you are essentially using a query to run another query (and by extension, all queries that might be contained within that nested query). It is thus possible to build a chain of nested reports that can cause severe performance issues.
101	104
102	105	The flexibility of nesting reports and forms is most desirable for many small cases, in which sub-reports only exhibit a very small performance hit. Complex or multi-level nested reports may experience significant performance issues; in these cases it is best to find a way to achieve your goal without using sub-reports.
103	106
...	...	@@ -105,7 +108,7 @@ The flexibility of nesting reports and forms is most desirable for many small ca
105	108
106	109	If you have content that you want to repeat within a form, you don’t need to use a nested sub-form. By enclosing this content with the ``[repeater]`` tag, the forms engine will repeat that content until it is exhausted.
107	110
108		-In this example, we would generate a table with 1+n rows. The first row is static and displays text in two cells. The second row is within a repeater, which means that it will generate _n_ times where _n_ is the number of valid ``[PersonID]`` entries. This repeater has a nested repeater in the second cell, which will populate all valid ``[Name]`` for each ``[PersonID]``.
	111	+In this example, we would create a report with 1+n rows. The first row is static and displays text in two cells with the text "Person" and "Certs". The second row is within a repeater, which means that it will generate _n_ times where _n_ is the number of valid ``[PersonID]`` entries. This repeater has a nested repeater in the second cell, which will populate all valid ``[Name]`` for each ``[PersonID]``.
109	112
110	113	```html
111	114	<table>
...	...	@@ -122,9 +125,9 @@ In this example, we would generate a table with 1+n rows. The first row is stat
122	125	</table>
123	126	```
124	127
125		-All of these count against the Records display limit. If you have four ``[PersonID]`` and each has three ``[Name]`` entries, then the form would count as 12 records. This means that if you set it to only display 10 records, the form would not completely generate.
	128	+All of these count against the Records display limit. If you have four ``[PersonID]`` records and each ``[PersonID]`` has three ``[Name]`` entries, then the form would count as 12 records. This means that if you set it to only display 10 records, the form would not display completely.
126	129
127		-You can only nest one set of repeaters at a time. This is a correct use:
	130	+Limitations: You can only nest one set of repeaters at a time. This is a correct use:
128	131
129	132	```html
130	133	[repeater]
...	...	@@ -140,7 +143,7 @@ You can only nest one set of repeaters at a time. This is a correct use:
140	143	[/repeater]
141	144	```
142	145
143		-And this is an incorrect use:
	146	+And this is an incorrect use:
144	147
145	148	```html
146	149	[repeater]
...	...	@@ -156,7 +159,12 @@ You can only nest one set of repeaters at a time. This is a correct use:
156	159	[/repeater]
157	160	```
158	161
159		-Video tutorials
	162	+##Tutorial
	163	+
	164	+We will go over a fairly complex FORMs report using the concepts described above. We also have a couple of Video tutorials
160	165
161	166	* http://blog.izenda.com/quick-tutorial-how-to-use-the-repeater-tag/
162		-* http://screencast.com/t/6RwYd7sKKKh (alternate)
...	...	\ No newline at end of file
	0	+* http://screencast.com/t/6RwYd7sKKKh (alternate)
	1	+* http://blog.izenda.com/quick-tutorial-making-the-most-of-your-toolbar-options/
	2	+
	3	+