Developers can use the Division element in their Logi reporting applications to contain and organize groups of elements within a report. The Division element makes working with groups of element in Studio easier and provides the ability to dynamically apply style classes, or to show and hide report sections.
The following topics discuss the Division element and techniques for its use:
- Hiding/Showing Report Sections Using Conditions
- Hiding/Showing Report Sections Using Show Modes
- Hiding/Showing Report Sections Using Security Rights
- Hiding/Showing Report Sections Using Action.Refresh Element
About the Division Element
In Studio, the Division element functions as a "container" for other elements. It's a parent element that can have a wide range of child elements.
The presence of a Division element normally causes a set of HTML <SPAN> tags to be generated when the report is run. However, the element has an attribute that allows <DIV> tags to be generated instead. Generally, the DIV tag is considered a "block" container and SPAN an "in-line" container. A DIV tag also automatically produces a Line Break after it.
New for 14.2 You also have the option to specify the Output HTML DIV Tag attribute for all elements that are not set manually at the application level. The Output HTML DIV Tag attribute in the Division element has two possible values: True or False. If you select True, <div> is the wrapper tag for your element. If you select False, or if the attribute is blank/undefined, <span> is the wrapper tag for your element. The global constant, rdOutputHtmlDivTagDefault, specifies the default rendering results when the Output HTML DIV Tag of the Division element is not set explicitly. The default value for this constant is blank, or False. When set to True, the default rendering result is <div>.
You can assign a style class to a Division element and, as a container, that class will affect all of the Division's child elements. For example, a style class that sets a font size can be applied once, to a Division element, and all of the elements the Division contains will also use that font size (unless individually overridden). Division elements also include "HTML Attribute Params", enabling you to apply your application to work with other frameworks or libraries easier. With the HTML Attribute Params, you have the option to include "style" parameters. If an attribute was set in both Element and HTML attribute params, the one set in the HTML attribute params will be ignored.
Divisions can be also be used as an organizing entity. Report sections, containing any number of elements, can be placed within a Division. Then the Division can be shown or hidden, using dynamic criteria, causing the section to appear or disappear in the report. This provides tremendous flexibility and can be used to reduce the number of report definitions that need to be developed and maintained and can be used to make a report appear differently in different circumstances or for different users.