If more than one simple confirmation is required, input dialogs are used. This allows you to provide the user with one or more text boxes to fill out.
An attribute is defined for each text box. Similar to the object definitions (objectTypes.xml), there are several attribute types available for the individual requirements of the text boxes. You can add validators (<validator>) to these attributes, for example, to limit the scope of the attribute by restricting the number of characters or figures that can be entered in an text box. The names of the XML elements result from the name of the attribute type, that is, <booleanAttribute>, <longAttribute>. You should use naming conventions for the IDs of the attributes, thus facilitating working with the collected data of the dialog. That means, when you transfer an attribute from a dialog to an object, both attributes should have the same name. For example, when create an object, the attribute of the environment selection in the client_sign dialog should have the same name as the corresponding attribute of the object to be created.
Existing attribute types
boolean |
Attribute for Boolean values (Yes/No). |
date |
Attribute for date values. |
double |
Attribute for floating point numbers. |
enum |
Attribute for enumerations (enumerations_*.xml). |
long |
Attribute for integers. |
selection |
Attribute for selecting values from a predefined dynamic list, for example, when selecting an environment. PredefinedValueProvider is available to define the possible values of the selection list. The application contains some of these configurable providers (see below). But you can also implement some providers manually. |
string |
Attribute for simple text text boxes. Content and length of the text can be limited. |
text |
Attribute for texts consisting of several rows. |
There are several PredefinedValueProviders for the selection attribute. They can be parameterized and provide different possibilities.
Existing PredefinedValueProviders
client |
Provides a list of all environments that the user has access to. This list can be limited by a maximum of one of the following parameters:
Additional parameters:
|
static |
Manages a list of elements defined previously in Java code. |
usergroup |
Outputs a list with available user groups. Parameter:
|
view |
Uses a view (views_*.xml) to create a list with elements. The parameters value, id and client require the IDs of the corresponding columns in the view as values. |
In the following example a new dialog is created, which is displayed when creating a new control. Some attributes of the control are queried and then set in the newly created control.
Location |
XML file in the xml folder |
Procedure |
|
Documents |
dialogs.xsd, forms.xsd, dialogs.xml, forms_*.xml |
Example |
AddNewInputDialog \WEB-INF\config\custom\xml\custom.xml: Add custom dialog |