Interface ivaA_number

type of the element in the UIdateEl - internal, never loaded

internal represetnation of the disabled field

readonly status calculated from readonly (Note: not calculated for list views, only for detail)

visibility status calculated from visible - use ths value to hide or show columns

action that is started by click or self-defined view command

• When used together with the field in the list, system creates a button that activates operation
• When used in the detail with the item of the view type, it is used instead of view defition in view. Here can be used any a... command.
  • Link can freely defined and even evaluated by fval. When evaluated by fval, it allow total control over the attributes, but it does not get default attributes!
  • @example: object linked if the tskReminder
  • It can manage readonly settings and e.g. allow to have view item editable even when master object is readonly
  • @example: tskRelTaskUser linked in tskTask

Optional mark requesting to send value of the field always to the serer When value s marked true, update always send value to the server - in the group field if modified and in the group attrParam when not modified Use when value is necessary for preUpdate/postUpdate function

Optional name of the block. Use block to get more small items to single line User blockStyle to set the style of the block

Style applied to the block blockStyle is always applied only with the first attribute. When block is created the style from next placed block is never applied

string or number of box in which the attribute is placed DEPRECIATED: Do not use box but split attribute to the box definitinos

Default value for field when object is new. Equal with dataAttribute.default Use only in case that there is more views and default value is different for them User false value of fields to disable using default value

command evaluated in order to check if user can edit field. Negation of the readonly. Has lower priority and is disregarded in case that readonly is defined. Do not use both of them

Optional attributes says that attributes should be totally ignored and view behaves as as attribute doesn't exists Use when extneding object should ignore some attributes from parent object WARNING: Curently implemented only for listView, detail does not yet supported it

Optional name of enum Uses id dataAttribute is not defined or view uses different enum

Optional name of the condition use to select part of the filter if contains = it is expected to be condition usef to evaluate - see enumLimit description at data attribute

Optional enum type used in case that field is not from object (no dataAttr)

Iptional evaluation string - field can be evaluated before it is placed to the field; Should contain string evaluated with fields from row; supported by list and detail - for detail it make sense with readonly:true or some other type of content ocntrol

user settings to hide the column - used only for list view - user can change this value and value is stored in the browser memory

Optinonal commands about label false - no label is printed string - string to translate (used instead of fieldname) true - does not affects functionality (useless) evaluaated - (=obj.enumVal('x')) --- should return translated value, result is not translated. Remember that obj is empty (nevertheless defined) for new object

Optinal attributes mark fields that are not from database and could not be saved. Use that for fields that are modified on the client application but shall not be saved because they are not from object table and save is made in som other way

• Let's note that it is only rarely necessary, because strange items are mostly not updated and so never goes to the save
• Field is not evaluated! use true for strange field that makes trouble during saving

Name of the object operation started when user leaves the item

• use enabled attributes of the operation to check if operaion should be started or not. evaluation of the enabled string gets actual state of the object Enabled field is evalauted everytime when user leaves the item

Name of the operation linked with the attribute; used in the list (or lately also detail view attributes) Not supported in detail. User buttons:[] in detail Allowed content is:

• name of the operation defined in object (e.g. tunEtwas), (for detail not yet implemented)
• openSelfDetail, openSelfClip, openSelfModalDetail - only list
• form.object.viewtype....., other operation except form are not allowed - only list

Optional order string used to order attributes

optional placeholder text in the field Always translated, not evaluated

Visible but not editable - used in the json defition file and converted to the _readonly according to the data. Do not use it with the data processing in the view

When true, field is considered to be required reqardless on the data attribute settings

The same as visible

When true it says the input is for short - up to 5 digits and field could be also short Makes sense only for text-like fields like string and number and listbox

Optional shortcut

Optional attribute source

Optional eval values used for strange object; eval is never used for strange Used only in list table

optional style for element See style option for boxElements for more details about the field

__Warning: supported currently only for view, image and some text fields;

• Explicitly not supported for any object/file picker and event not for markdown editor

Optional view type that describes, how to present value

optional atribute that allows specify clip to open. @example: oper:"form.sysUser" view:"sysUser.clip." @example: "view":"form.tskDefUserTask.detail.default(readonly:viewDef=true,location=modalSecond)"

system setting, that the row is necessary but not visible to allow e.g. keys for detail open - user cannot change this value; do not use the value, but use _visible instead of that

Optional field allows limits when field is visible. Don't set the value in default state when field shall be visible both in read and write mode