XML Schema "lum_button.xsd"
Target Namespace:
http://www.lumis.com.br/douicontrols/lum_button
Components:
5 local elements, 9 complexTypes, 1 simpleType
Schema Location:
/home/opc/workspace/lpjava-16.1.x-dist/repo/Lumis_PortalJava/distribution/tmp/control/button/lum_button.xsd, see XML source
Imports Schemas (2):
douibasecontrol.xsd [src], douicontrolsdefinition.xsd [src]
Imported by Schema:
douicontrolsdefinition.xsd [src]
All Element Summary
additionalButtons (type embedded) Include any additional button here that will be placed after all auto layout buttons.
Type:
embedded complexType
Content:
complex, 1 attribute, any element
Defined:
locally at 1 location
Includes:
definition of 1 attribute
image (type xsd:string)
Type:
xsd:string
Content:
simple
Defined:
locally at 6 locations
onClick (type lum_base:onClientEvent)
Type:
lum_base:onClientEvent
Content:
complex, 7 attributes, 10 elements
Defined:
locally at 7 locations
replaceButtons (type embedded) Include any buttons here that will replace an auto layout buttons.
Type:
embedded complexType
Content:
complex, 108 elements
Defined:
locally at 1 location
rowAction (type lum_rowAction) Indicates that the button is going to be a row action.
Type:
lum_rowAction
Content:
empty, 2 attributes
Defined:
locally at 4 locations
Complex Type Summary
lum_addButton
Content:
complex, 10 attributes, 112 elements
Includes:
definitions of 5 attributes and 2 elements
Used:
at 1 location
lum_autoAdminListButtons
Content:
complex, 10 attributes, 113 elements
Includes:
definitions of 5 attributes and 3 elements
Used:
at 2 locations
lum_button
Content:
complex, 7 attributes, 113 elements
Includes:
definitions of 2 attributes and 3 elements
Used:
at 5 locations
lum_buttonList
Content:
complex, 8 attributes, 110 elements
Includes:
definitions of 4 attributes
Used:
at 1 location
lum_deleteButton
Content:
complex, 9 attributes, 113 elements
Includes:
definitions of 4 attributes and 3 elements
Used:
at 1 location
lum_editButton
Content:
complex, 12 attributes, 113 elements
Includes:
definitions of 7 attributes and 3 elements
Used:
at 1 location
lum_lockButton
Content:
complex, 7 attributes, 113 elements
Includes:
definitions of 2 attributes and 3 elements
Used:
at 1 location
lum_positionFieldOrderButton
Content:
complex, 9 attributes, 112 elements
Includes:
definitions of 4 attributes and 2 elements
Used:
never
lum_rowAction Indicates that the button is going to be a row action.
Content:
empty, 2 attributes
Includes:
definitions of 2 attributes
Used:
at 1 location
Simple Type Summary
additionalButtonsInsertPosition
Used:
at 1 location
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Revision: 25853 $ $Date: 2023-08-14 15:27:15 -0300 (Mon, 14 Aug 2023) $ -->
<xsd:schema elementFormDefault="unqualified" targetNamespace="http://www.lumis.com.br/douicontrols/lum_button" xmlns="http://www.lumis.com.br/douicontrols/lum_button" xmlns:control="http://www.lumis.com.br/douicontrols" xmlns:lum_base="http://www.lumis.com.br/douicontrols/douibasecontrol" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://www.lumis.com.br/douicontrols" schemaLocation="../douicontrolsdefinition.xsd"/>
<xsd:import namespace="http://www.lumis.com.br/douicontrols/douibasecontrol" schemaLocation="../douibasecontrol.xsd"/>
<xsd:complexType name="lum_button">
<xsd:complexContent>
<xsd:extension base="lum_base:lum_sourceBoundControl">
<xsd:sequence>
<xsd:element minOccurs="0" name="image" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="0" name="rowAction" type="lum_rowAction">
<xsd:annotation>
<xsd:documentation>
Indicates that the button is going to be a row action. Row actions are those actions that performs some processing over the table items, such as delete and edit.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="onClick" type="lum_base:onClientEvent"/>
</xsd:sequence>
<xsd:attribute name="text" type="xsd:string" use="optional"/>
<xsd:attribute default="false" name="isPrimary" type="xsd:boolean" use="optional">
<xsd:annotation>
<xsd:documentation>
Indicates whether the button is a primary button. Primary buttons are emphasized over non-primary buttons.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="lum_rowAction">
<xsd:annotation>
<xsd:documentation>
Indicates that the button is going to be a row action. Row actions are those actions that performs some processing over the table items, such as delete and edit.
</xsd:documentation>
</xsd:annotation>
<xsd:attribute default="false" name="bulkAction" type="xsd:boolean" use="optional">
<xsd:annotation>
<xsd:documentation>
Indicates whether the given row action is a bulk action either. Bulk actions are actions that may be performed over a single item as well as over multiple items.
These actions are shown in each row and also in the administration list top part, within a select component. When these actions are performed from the select component,
multiple items may be selected in the table.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="false" name="isPrimary" type="xsd:boolean" use="optional">
<xsd:annotation>
<xsd:documentation>
Indicates whether the given row action is the primary one. If this attribute is set to true, then this row action will be emphasized.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<xsd:complexType name="lum_addButton">
<xsd:complexContent>
<xsd:extension base="lum_base:lum_sourceBoundControl">
<xsd:sequence minOccurs="0">
<xsd:element default="lumis/portal/client/images/Add.gif" minOccurs="0" name="image" type="xsd:string"/>
<xsd:element minOccurs="0" name="onClick" type="lum_base:onClientEvent"/>
</xsd:sequence>
<xsd:attribute default="STR_ADD" name="text" type="xsd:string" use="optional"/>
<xsd:attribute name="interfaceId" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
By default the add interface opened when you press this button will use the following rules in precedence order:
1)Interface Id explicitly in as an attribute
2)Interface (if exists) with id = "add"+currentInterfaceId with first letter in upper case. e.g. if the current interface is administration, the interface calculated will be addAdministration
3)Interface (if exists) with id = "add"

If none of these rules apply, the button control will remove itself from its parent.
If the destination interface has been placed within a page of the portal, this button will redirect to that page.
If the destination interface has not been placed in a page, the button will open a popup page with the given interface mounted run-time.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="false" name="keepParentActive" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
<![CDATA[
By default, a "keepParentActive" attribute with value "false" is used on the onClick event for opening the destination interface for this add button.
By specifying this attribute on the add button, it will be used when generating its onClick event.
<p>
For more information, see keepParentActive attribute on the onClick element.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="openRuntimeInterfaceBehavior" type="lum_base:openRuntimeInterfaceBehavior">
<xsd:annotation>
<xsd:documentation>
<![CDATA[
By default no openRuntimeInterfaceBehavior on the onClick generated for the add button.
If a value is specified in this attribute, it will be used on the onClick event for opening the destination interface for this add button.
<p>
For more information, see openRuntimeInterfaceBehavior attribute on the onClick element.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="false" name="isPrimary" type="xsd:boolean" use="optional">
<xsd:annotation>
<xsd:documentation>
Indicates whether the button is a primary button. Primary buttons are emphasized over non-primary buttons.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="lum_positionFieldOrderButton">
<xsd:complexContent>
<xsd:extension base="lum_base:lum_sourceBoundControl">
<xsd:sequence>
<xsd:element minOccurs="0" name="image" type="xsd:string"/>
<xsd:element minOccurs="0" name="onClick" type="lum_base:onClientEvent"/>
</xsd:sequence>
<xsd:attribute default="STR_ORDER" name="text" type="xsd:string" use="optional"/>
<xsd:attribute default="false" name="keepParentActive" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
<![CDATA[
By default, a "keepParentActive" attribute with value "false" is used on the onClick event
for opening the destination interface for this order button.
By specifying this attribute on the order button, it will be used when generating its
default onClick event.
<p>
For more information, see keepParentActive attribute on the onClick element.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="openRuntimeInterfaceBehavior" type="lum_base:openRuntimeInterfaceBehavior">
<xsd:annotation>
<xsd:documentation>
<![CDATA[
By default no openRuntimeInterfaceBehavior is set on the onClick generated for the order button.
If a value is specified in this attribute, it will be used on the onClick event for opening
the destination interface for this order button.
<p>
For more information, see openRuntimeInterfaceBehavior attribute on the onClick element.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="false" name="isPrimary" type="xsd:boolean" use="optional">
<xsd:annotation>
<xsd:documentation>
Indicates whether the button is a primary button. Primary buttons are emphasized over non-primary buttons.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="lum_lockButton">
<xsd:complexContent>
<xsd:extension base="lum_base:lum_sourceBoundControl">
<xsd:sequence minOccurs="0">
<xsd:element default="lumis/portal/client/images/Lock.gif" minOccurs="0" name="image" type="xsd:string">
<xsd:annotation>
<xsd:documentation>image of the button</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="rowAction" type="lum_rowAction">
<xsd:annotation>
<xsd:documentation>
Indicates that the button is going to be a row action. Row actions are those actions that performs some processing over the table items, such as delete and edit.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="onClick" type="lum_base:onClientEvent"/>
</xsd:sequence>
<xsd:attribute default="STR_LOCK" name="text" type="xsd:string" use="optional"/>
<xsd:attribute default="false" name="isPrimary" type="xsd:boolean" use="optional">
<xsd:annotation>
<xsd:documentation>
Indicates whether the button is a primary button. Primary buttons are emphasized over non-primary buttons.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="lum_editButton">
<xsd:complexContent>
<xsd:extension base="lum_base:lum_sourceBoundControl">
<xsd:sequence minOccurs="0">
<xsd:element default="lumis/portal/client/images/Edit.gif" minOccurs="0" name="image" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="0" name="rowAction" type="lum_rowAction">
<xsd:annotation>
<xsd:documentation>
Indicates that the button is going to be a row action. Row actions are those actions that performs some processing over the table items, such as delete and edit.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="onClick" type="lum_base:onClientEvent"/>
</xsd:sequence>
<xsd:attribute default="STR_EDIT" name="text" type="xsd:string" use="optional"/>
<xsd:attribute name="interfaceId" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
By default the edit interface opened when you press this button will use the following rules in precedence order:
1)Interface Id explicitly in as an attribute
2)Interface (if exists) with id = "edit"+currentInterfaceId with first letter in upper case. e.g. if the current interface is administration, the interface calculated will be editAdministration
3)Interface (if exists) with id = "edit"

If none of these rules apply, the button control will remove itself from its parent.
If the destination interface has been placed within a page of the portal, this button will redirect to that page.
If the destination interface has not been placed in a page, the button will open a popup page with the given interface mounted run-time.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="false" name="keepParentActive" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
<![CDATA[
By default, a "keepParentActive" attribute with value "false" is used on the onClick event for opening the destination interface for this edit button.
By specifying this attribute on the edit button, it will be used when generating its onClick event.
<p>
For more information, see keepParentActive attribute on the onClick element.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="openRuntimeInterfaceBehavior" type="lum_base:openRuntimeInterfaceBehavior">
<xsd:annotation>
<xsd:documentation>
<![CDATA[
By default no openRuntimeInterfaceBehavior on the onClick generated for the edit button.
If a value is specified in this attribute, it will be used on the onClick event for opening the destination interface for this edit button.
<p>
For more information, see openRuntimeInterfaceBehavior attribute on the onClick element.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="listControlId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Identifier of the list control that this button is associated to. If not specified the id of the first control of type lum_advancedTabularData, lum_details or lum_tabularData (in this order of preference) in the interface is used.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="parameterId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
By default the edit button passes the primary key value with a parameter name as the field id. If you want to change the name of the parameter that is being passed to the edit property page, set this value to the desired name.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="false" name="isPrimary" type="xsd:boolean" use="optional">
<xsd:annotation>
<xsd:documentation>
Indicates whether the button is a primary button. Primary buttons are emphasized over non-primary buttons.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="lum_deleteButton">
<xsd:complexContent>
<xsd:extension base="lum_base:lum_sourceBoundControl">
<xsd:sequence minOccurs="0">
<xsd:element default="lumis/portal/client/images/Delete.gif" minOccurs="0" name="image" type="xsd:string">
<xsd:annotation>
<xsd:documentation>image of the button</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="rowAction" type="lum_rowAction">
<xsd:annotation>
<xsd:documentation>
Indicates that the button is going to be a row action. Row actions are those actions that performs some processing over the table items, such as delete and edit.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="onClick" type="lum_base:onClientEvent"/>
</xsd:sequence>
<xsd:attribute default="STR_DELETE" name="text" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
text that will be displayed within the button. Default value is STR_DELETE (translated to the current language)
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="delete" name="processActionId" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
identifier of the process action that should be called when this button is pressed.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="listControlId" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
identifier of the list control that the delete process action should take its item to delete values from.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="false" name="isPrimary" type="xsd:boolean" use="optional">
<xsd:annotation>
<xsd:documentation>
Indicates whether the button is a primary button. Primary buttons are emphasized over non-primary buttons.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="lum_buttonList">
<xsd:complexContent>
<xsd:extension base="lum_base:lum_control">
<xsd:attribute default="LumButton1" name="listClassId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Class that will be placed in the HTML element that represents this button list. This class is generally used to affect visualization via CSS.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="align" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Deprecated.
controls alignment of buttons. One possible value is "right".
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="false" name="isVertical" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Deprecated.
defines whether the controls within this list are vertially positioned.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="true" name="spacer" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Deprecated.
specifies whether there should be a spacer between the buttons.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:simpleType name="additionalButtonsInsertPosition">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="before">
<xsd:annotation>
<xsd:documentation>
Signifies that the additional buttons will be placed before the default buttons.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="after">
<xsd:annotation>
<xsd:documentation>
Signifies that the additional buttons will be placed after the default buttons. This is the default value.
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="lum_autoAdminListButtons">
<xsd:complexContent>
<xsd:extension base="lum_base:lum_control">
<xsd:sequence minOccurs="0">
<xsd:element maxOccurs="1" minOccurs="0" name="replaceButtons">
<xsd:annotation>
<xsd:documentation>
Include any buttons here that will replace an auto layout buttons. (types: lum_addButton, lum_editButton, lum_deleteButton, lum_lockButton, lum_configureButton)
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence minOccurs="1">
<xsd:group ref="control:lum_anyControl"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="additionalButtons">
<xsd:annotation>
<xsd:documentation>
Include any additional button here that will be placed after all auto layout buttons.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence minOccurs="1">
<xsd:any maxOccurs="unbounded" processContents="skip"/>
</xsd:sequence>
<xsd:attribute default="after" name="insertPosition" type="additionalButtonsInsertPosition" use="optional"/>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="onClick" type="lum_base:onClientEvent"/>
</xsd:sequence>
<xsd:attribute name="addInterfaceId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Interface that should be opened when the add button is pressed.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="editInterfaceId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Interface that should be opened when the edit button is pressed.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="delete" name="deleteProcessActionId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Process action Id that should be called when the delete button is pressed.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="lock" name="lockProcessActionId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Process action Id that should be called when the (un)lock button is pressed.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="configureInterfaceId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Interface that should be opened when the configure button is pressed.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>
XML Schema documentation generated with DocFlex/XML (Kit) v1.6.2
DocFlex/XML is a powerful template-driven documentation and report generator from any data stored in XML files. Based on an innovative technology developed by FILIGRIS WORKS, this new tool offers virtuoso data querying and formatting capabilities not found in anything else!
Need to convert your XML data into a clear nice-looking documentation or reports? Web-ready hypertext HTML or printable MS Word / OpenOffice.org friendly RTF? DocFlex/XML may be a cheap, quick and effective solution exactly for this task!
Have questions? Not sure how to use it? Just send us e-mail to contact@filigris.com and we are always happy to help you! See also our services at www.filigris.com

Lumisportal  16.1.2.240429 - Copyright © 2006–2024 Lumis EIP Tecnologia da Informação LTDA. All Rights Reserved.