2. Entry Form Presentation

1. Introduction: Data Types

When entering or modifying data in the Silver Essence Portal, the type of field to enter or maintain the data is derived from the BaseEntity Property. Which type should be used is determined by the data type of the Property. By default, the following types are used.
  • String
    String values, or alphanumeric values can be entered through plain text-boxes. If a Property is of this data type, the following alternatives are available within the configuration:
    • Multi-line text-boxes:
      If multiple lines of text can be entered, a multi-line text-box can be specified. If the string has a maximum length (example: a Twitter post can go up to 140 characters) a counter is shown so the user knows how many remaining characters are left.
    • Rich Text Editors
      The Rich Text Editor is a multi-line text-box which has a toolbar that shows the options like bold, italic or underlined text. The Rich Text Editor generates HTML code, which is then stored upon saving.
    • Checkboxes
      In some cases, the string data type is used like a boolean, containing a true and false value, Most often these values will be True & False, but cases like Yes & No are also used. Properties that are of the string data type can be marked to be used as boolean. In that case, the true and false values must be set as well.
  • Integer
    Integers, or numbers can be entered trough plain text-boxes which only accept numerical values. In other words, text is not accepted for input. Integers cannot contain decimal points. The Integer data type has an alternative too:
    • Checkboxes
      In some cases, the integer data type is used like a boolean, containing a true and false value, Most often these values will be 1 & 0, but cases like 0 & -1 are also used. Properties that are of the integer data type can be marked to be used as boolean. In that case, the true and false values must be set as well.
  • Float
    Floats, or numbers can be entered trough plain text-boxes which only accept numerical values. In other words, text is not accepted for input. Contrary to Integers, Floats can contain decimal points. The number of decimals can be specified.
  • Booleans
    Booleans typically have 2 values only, true and false. To make them show up as checkboxes in the Silver Essence Portal, they must be marked to be treated as booleans, after which you can set the true and false value to be used. Since this cannot be determined from the data type, you need to specify these values manually.
  • DateTime
    DateTime fields contain both the date and the time. In the Silver Essence Portal they are shown as regular text-boxes in which the user can manually enter the date and time. A Calendar Icon is shown so the data can also be picked from a Calendar. A Clock icon is shown so the time can also be picked from a list. Do notice that in many cases the datetime data type is misused for fields that should show just the date. For example, the start date of a project. If that is the case and you want just the date, you can switch the data type to Date and the time will simply be ignored.
  • Date
    Date fields contain just the date. In the Silver Essence Portal they are shown as regular text-boxes in which the user can manually enter the date. A Calendar Icon is shown so the data can also be picked from a Calendar.
  • Time
    Time fields contain just the time. In the Silver Essence Portal they are shown as regular text-boxes in which the user can manually enter the time. A Clock icon is shown so the time can also be picked from a list.
  • GUID
    A GUID, or globally unique identifier, is a string that consists of 32 alphanumeric characters and 4 randomly placed dashes. Typically the GUID is used as the key identifiers for records in a database. Since GUID's are not really humanly readable, they are not displayed in the Silver Essence Portal. 
  • OledbImage
    The OledbImage is used for storing files into a database. OledbImages should be used in conjunction with a string property that will store the actual filename. This data type is not maintainable from the QuickEditor. You will find more information on how to configure these properties in the "Special Cases" section.
The DataType is considered in the following settings.

2. Input Type

Depending on the DataType, you can set the Input Type. Settings can only be applied to the following DataTypes:
  • Strings
    Strings can be shown as a regular Text Input, a MultiLine Text Box or a Rich Text Editor. The option to set the Input Type for strings is however not available if the Property should be shown as a CheckBox, or if a LookUp is specified for the input.
  • Date/Time
    Datetime Properties can be either shown as a Date, Time or Date/Time field.
Silver Editor: BaseEntity QuickEditor Input Type

2. CheckBox

Properties that are of the DataType Integer, Boolean, String or GUID can be specified to appear as CheckBoxes. Upon choosing this option, 2 additional settings for the True and False value need to be filled. By default, this will be 1 and 0 for integers, True and False for strings. Other DataTypes do not have a default value.

Once you have set this for a Property of the String DataType, you can no longer select the input type. If you want to change to a different input type, first uncheck the CheckBox option. This will also remove the True and False values.

Silver Editor: BaseEntity QuickEditor CheckBoxes

3. Required

If a Property must have a value, you can set the Property to be Required. This is possible for all DataTypes. In the Silver Essence Portal, there will be an Exclamation Mark shown to inform the user. Upon saving an entry, a check is done if the user did enter all the required fields.

If a Property is to be shown as a CheckBox, there is no need to set a Property to Required. In these cases, the True or False value will be used so empty values are not possible.

Silver Editor: BaseEntity QuickEditor Required