On the Dependencies tab of an element, you can define the interdependencies of individual elements of a dialog.
Depending on the elements to be linked via a dependency, various actions are possible, for example, you can define that a dialog element is displayed or not depending on whether there is content in a text box or not.
Dependencies can be modeled for the following elements:
The Button element has a name. You can use this element to model buttons that are to be displayed in addition to the existing buttons in a dialog.
On the Data tab, you can specify whether the element is a mandatory field, is read-only, or is subject to voting.
The Check box element consists of a name and the check box itself. The check box represents a Boolean value. Inline editing is possible.
On the Data tab, you can specify whether the element is a mandatory field, is read-only, or is subject to voting. You can activate report support here, too. Enter the GUID of the relevant report in the Default ID of report field. If you do so, the data will be determined by report right before the dialog is displayed and will then be displayed in the dialog.
Example code for the report support
Context.setProperty("375ade20-6ea5-11e6-1af0-504e43.value", "true");
The Check box list element has a label and several check boxes. You can define the number of check boxes. The label can be deleted on the Display tab or by clearing the Has label check box.
On the Data tab, you can specify whether the element is a mandatory field, is read-only, or is subject to voting. You can activate report support here, too. Enter the GUID of the relevant report in the Default ID of report field. If you do so, the data will be determined by report right before the dialog is displayed and will then be displayed in the dialog.
Further check boxes can be added on the List entries tab.
Example code for the report support
Example with three check boxes with default value true for the second check box.
Context.setProperty("375ade20-6ea5-11e6-1af0-504e43.value","false,true,false");
The Static combo box element has a label. The label can be deleted on the Display tab or by clearing the Has label check box.
On the Data tab, you can specify whether the element is a mandatory field, is read-only, or is subject to voting. You can activate report support here, too. Enter the GUID of the relevant report in the Default ID of report field. If you do so, the data will be determined by report right before the dialog is displayed and will then be displayed in the dialog.
Further list entries can be added on the List entries tab. You can assign a name and a value to the individual entries in this list.
Example code for the report support
Context.setProperty("375ade20-6ea5-11e6-1af0-504e43.value","2");
If you enter the list entries of the static combo box during design time as follows and if you use the code above, the value 2 with the label b is set in the dialog during runtime.
The Dynamic combo box element has a label. The label can be deleted on the Display tab or by clearing the Has label check box.
On the Data tab, you can specify whether the element is a mandatory field, is read-only, or is subject to voting. You can activate report support here, too. Enter the GUID of the relevant report in the Default ID of report field. If you do so, the data will be determined by report right before the dialog is displayed and will then be displayed in the dialog.
Further list entries can be added on the List entries tab. You can assign a name and a value to the individual entries in this list.
The values for dynamic combo boxes are not localizable. Values and labels will always be the same for each combo box entry. Available values can be defined during runtime.
Example code for the report support
Context.setProperty("availableValues","1,2,3,4");
Context.setProperty("375ade20-6ea5-11e6-1af0-504e43.value","2");
Date and time
The Hyperlink element has a name and represents either a hyperlink (for example, http://www.softwareag.com), or a shortcut to ARIS Architect models. Inline editing is possible.
On the Data tab, you can specify whether the element is a mandatory field, is read-only, or is subject to voting. You can activate report support here, too. Enter the GUID of the relevant report in the Default ID of report field. If you do so, the data will be determined by report right before the dialog is displayed and will then be displayed in the dialog.
Example code for the report support
Context.setProperty("375ade20-6ea5-11e6-1af0-504e43.value", "http://www.myServer/myPage.htm");
The Info pane element has a name and several text lines that are displayed when the task is being edited, for example, as an editing note. The executor cannot change the text.
The Input table item has a name and represents a table. You can define the number of lines. On the Display tab, you can change the name and specify it in various languages. You can specify whether a hyperlink is displayed only with an icon or with an icons and a text.
You can activate report support on the Data tab. If you do so, the data will be read from ARIS by a report right before the dialog is displayed and will then be displayed in the dialog when the task is opened for editing. You can dynamically change the displayed name (label) of all elements using a report. If the task is displayed read-only, the report is not executed.
You can use the Columns tab to edit the number and position of columns. The number of rows depends on the number of entries in a list that are connected to the corresponding column in the data flow. Use the Item type column on the Columns tab to define the item type to be displayed when editing a task in the dialog. These are available:
Check box
Hyperlink
Text box
Option button
You can define dependencies among columns on the Column dependencies tab. For example, if the source column contains a check box that can be enabled or disabled, it affects the behavior of the target column. The target column could then contain different text. You can only define dependencies between two columns.
Note that you must define all behaviors. For example, if the check box in the first column is enabled, you also have to specify the behavior if the check box in the first column is not enabled.
Example code for the report support
Context.setProperty("375ade20-6ea5-11e6-5023875e3a.column1", "value1, value2");
You can set the value(s) for option button columns the same way as for all other column types via report-support. The code for four option buttons, where the last one is ticked, looks as follows:
Context.setProperty("columnName","false,false,false,true");
The Label element consists of a single text line. Inline editing is possible.
The List element has a label and contains list entries. Multiple selection is possible. You can define the number of lines.
The label can be deleted on the Display tab or by clearing the Has label check box.
On the Data tab, you can specify whether the element is a mandatory field, is read-only, or is subject to voting.
Further list entries can be added on the List entries tab.
When the process is run, the values modeled in the data flow are applied to the list entries.
Example code for the report support
Context.setProperty("375ade20-6ea5-11e6-1af0-504e43.value","3");
The Number field element has a label and is used for entering numbers. It is a spin box with arrows for increasing or reducing the numerical value. Values can also be entered directly. The label can be deleted on the Display tab or by clearing the Has label check box. Inline editing is possible.
You can activate report support on the Data tab. If you do so, the data will be read from ARIS by a report right before the dialog is displayed and will then be displayed in the dialog when the task is opened for editing. You can dynamically change the displayed name (label) of all elements using a report. If the task is displayed read-only, the report is not executed.
Example code for the report support
Context.setProperty("375ade20-6ea5-11e6-1af0-504e43.value","1");
The Password element has a label and is used for entering a password if the dialog is edited by a user while a process is being run. A period (.) is shown on the screen for each character entered.
The label can be deleted on the Display tab or by clearing the Has label check box.
On the Data tab, you can specify whether the element is a mandatory field, is read-only, or is subject to voting.
Inline editing is possible.
The Period element has a label and is used for entering a duration. The label can be deleted on the Display tab or by clearing the Has label check box.
It consists of two parts - a spin box for selecting the duration and a list for selecting the unit (days, hours, minutes, or seconds).
On the Data tab, you can specify whether the element is a mandatory field, is read-only, or is subject to voting.
The Option button group element has a label. The label can be deleted on the Display tab or by clearing the Has label check box.
The available values whether the option buttons are ticked or not, can be passed at design time or dynamically during the process runtime by a dataflow or a report. Only one option button in such a group can be checked at any one time.
Further option buttons can be added on the List entries tab. You can assign a name and a value to the individual option buttons in this list.
Example code for the report support
Context.setProperty("availableValues","Yes,No,Maybe");
Context.setProperty("value","No");
The Text area element has a label and allows multiple text lines to be entered. You can specify the number of lines to be displayed at runtime. The label can be deleted on the Display tab or by clearing the Has label check box. Inline editing is possible.
On the Data tab, you can specify whether the element is a mandatory field, is read-only, or is subject to voting. You can activate report support here, too. Enter the GUID of the relevant report in the Default ID of report field. If you do so, the data will be determined by report right before the dialog is displayed and will then be displayed in the dialog.
Example code for the report support
Context.setProperty("375ade20-6ea5-11e6-1af0-504e43.value","This is my first line.,This is my second line.");
The Text box element has a label and is used for entering a single text line. The label can be deleted on the Display tab or by clearing the Has label check box. Inline editing is possible.
On the Data tab, you can specify whether the element is a mandatory field, is read-only, or is subject to voting. You can activate report support here, too. Enter the GUID of the relevant report in the Default ID of report field. If you do so, the data will be determined by report right before the dialog is displayed and will then be displayed in the dialog.
You can specify a validation. This means that the input in the dialog will be checked when a task is edited. The following validations are available:
No validation (text box input is not checked)
Must not be specified (the box must not be completed)
Must be specified (the box must be completed)
E-mail address (a valid e-mail address must be entered)
Floating point number (a valid floating point number must be entered)
Example code for the report support
Context.setProperty("375ade20-6ea5-11e6-1af0-504e43.value","This is my text.");
The User element consists of a label and Browse. If this button is clicked during editing of a human task, a dialog showing all active users opens. Active users are users that have been modeled as active users in the organizational chart or defined by LDAP.
The label can be deleted on the Display tab or by clearing the Has label check box.
On the Data tab, you can specify whether the element is a mandatory field, is read-only, or is subject to voting. You can also specify whether only users, user groups (and their quantity) or both are allowed. When running the dialog, the users or user groups offered for selection will change accordingly.
The dialog shown here is visible only when executing the process, not during the dialog test.
In the Find window, you can search for users, user groups, or login IDs. The Search result area displays the search result, that is, all active users and user groups that exist
in the system. They can be selected by double-clicking. You remove them from the selection
using Delete. To display all persons belonging to a user group, double-click the relevant user
group.
Example code for the report support
Context.setProperty("usergroupFilter","MyGroup");
To set the list of selected users and user groups, specify their names as a comma-separated String:
Context.setProperty("selection","jsmith,jdoe,jadoe");