Controls

In LumisXP each service interface receives its information from XML grouped into controls, which are simply tags XML named as <control/>.

Each control has a type attribute that defines what it contains.

Let's see an example, the lum_list control: <control type="lum_list"/>

The name defined by the type attribute of each control usually describes what that control will be assembling. For example:

• lum_form: brings information about the interface form;
• lum_list: brings information from the list of registered data that are displayed in the List or Administration interface;
• lum_details: brings the details of a registered item when it is selected in the List interface;
• lum_navigationList: brings information from the list of registered data in a Menu interface;
• lum_tabularData: brings information from the table of registered items;
• lum_link: brings information about the link to List interfaces, usually used in Quick List interfaces;
• lum_filters: brings filter information defined for the interface;
• lum_pagination: brings pagination information of the interface across multiple pages.

To modify the default layout that LumisXP builds its interfaces with, it is not always necessary to modify all controls. Often it is enough to modify the lum_list or lum_details, for example.

Next, it will be shown how to customize the XSL to modify the most used controls in the product's service interfaces.

The process of customizing XSL files from a blank XSL will be repeated for all the other controls that will be exemplified next. The process is: read the XML of the interface (after the content is registered in the administrative interface of the services in question) and check which controls need to be customized.