Parameter type "Color table"
The configuration key of the "Color dictionary" parameter type is used to determine the color scheme of statistical values. If the same values occur in different statistics, the values should be viewable in consistent colors. Thus, the "Approved" value is always "green" no matter which statistic this value appears in.
This chapter describes how to edit a configuration key value. Declaring a configuration key is covered in another section of this guide. For more information, see Declaring configuration keys in modules and components.
To edit a configuration key value of the "Color table" parameter type in the "Settings..." view
NOTE: Before you can edit the values in a database column, you must add a matching entry in Configuration (custom). You can recognize this entry because it is marked with an X in the Value (custom) column in the list of configuration keys in the Settings... view of the selected database object.
-
Open the required database object in the definition tree view and select the Settings... view.
- In the Settings... view, select the configuration key of the parameter type "Color table", which you created previously in the Object definitions view.
- Enter the
value - Is equivalent to standard value in the Value (custom) column, by clicking 
.
-
Open the Change color dictionary dialog by clicking 
.
You can add and remove color values in Numbered values and in Predefined values.
- Click in a pane.
A new color bar is shown below the corresponding pane.
- Click the color of the new color bar.
- In the Color dialog, select a color.
- Click Add color.
This displays the selected color under Custom colors.
- Click OK to close the window.
- Perform one of the following actions with the new color bar in Change color dictionary.
- Assign an item in the statistics to the color bar by hovering the mouse over the dashed area of the required color bar in the Numbered values area. Drag this bar to the position of choice whilst holding down the mouse button.
The color bar is now in the right position. If the color bar in in the first position, it will appear in the first position of the statistics. This bar represents the value with the highest priority. The importance of the other bars is set according to their position in the list of color bars.
- Enter a name for the color bar in the corresponding field.
The color bar now has a name. For example, the green color bar is called "Approved".
- Close the Change color dictionary dialog using Apply.
Your settings are saved. The number of selected columns is displayed under Details in the field and in the Settings... view in the Value (custom) column.
Project configuration - customization
This dialog allows you to create and edit substitution rules for module copies. Substitution rules are listed that were added with Copy objects.
NOTE: Substitution rules have higher priority that references in the definition tree. References in the definition tree are no changed in this case.
For example, a substitution rule from both the VI_Delegation module and the Custom_Delegation module copy can exist. The modules are mentioned by way of example in the steps below.
To edit a substitution rule
- In the Edit menu, select Configure project | Customization.
This displays Configure project - Customization. If substitution rules already exist, they are listed here. The following editing options are available in this dialog.
Table 41: Functions in the "Configure project - Customization" dialog
 |
Creates a new substitution rule.
In the Module name column, (no name) is shown and the Module name and Replace by fields are empty. |
 |
Deletes the marked substitution rules from the list. |
| Input field Module name |
Specifies the module name.
When you create a substitution rule the field is empty. Enter the module manually. Edit a substitution rule, overwrite the module name (for example, VI_Delegation) with another module name. |
| Input field Replace by |
Specifies the module copy.
When you create a substitution rule the field is empty. Enter the module copy manually. Edit a substitution rule, overwrite the module copy name (for example, Custom_Delegation with another module copy name. |
- Create an edit rule or modify an existing edit rule.
- Save the changes.
NOTE: If a module is no longer needed, the substitution rules can simply be deleted.
Detailed information about this topic
Project configuration - customization overview
On the Customization overview tab, you can view the modified sections of the configuration. Objects that exist in the object model, can be edited in the definition tree view. The Web Designer jumps directly to the object when you double-click on the respective node. These objects are labeled in the following table.
Table 42: Tab "Customization overview"
|
Configuration parameter |
Modified configuration parameters and subnodes are grouped by document in the list. |
x |
|
Extensions |
Added extensions are grouped by document in the list.
- Extension nodes, for example, "Add node", "Remove node" and "Modify property" are listed under the added extensions.
- Other child elements are listed under the extension node "Add mode".
|
x |
|
Customizations |
Overwritten modules are listed as objects you can also find listed under Edit | Configure project | Customizations. |
x |
|
Column-dependent references |
Lists modified, custom, column dependent references. |
x |
|
Object-dependent references |
Lists modified, custom, object dependent references by reference type, reference, and object. |
|
|
Root node |
Root nodes are always displayed, whether with or without subnodes. This means that no changes have been made. |
|
The following table describes which editing options you have on the Customization overview tab.
Table 43: Functions on the "Customization overview" tab
|
|
Deletes all child elements
- Mark the nodes you want to delete in the tree view and click . All nodes under a root node (Configuration, Extensions) can be edited.
|
|
|
Deletes single nodes, like extension nodes, configuration nodes, customizations, or column or object dependent references.
Deleting single nodes.
|
Statistical references
A component can be referenced in two ways. Normally, a static reference is used to reference components directly using their names.
An example of a static reference is calling the component VI_Popup.
NOTE: It is not possible to use object-dependent references on the login page if the web application is executing against an application server.
Detailed information about this topic
