Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
protogrid:field [2020-07-06 11:07] – * jusprotogrid:field [2021-12-21 22:49] (current) dru
Line 4: Line 4:
  
 There are different types of fields: There are different types of fields:
-  * Text  +  * Text 
-  * Number +  * Rich Text 
 +  * Number
   * Tableview   * Tableview
   * Date & time   * Date & time
Line 15: Line 16:
     * Editable: always editable to the user     * Editable: always editable to the user
     * Editable before first save     * Editable before first save
-    * Computed by a [[scriptlibrary]] +    * Computed by a [[protogrid:Script_Library#Server ScriptLibrary]] 
-    * Computed by a [[scriptlibrary:Client-ScriptLibrary]]+    * Computed by a [[protogrid:Script_Library#Client ScriptLibrary]]
     * Hidden: Values might exist in the backend, but are not rendered for the user     * Hidden: Values might exist in the backend, but are not rendered for the user
     * Hidden in client: The field is rendered hidden in the browser. Note that this is a feature for eased user access and not a security feature.     * Hidden in client: The field is rendered hidden in the browser. Note that this is a feature for eased user access and not a security feature.
Line 23: Line 24:
   * Min-Max-Validation (for Numbers and Date & times): You may require that the value of this field is no smaller or bigger than a given value. This will be validated upon saving.   * Min-Max-Validation (for Numbers and Date & times): You may require that the value of this field is no smaller or bigger than a given value. This will be validated upon saving.
   * Regular-Expression-Validation (for Text): You may require the text to match a certain structure given by a regular expression in the field definition. This will be validated upon saving. Examples of regex strings are given below   * Regular-Expression-Validation (for Text): You may require the text to match a certain structure given by a regular expression in the field definition. This will be validated upon saving. Examples of regex strings are given below
-    * Mail: The regex string <code>.*@.*\..*</code> matches input of the form [a-z0-9]@[a-z0-9].[a-z0-9] +    * Mail: The regex string ''.*@.*\..*'' matches input of the form [a-z0-9]@[a-z0-9].[a-z0-9] 
-    * Phone: The regex string {{code|^(\+?)(\d{2,4})(\s?)(\-?)((\(0\))?)(\s?)(\d{2})(\s?)(\-?)(\d{3})(\s?)(\-?)(\d{2})(\s?)(\-?)(\d{2})}} matches Swiss phone number entered in international format and the most common styling rules. It matches +41 44 123 12 34, +41 (0) 44 123 12 34, +41-44-123-1234, 0041 44 123 12 34. It does not match 044 123 12 34, +41 0 44 123 1234, +41.44.123.1234.+    * Phone: The regex string ''%%^(\+?)(\d{2,4})(\s?)(\-?)((\(0\))?)(\s?)(\d{2})(\s?)(\-?)(\d{3})(\s?)(\-?)(\d{2})(\s?)(\-?)(\d{2})%%'' matches Swiss phone number entered in international format and the most common styling rules. It matches +41 44 123 12 34, +41 (0) 44 123 12 34, +41-44-123-1234, 0041 44 123 12 34. It does not match 044 123 12 34, +41 0 44 123 1234, +41.44.123.1234.
  
 Note that whether or not a field is editable to a certain user also depends on the users role in the [[Environment]]. Note that whether or not a field is editable to a certain user also depends on the users role in the [[Environment]].
Print/export