User Input Elements
User Input elements produce input controls, which allow users to interact with applications at runtime. They're often used to often to provide data selection and filtering criteria.
The following topics discuss each of the Logi Info Input elements:
- Input Telephone (Mobile Only)
- Input Time
- Input File Upload
- Input Text Area
- Input Check Box
- Input Select List
- Input Check Box List
- Input Combo List
- Input Radio Buttons
- Input Slider
- Input Color Picker
- Input Chart.List
- Input Chart.Range
- Input Selection Point & Range
About Input Elements
Logi Info Input elements are based on the standard HTML input control types and provide useful interactivity. They can be used to gather user input at runtime in order to login to an application, to filter or restrict data, to modify the style or appearance of a report, to insert new or update existing data, and more.
New for 14.1 Adding HTML Attribute Params to your User Input elements enables you to apply your application to work with other frameworks or libraries easier. Depending on the type of HTML Attribute Params you add, there will be different parameters available to use, or you can define your own parameters. If an attribute was set in both Element and HTML Attribute Params, the one set in the HTML Attribute Params will be ignored.
When you include Input elements in a report definition, a ;<FORM> tag is automatically added to the HTML page generated. Following standard HTML behavior, when a user clicks links or buttons that reload the report or pass control to another definition, the form is submitted, along with all of the input control values that have been entered.
When an report page is submitted, the values of all of its Input elements are automatically passed to the next Report or Process definition. DO NOT use Link Parameters to try to pass the entered values - they'll become null.
In the next Report or Process definition, you can access the entered values using Request tokens. For example, if an Input Text element has an element ID of inpLastName, its value is available in the token @Request.inpLastName~.
Because the values are passed using HTTP POST, they will not appear in the URL. They are clearly shown, however, in the Debugger Trace Page when you turn debugging on, and this is a great tool for determining what's happening with user input values.
Due to the stateless nature of HTML pages, you generally have to submit (or refresh) a page before its value is usable in its own report definition. There are some exceptions to this; it's possible to use JavaScript to get and set the values of Input elements without submitting the page. This, and many other useful techniques, are described in Working with User Input Elements.
Our Sample Center is also an good resource. Special mobile input elements are discussed in Logi Mobile Reports.