CDF types
CDFs can be defined with standard domains, or your own domains that you can create with LN Studio. If you do not use a standard or own domain, the CDFs are added to the table with an implicit domain that is dependent on the data type.
This table shows the supported data types:
Data Type | Remark | Implicit Domain |
|---|---|---|
String | Multibyte string, length between 1 and 999; default length is 30 | <pk>cdf___str<lll> (3 underscores) |
Integer | Integer number (long) | <pk>cdf______int (6 underscores, for integers with 10 positions and format ZZZZZZZZZ9) <pk>cdf____i<ll><ss> (4 underscores) |
Numeric | Numeric number (double) | <pk>cdf______num (6 underscores, for doubles with 9 digits before and 5 digits after decimal point and format ZZZZZZZZ9VD99999) <pk>cdf__n<bb><aa><ss> (2 underscores) |
Date | Date/Time, local time on screen, stored as UTC | <pk>cdf______dat (6 underscores, for dates with format %u001 %U001) <pk>cdf______u<ss>, 6 underscores) |
Checkbox | true or false | <pk>cdf______chk (6 underscores) |
List | A predefined list of choices | <pk>cdf_lst<list> (1 underscore) |
Text | Text field | <pk>cdf______txt (6 underscores) |
Explanation for the domain codes:
- <pk> the package code of the table to which the CDF is added
- <ll[l]> length of the string or integer
- <ss> sequence number, per format a different sequence number is generated
- <bb> digits before
- <aa> digits after
- <list> list code that holds the predefined list of choices
The domain codes can be required during the development of the extensions with the Extension Modeler.
See Extension Modeler.
You can also add calculated CDFs; those are not physically stored in the table, but calculated based on other table fields and presented in the UI. This type of CDF is deprecated. We recommend that you use the Calculated Field extension type of the session extension point.
See Calculated Field
CDFs, except the calculated ones and text fields, can be defined with multiple elements (arrays).