DT411 Data Field
DI000213 DI
ID of the data item
DI002060 Data item
Name of the data item. This name is displayed as a data field heading in the modules.
Note
- The displayed data field heading in the module can also be overwritten by making an entry in the DF heading field.
DI000984 DT
Data table from which the data item stems
DI010200 DF heading
Here, an individual heading can be defined for each data field of a data area. The entry defined here is displayed in the user view of the module instead of the name displayed in
Data Field. For buttons or context menu entries (
DF behavior c... and m...), this entry is displayed instead of the module name of the module to be opened.
Notes
- If the data field heading for a particular field is not to be displayed in an area which is no form (Layout parameter = 0 or 1), you have to enter ASCII code 0160 to generate a non-breaking space. To do so, you have to hold down the ALT key while you enter the four digits.
- In this field, variables(@D, @G and @(System variables) can be used, the values of which are read when the module is opened. Use a double @ to make sure that the variable (e.g. @D) is not read but an @ sign is actually output in the field. E.g., @@D15 is written in the DF heading, the text @D15 is displayed in the module heading.
DI041088 DF Python ID
Identifier of a data field. It is used in connection with Python to identify the data field.
Notes
- Names must be usable as Python literals. They must not contain blanks, umlauts, special characters, etc.
- The DF python ID must be uniquely defined in the system.
- Individual Python IDs must start with an L and the license number.
- This value can also be preset on the data item in the DI Python ID data field.
- In this case, the preset Python ID and the "DI:" entry are displayed.
- If the Python ID in the DI is, e.g., "requested_start", "DI: requested_start" is written in the DF Python ID data field.
- The preset value can be overwritten. If this value is deleted, the preset from the data item is displayed again.
- The Python IDs of default data fields cannot be changed.
DI000307 DF
ID of the data field
DI000203 Traffic DI
When you enter a traffic light DI here, the
traffic light function will take effect.
Note
- The traffic light symbols overwrite the symbol stored in the Symbol ID data field.
DI027481 Action ID
Here, the ID of the objects which are addressed when carrying out an
action is entered.
From DB 39.5.11
Details
- A listbox which offers frequently used macros as well as NEW modules that have been changed within the last 30 days for selection is implemented on the field.
New from DB 39.5.8
Details
- A listbox which offers the modules that have been changed within the last 30 days for selection is implemented on the field.
Actions can be defined for data fields with the following
DF behavior:
From DB 39.5.14
- c2, c4, c5
- d2, d4, d5
- e2, e4, e5
- f2, f4, f5
- g2, g4, g5
- m4, m5
From S 39.5.25
c1, c2, c4, c5
d1, d2, d4, d5
e1, e2, e4, e5
f1, f2, f4, f5
g1, g2, g4, g5
m1, m4, m5 Up to S 39.5.25
c1, c2, c4
d1, d2, d4
e1, e2, e4
f1, f2, f4
g1, g2, g4
m1, m4
DI000111 LBMOD
Here, the
ID of the listbox module is stored for
DF behavior = "li"/"le".
New from DB 39.5.8
Note
- A listbox which offers the modules that have been changed within the last 30 days for selection is implemented on the field.
DI010190 Action
Name of the module, menu item, or macro entered in the
Action ID field which is addressed when an
action is carried out
Details
- In the module, this name is used for buttons as well as in the context menu. It can be overwritten by making a deviating entry in the DF heading field.
DI009468 @L variable
Number of the
list variables to be referenced
Details
- The program saves the data field values of marked records in the entered list variable.
Note
- In the target module, @L must be entered for a data field in Filter from
DI000288 Summarization type
From S 39.5.14
Summarization type of the data field
Values
- 0: no summarization (for DFs "Summ. type" from DI)
- 1: sum
- 2: maximum
- 3: minimum
- 4: mean (average)
- 5: never summarize, always calculate NEW
Notes
- If no value is entered here, the value in the Summarization type parameter of the data item (DT412) applies to the target module.
- If the value entered here deviates from that of the DI, the value of the DF overwrites the value of the DI.
- NEW Summarization type = 5 on a data item (DT412) prevents any summarization and does not allow deviating summarization types in the data field (DT411). For fields with relative values, e.g. percentage specifications, summarization basically does not make any sense. The Never summarize, always calculate summarization type on the data item provides the customizer with a means to prohibit this effectively.
- If a summarization type is neither stored on the Summarization type parameter of the data field (DT411) nor on the parameter of the same name of the data item (DT412), the following default summarization type is used:
- Alphanumeric: maximum
- Numeric: sum
- Date fields: maximum
- The values of the checkbox fields are not summarized, the checkboxes are always displayed as deactivated
- Due to the rounding of individual fields, an incorrect sum may be displayed since it is calculated from the exact values and displayed rounded afterwards due to formatting.
Up to S 39.5.14
Values
- 0: no summarization (for DFs "Summ. type" from DI)
- 1: sum
- 2: maximum
- 3: minimum
- 4: mean (average)
Notes
- If no value is entered here, the value in the Summarization type parameter of the data item (DT412) applies to the target module.
- If the value entered here deviates from that of the DI, the value of the DF overwrites the value of the DI.
- If a summarization type is neither stored on the Summarization type parameter of the data field (DT411) nor on the parameter of the same name of the data item (DT412), the following default summarization type is used:
- Alphanumeric: maximum
- Numeric: sum
- Date fields: maximum
- The values of the checkbox fields are not summarized, the checkboxes are always displayed as deactivated
- Due to the rounding of individual fields, an incorrect sum may be displayed since it is calculated from the exact values and displayed rounded afterwards due to formatting.
DI001706 Grid
Values
- For histogram data fields:
- The grid specifies the scale graduations of the histogram scale.
- Example: When Grid = 100, the y axis of the scale is divided into steps of hundreds (100, 200, 300, etc.).
- For time scale data fields (division of the x axis of the time scale):
- 2: day
- 3: week
- 4: month
- 5: quarter
- 6: year
Note
- The size of the scale can be customized via the Scale and Grid data fields.
DI040119 LB: value transfer
This parameter determines which data field from the
listbox is transferred.
Values
- : The data field is copied from the listbox.
- : The data field is not copied.
Notes
- You have to make sure that this parameter is used reasonably.
- I.e., for listboxes on project ID fields, the LB: Copying values parameter should be activated for the project ID, not for the name.
- If this parameter is activated for no data field in a listbox, nothing from the list can be copied.
- The parameter can only be activated for one data field in the data area. If it is activated for another data field in addition, the activation is deleted for the first data field.
- If this parameter is activated, the LB: part string search field is activated automatically.
DI040815 LB: Part string search
This parameter defines for the
Listbox modules, which data fields are considered in the
part string input.
Values
- : The data field is considered in the part string search.
- : The data field is not considered in the part string search.
Details
- If the LB: copying values parameter is activated for a data field, this parameter is activated automatically. It can, however, be deactivated manually.
- In a listbox module, you can also set multiple fields or no field at all for the substring search.
Example
- This way you cannot only input the table in the listbox of the DT data field in the Data Dictionary, but also the beginning of the table name in order to filter the LB contents.
Note
- If a listbox contains the value to be copied, a respective name, and an additional detailed description, it is recommended to only use value and name in the part string search. If you include the explanation in the continuous text, this is likely to produce too many unintentional hits.
DI040118 Input only via listbox
If this parameter is activated, data field input is restricted to the values from the
listbox.
Values
- : Data field input is restricted to values from the listbox.
- : Data field input is not restricted.
Note
- If a value which is not contained in the listbox is entered in a listbox data field manually or via Drag&Drop, the input is ignored and the field remains empty. The user must repeat the input or select a valid value from the listbox.
DI001995 Window
Specifies in which of the module's sub-windows the data field will be displayed. The following division description applies to PLANTA Standard. In customized solutions, the files can be divided differently, according to customer requirements.
Details
- Window 1: Left-hand data window
- Identifying data (e.g. idents and names)
- Window 2: Central data window
- Other data (e.g. dates and durations)
- Window 3: Right-hand data window
- Scale fields and items displayed under a scale (e.g. bars).
- Window 9: Invisible data window
- Fields that are not visible when starting the module but can be displayed by the user. They have the DF options checkbox activated.
- Fields that are neither visible in the module nor displayed by the user, but that are visible in the filter criteria. They have the Filter criteria checkbox activated and the DF options deactivated.
- Fields that are completely invisible for users. They can neither be displayed by the user, nor be viewed in the filter criteria. Both the DF options and the Filter criteria checkboxes are deactivated.
Notes
From DB 39.5.11
- NEW If a field in a data area is moved to an invisible window (window 9), the Filter criteria and DF options parameters are deactivated automatically.
- If a field is to be displayed in window 1 (or window 2), you have to enter a value in the Width W2 (or Width W3) data field in the Other Module Parameters module.
- Upon creation of a new module in the Modules module, a width for window 1 is defined in Width W1. Hence, no explicit width must be allocated here.
Up to DB 39.5.11
If a field is to be displayed in window 1 (or window 2), you have to enter a value in the Width W2 (or Width W3) data field in the Other Module Parameters module.
Upon creation of a new module in the Modules module, a width for window 1 is defined in Width W1. Hence, no explicit width must be allocated here.
DI000221 DF behavior
Here, the data field behavior is defined.
From DB 39.5.14
Function |
Value |
See also |
Background |
a |
|
Action on OLE |
a2: menu item a4: module/macro a5: module subclass |
NEW When selecting one of these values, symbol 000984 is automatically entered on the respective data field and the DF height = 40 is allocated to optimize the OLE representation. See also: Customize Actions on OLE |
Blind field (e.g. password fields) |
b |
|
Bar |
ba |
|
Button |
c1: module c2: menu item c4: module/macro c5: module subclass |
See also: Customize Buttons |
Date listboxes (for date data fields) |
cc |
See also: Customize date listboxes |
Overwrite menu item |
d1: with module d2: with menu item d4: with module / with macro |
See also: Overwrite Menu Item |
Link |
e1: module e2: menu item e4: module/macro c5: module subclass |
See also: Customize Link |
Action when double clicking |
f1: module f2: menu item f4: module/macro f5: module subclass |
|
Action when pressing Enter |
g1: module g2: menu item g4: module/macro g5: module subclass |
|
Hyperlink |
h |
See also: Embed hyperlink |
Hotkey |
hk |
|
Hyperlink for output |
ho |
|
Input field (input) |
i i2: checkbox - only for y types |
|
Listboxes |
li: implicit le: explicit |
See also: Customize listboxes |
Context menu |
m1: module m4: module/macro m5: module subclass |
See also: Customize Context Menu |
Markdown |
mi: input mo: output |
|
Output field (output) |
o o2: checkbox - only for y types |
|
IronPython script |
py |
|
Note
- To open a method with data field behavior *5, it must have the following signature:
def my_method(self, apllied_dfc, clicked_df):
pass
From S 39.5.27 and C39.5.26
Function |
Value |
See also |
Background |
a |
|
Action on OLE NEW |
a2: menu item a4: module/macro a5: Module subclass |
The behavior itself is available from version S 39.5.27 with C 39.5.26. The listbox on the DF behavior field contains the respective values by default from version DB 39.5.13. See also: Customize Actions on OLE |
Blind field (e.g. password fields) |
b |
|
Bar |
ba |
|
Button |
c1: module c2: menu item c4: macro c5: module subclass |
See also: Customize Buttons |
Date listboxes (for date data fields) |
cc |
See also: Customize date listboxes |
Overwrite menu item |
d1: with module d2: with menu item d4: with macro |
See also: Overwrite Menu Item |
Link |
e1: module e2: menu item e4: macro c5: module subclass |
See also: Customize Link |
Action when double-clicking |
f1: module f2: menu item f4: macro f5: module subclass |
|
Action when pressing ENTER |
f1: module g2: menu item g4: macro g5: module subclass |
|
Hyperlink |
h |
See also: Embed hyperlink |
Hotkey |
hk |
|
Hyperlink for output |
ho |
|
Input field (input) |
i i2: checkbox - only for y types |
|
Listboxes |
li: implicit le: explicit |
See also: Customize listboxes |
Context menu |
m1: module m4: macro m5: module subclass |
See also: Customize Context Menu |
Markdown |
mi: input mo: output |
|
Output field (output) |
o o2: checkbox - only for y types |
|
IronPython script |
py |
|
Note
- To open a method with data field behavior *5, it must have the following signature:
def my_method(self, apllied_dfc, clicked_df):
pass
From S 39.5.25
Function |
Value |
See also |
Background |
a |
|
Blind field (e.g. password fields) |
b |
|
Bar |
ba |
|
Button |
c1: module c2: menu item c4: macro c5: module subclass NEW |
See also: Customize Buttons |
Date listboxes (for date data fields) |
cc |
See also: Customize date listboxes |
Overwrite menu item |
d1: with module d2: with menu item d4: with macro |
See also: Overwrite Menu Item |
Link |
e1: module e2: menu item e4: macro c5: module subclass NEW |
See also: Customize Link |
Action when double-clicking |
f1: module f2: menu item f4: macro f5: module subclass NEW |
|
Action when pressing ENTER |
f1: module g2: menu item g4: macro g5: module subclass NEW |
|
Hyperlink |
h |
See also: Embed hyperlink |
Hotkey |
hk |
|
Hyperlink for output |
ho |
|
Input field (input) |
i i2: checkbox - only for y types |
|
Listboxes |
li: implicit le: explicit |
See also: Customize listboxes |
Context menu |
m1: module m4: macro m5: module subclass NEW |
See also: Customize Context Menu |
Markdown |
mi: input mo: output |
|
Output field (output) |
o o2: checkbox - only for y types |
|
IronPython script |
py |
|
Note
NEW
- To open a method with data field behavior *5, it must have the following signature:
def my_method(self, apllied_dfc, clicked_df):
pass
From DB 39.5.8
Function |
Value |
See also |
Background |
a |
|
Blind field (e.g. password fields) |
b |
|
Bar |
ba |
|
Button |
c1: module c2: menu item c4: macro |
See also: Customize Buttons |
Date listboxes (for date data fields) |
cc |
See also: Customize date listboxes |
Overwrite menu item |
d1: with module d2: with menu item d4: with macro |
See also: Overwrite Menu Item |
Link |
e1: module e2: menu item e4: macro |
See also: Customize Link |
Action when double-clicking |
f1: module f2: menu item f4: macro |
|
Action when pressing ENTER |
f1: module g2: menu item g4: macro |
|
Hyperlink |
h |
See also: Embed hyperlink |
Hotkey |
hk |
|
Hyperlink for output |
ho |
|
Input field (input) |
i i2: checkbox - only for y types |
|
Listboxes |
li: implicit le: explicit |
See also: Customize listboxes |
Context menu |
m1: module m4: macro |
See also: Customize Context Menu |
Markdown NEW |
mi: input NEW mo: output NEW |
|
Output field (output) |
o o2: checkbox - only for y types |
|
IronPython script |
py |
|
Up to DB 39.5.8
Function |
Value |
See also |
Background |
a |
|
Blind field (e.g. password fields) |
b |
|
Bar |
ba |
|
Button |
c1: module c2: menu item c4: macro |
See also: Customize Buttons |
Date listboxes (for date data fields) |
cc |
See also: Customize date listboxes |
Overwrite menu item |
d1: with module d2: with menu item d4: with macro |
See also: Overwrite Menu Item |
Link |
e1: module e2: menu item e4: macro |
See also: Customize Link |
Action when double-clicking |
f1: module f2: menu item f4: macro |
|
Action when pressing ENTER |
f1: module g2: menu item g4: macro |
|
Hyperlink |
h |
See also: Embed hyperlink |
Hotkey |
hk |
|
Hyperlink for output |
ho |
|
Input field (input) |
i i2: checkbox - only for y types |
|
Listboxes |
li: implicit le: explicit |
See also: Customize listboxes |
Context menu |
m1: module m4: macro |
See also: Customize Context Menu |
Output field (output) |
o o2: checkbox - only for y types |
|
IronPython script |
py |
|
DI002926 Mandatory
Here, you can define whether a data field is a
mandatory data field.
Values
- : This data field is a mandatory field. When a record is created or changed, an entry must be made in this data field. Otherwise, the changes will not be saved.
- : This data field is no mandatory field.
Note
- For mandatory data fields, an * is displayed automatically behind the heading.
DI000223 Default value
Here, the respective value is entered, with which the respective data field is filled by default upon creation of a record. The data area should have
Create =
.
Details
- If the required data field is contained in a subordinate area which is set to Create = , but is to be filled with a default value when creating a parent data area, the data field must additionally be included in the creation area with its default value and possibly be set to Window = 9.
Special values
- @/@D/@G/@U: the value of a variable (e.g. today's date or resource) is entered.
DI000220 Sort sequence
Here, the number which specifies the order by which is sorted within the respective data area is input/output. A minus sign (e.g. -1) means: sorting in descending order.
Details
- The sorting criteria take effect when carrying out a search or clicking on the Sort menu item.
- Sorting only takes effect within a data area.
- It must be specified sequentially.
DI001714 Filter from
Here, you can
set filter criteria by which the data of a module is filtered. Absolute values or
variables can be entered.
Details
- The field can be preset by the customizing. In such a case, the data is filtered when the module is opened.
- Or the user can fill the field himself/herself with the required value in the Filter Criteria module. In such a case, the data is filtered after clicking on the Filter or Filter additively button.
Notes
- For virtual data fields, the value in this field is marked red and bold.
- If no filter criteria have been preset, all data will be found when filtering.
- If you often filter on the same data field, it is recommendable to set a respective index in the database.
DI001718 Filter to
For description, see
Filter from
DI040816 Regular expression
In this field, regular expressions for
filtering are stored.
DI056857 Use filter on
Values
- 0: Everywhere
- For structures, the filter is used on every level.
- 1: Only on top level
- Filter only takes effect on top level (only usable for structures)
- 2: Not on top level
- Filter does not take effect on top level (only usable for structures)
Example
- The IT-ST resource has the child resources R48 and R9.
- In the Resource Structure module, only the IT-ST resource and the parent external resource are displayed (here R9).
- For this purpose, enter
- "IT-ST" in Filter from and = 1 in Use filter on for the Resource (Resource ID) data field
- = 1E in Filter from and = 2 in Use filter on for the Resource type data field
- Result: After opening the module, only the IT-ST resource and the subordinate resource R9 are displayed.
DI056858 Filter deactivated
If this parameter is activated, all entries in the
Filter from,
Filter to,
Regular expression, and
Use filter on parameters of the respective data item are ignored when filtering. In order to illustrate this, all 4 fields are highlighted in gray.
DI000234 Symbol ID
ID of the symbol that is to apply to the data field
Notes
Details
- For the data field heading, the symbol defined in the Heading symbol ID parameter applies.
DI002031 Symbol
Preview of the data field symbol which is defined via the
symbol ID parameter
DI010197 Hdg symbol ID
ID of the data field heading symbol
Note
- If a symbol for the data field heading is entered on data field level, it overrides a possibly existing deviating heading symbol on skin level (Symbol heading in DT030).
DI010201 Hdg symbol
Preview of the data field symbol which is defined via the
Hdg. symbol ID parameter
DI029731 Effect ID
ID of the data field effect
Notes
- The effect takes effect on the entire field content (font and background).
DI000258 Format ID
Here, the ID of a date or number format is for the data item entered/displayed.
Note
- The format specified here overrides deviating formats for the corresponding data field which are possibly specified on other levels:
DI002076 Format
Here, a preview of the format which has been specified for the selected data field in the
Format ID parameter is displayed.
DI003701 DF height
Here, the height of the data field in the selected data area is displayed/defined.
Values
- Specified in tenths of a millimeter
DI003703 DF width
Here, the width of the data field in the selected data area is displayed/defined.
Values
- Specified in tenths of a millimeter
Notes
- If the heading or the value of the data field cannot be displayed in the set width at the surface of the respective module, the data is truncated and displayed with an ellipsis.
- If the cursor is positioned over the truncated data, the complete data is displayed in a tool tip.
DI027098 Hdg height
Here, the height of the data field heading in the selected data area is displayed/defined.
Values
- Specified in tenths of a millimeter
DI027099 Hdg width
Here, the height of the heading in the data area is displayed/defined.
Values
- Specified in tenths of a millimeter
DI000232 Y pos. H
Here, the y position of the data field heading in the selected data area is displayed/defined.
Values
- Specified in tenths of a millimeter
Notes
- This parameter only takes effect in data areas with Layout = 2 (form).
- Data field headings cannot be displayed in the module without the corresponding data fields.
DI000233 X pos. H
Here, the x position of the data field heading in the selected data area is displayed/defined.
Values
- Specified in tenths of a millimeter
Notes
- This parameter only takes effect in data areas with Layout = 2 (form).
- Data field headings cannot be displayed in the module without the corresponding data fields.
DI000230 Y pos. W
Here, the y position of the data field in the selected data area is displayed/defined.
Values
- Specified in tenths of a millimeter
Notes
- This parameter only takes effect in data areas with Layout = 2 (form).
- Data fields can be displayed in the module without the corresponding data field headings.
DI000231 X pos. W
Here, the x position of the data field in the selected data area is displayed/defined.
Values
- Specified in tenths of a millimeter
Notes
- This parameter only takes effect in data areas with Layout = 2 (form).
- Data fields can be displayed in the module without the corresponding data field headings.
DI022738 Alignment
From S 39.5.0
Defines the alignment of the data field.
Values
- 0: No alignment
- 1: Left aligned
- 2: Centered NEW
- 3: Right aligned
Notes
- Checkboxes are always centered, regardless of the alignment.
- Number fields are right-aligned and text fields are left-aligned by default.
Up to S 39.5.0
Defines the alignment of the data field.
Values
- 0: No alignment
- 1: Left aligned
- 3: Right aligned
Notes
- The parameter has no effect on checkboxes. Checkboxes are always centered, regardless of the alignment.
- Number fields are right-aligned and text fields are left-aligned by default.
DI001992 Pos.
Automatically incrementing number. When moving via
Drag&Drop and creating a data field, the pos. is set automatically. In modules in which data fields are created, this field should be included in window 9 as the first order criterion.
Note
- The position is the tab order of the data fields at the same time.
DI040869 Hotkey
The entered value defines a shortcut for activating the corresponding button.
Example:
- Value: A
- In the module, the respective button can be activated via the ALT + A key combination.
DI040918 Tooltip
Here, an individual tooltip can be stored. It is displayed if you move the cursor over the corresponding field in the target module.
The following external variables can be used
From S 39.5.17
Field type |
Variables |
Notes/Examples |
Regular data fields |
@uid - DF ID of the data fields @content - Content of the data field is displayed. |
|
Bar |
@startDateH(date format) - start date of the bar is displayed @endDateH(date format) - end date of the bar is displayed @duration - number of days between start and end date is displayed @wdDuration - number of days between start and end date, excluding weekends and holidays, is displayed @ds, @de - start date/end date NEW @ms, @me - start month/end month NEW @qs, @qe - start quarter/end quarter NEW @ws, @we - start week/end week NEW @ys, @ye - start year/end year of the histogram bar NEW @wys and @wye - start year/end year of the calendar week NEW |
Note: |
Histogram NEW |
@value - value of the histogram bar on which the cursor is placed (e.g. bars for projects with code B) @v_sum - sum of the values for the bars of a group (of a type) (e.g. bars for projects A-E) @hdg - name of the histogram (=DI name of the SUBDI) @ds, @de - start day/end day @ms, @me - start month/end month @qs, @qe - start quarter / end quarter @ws, @we - start week/end week @ys, @ye - start year/end year of the histogram bar @wys and @wye - start year/end year of the calendar week |
|
Example
Up to C 39.5.17
Field type |
Variables |
Notes/Examples |
Regular data fields |
@uid - DF ID of the data fields @content - Content of the data field is displayed. |
|
Bar |
@startDateH(date format) - start date of the bar is output @endDateH(date format) - end date of the bar is output @duration - number of days between start and end date is output @wdDuration - number of days between start and end date, excluding weekends and holidays, is displayed |
Note: - The date format is built from placeholders. The most frequently used placeholders are d for day, m for month, and y for year.
- Further options can be found on the following website: .NET Custom Date and Time Format Strings.
|
Example
Information
- The field is an I-text and is displayed in the translation modules.
DI003388 DF options
With this parameter you can therefore determine whether data fields in the
context menu for hiding/displaying of data fields can be hidden/displayed.
Values
- : The data field can be displayed or hidden.
- : The data field cannot be displayed or hidden.
New from DB 39.5.11
Note
- If a field in a data area is moved to an invisible window (window 9), the DF options parameter is deactivated automatically.
DI059179 Bar modification mode: create bar
Activating this checkbox enables the graphical creation of bars. It is recommended to only set one date type to "creation" (e.g. actual dates or required dates).
DI059181 Bar modification mode: edit dates: "Actual" menu item
Activating the checkbox enables
DI059180 Bar modification mode: edit dates: "Requested" menu item
Activating the checkbox enables
DI059186 Bar modification: link bar
Activating this checkbox enables you to
graphically link the bar,
change the link type by right-clicking, and
delete the link in the Gantt chart.
Requirements
- In the link area, a Linkage DI is available for the bar you wish to link.
DI059183 Bar modification: edit start
Activating this checkbox enables the graphical editing of start dates.
DI059184 Bar modification: edit end
Activating this checkbox enables the graphical editing of end dates.
DI059268 Bar modification: move
Activating this checkbox enables the graphical moving of bars.
DI059185 Bar modification: everything modifiable
Activating this checkbox enables the graphical moving of a bar, as well as the editing of start and end dates.
Note
- When activating this checkbox, the following checkboxes are activated automatically
DI051832 Bar link (DF Python ID)
By entering the
DF Python ID of a bar, this data field becomes an auxiliary bar field. It is displayed at the position defined in the
Docking point parameter.
Note
- The auxiliary bar field must be located in the same field as the respective bar.
DI040921 Bar link (DF ID)
By entering the
DF ID of a bar, this data field becomes an auxiliary bar field of the respective bar. It is displayed at the position defined in the
Docking point parameter.
Note
- The auxiliary bar field must be located in the same field as the respective bar.
DI040917 Docking point
Via this parameter, the position of the auxiliary bar field defined in the
Bar link (DF Python ID) data field, is determined.
Values
- 0: Start date is beginning of bar
- 1: Start date is end of bar
- 2: Start date is center of bar
Tip
- When you use "0” as a value for positioning an auxiliary field infront of the bar, the data field width and the X position of the field should be defined in addition (e.g. DF width = 200, X pos. F = -200), so that the field is not positioned at the bar itself.
DI026689 Multiline
This parameter controls whether line breaks are possible in the respective data field.
Values
- : By pressing ENTER, a line break is inserted. If the DF width is reached, an automatic line break occurs.
- : By pressing ENTER, you navigate to the next input field. If the DF width is reached, the data is displayed truncated with an ellipsis. If the cursor is positioned over the truncated data, the complete data is displayed in a tool tip.
DI027601 Number of lines
From DB 39.5.0
For data fields for which the
Multiline parameter is activated, you can use this parameter to define how many lines may be written in this data field.
Notes
- If the maximum number of lines is reached, no other manual line breaks or no other text can be entered, if this causes an automatic line break. In such a case, the The maximum amount of lines in the continuous text field has been reached message is displayed.
- The corresponding data field is hidden by default and can be displayed by the user if necessary.
- NEW Only values from 0 to 9999 can be entered.
Up to DB 39.5.0
For data fields for which the
Multiline parameter is activated, you can use this parameter to define how many lines may be written in this data field.
Notes
- If the maximum number of lines is reached, no other manual line breaks or no other text can be entered, if this causes an automatic line break. In such a case, the The maximum amount of lines in the continuous text field has been reached message is displayed.
- The corresponding data field is hidden by default and can be displayed by the user if necessary.
DI001993 Filter criteria
This parameter defines whether the data field is displayed in the
Filter Criteria.
Values
- : The data field is available as a search criterion in the options form.
- : The data field is not available as a search criterion in the options form. However, an entry in the Filter from or Filter to takes effect regardless.
Notes
From DB 39.5.11
- NEW If a field in a data area is moved to an invisible window (window 9), the Filter criteria parameter is deactivated automatically.
- Can be used for search criteria which the user can neither see nor change.
- Can be used for data fields which cannot be used as search criteria, e.g.: date/histogram bars, projected/summarized values.
- Especially in multi-user mode, large sequential search runs can cause computer overload. Hence, especially where mass data is affected, we recommend to restrict the filter criteria visible to the user.
Up to DB 39.5.11
Can be used for search criteria which the user can neither see nor change.
Can be used for data fields which cannot be used as search criteria, e.g.: date/histogram bars, projected/summarized values.
Especially in multi-user mode, large sequential search runs can cause computer overload. Hence, especially where mass data is affected, we recommend to restrict the filter criteria visible to the user.
DI029687 DF output
Preview of the data field heading as displayed in the module
DI003102 DF type
The field is automatically filled with the value from the (
DF type) field of DT412.
DI040844 Incarnation DI
The field is automatically filled with the value from the (
Incarnation DI) field of DT412.
DI040843 Fetch Exit DI
The field is automatically filled with the value from the (
Fetch exit DI) field of DT412.
DI040845 DI class
Here, the
Class of the data field is displayed.
DI041524 Listbox module
Here, the title of the listbox module stored in the
LBMOD data field is displayed.
DI041308 DBOLE value
Here, the ID of the OLE object which is used on the data field is displayed. The field is automatically filled as soon as an OLE entry has been made in the
Default value field. For more information, please refer to the
Embed OLEs section of
Module Workflow Level 1.
DI040904 IronPython script
On this parameter you can store IronPython scripts that are carried out on the client. Via these scripts, a value range can be customized on part of the client.
Notes
- In order to run IronPython scripts on the client, the DF behavior must be set to py.
DI040968 Data field configuration
On this parameter you can store configuration parameters for data fields.
Usage
DI056920 Print text
Here, an individual print output text or variables for print output objects can be defined for a
print area.
From C 39.5.13
Possible variables:
- @mod_name - module name
- @cur_column - current column
- @cur_row - current row
- @cur_page_h - current page (horizontal counting)
- @cur_page_v - current page (vertical counting)
- @total_pages - page number
- @date_time(F) NEW - Time specific for the print preview
- @date_time(h:mm:ss) NEW - Time specification
- @date_time(dd.MM.yy HH:mm:ss) NEW - Time for the print preview
- In these variables, only standard format strings can be used. For further information, click here.
Up to C 39.5.13
@mod_name - module name
@cur_column - current column
@cur_row - current row
@cur_page_h - current page (horizontal counting)
@cur_page_v - current page (vertical counting)
@total_pages - page number
DI041307 DBOLE
Preview of the OLE object which has been assigned to the data field
From DB 39.5.0
DI000106 Structure summarization
Summarizes data fields in data areas with
Structural representation =
along the structure (e.g. planned load along the project structure)
Up to DB 39.5.0
DI000106 Stru. summ.
Summarizes data fields in data areas with
Structural representation =
along the structure (e.g. planned load along the project structure)
DI062619 Active
Marks the data field as active or inactive depending on whether the respective data item is active or inactive
Note
- If you try to assign an inactive data item as a data field to a data area, a message indicating this is displayed.