Interface ivA_clip

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

internal represetnation of the disabled field

Mark that list loaded values

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

Div element created in the header div for calculation results

Optional list of operations that table calculated from values Calculations are always made by client application from loaded data

Result of the calculations made from the calcOpers Created by fhTable

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 attribute allow define, how enum values are presented in table

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

Optinal rule how to apply the string filter selected on the field, user

Filter

tag where to put the users's filter. Tag can be used serveral times Makes sense only for list attributes where are fillter available for columen Intended for filters from remote tables, e.g. user name

Example

(artifical) userID field has filterPattern: "userID in (select sysUserID from @sysdb.syswUser where userDesc like '%@filter%')"
Let's note that user link has direct support in the framework and directly supported by the system

when filter = false, field is not allowed for filtering and neither sor nor filter items will not be shown in the menu (only hide column), note: menu=false to hide menu completely

Filter should also support not variant using the pattern @not<space>:
 * When user use ! mark at the begging of line @not<space> is replaced by not<space>
 * When user not the mark, @not<space> is replaced from string
Copy

Link to the attr header item Created by htable

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

icon used as an alternative to the name in the header If defined field has as a label icon, but translated name is used in the menu of hidden columns

Icon defined in the column is visble once in the table header

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

option disables field menu item - if set to true, fields has no menu in the table event when other columns have

Optional name of the icon used in the list of hidden table fields. Use only name, value is not evaluated

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

The same as visible

Optional icon visible before text or instead of text in the field

Icon defined in this field si visible in each line - depending on evaluation of the icon definion

name of the alternative SQL select comand that is for list used in case that view with clip is loaded When used there must be defined attribute in the view serverData part that defines the alternative view and adiitonal WHERE condition DON'T FORGET that all standard WHERE conditions and filters should be usable also with the alternative view Alternative view is not combines with the field selection and all fields (*) are selected and sent to the client

Example

tskTask list contains definition for clip with user flags and stars
Copy

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

string to send server, when sorted by this column, use when field is calculated from other fields; if false, sorting is not allowed; usage example: sysErrorMessage

Definition of optional sorters and filters available on the column header if the field where is filled in the sorter, it operates as a filter, other wise it is a sorted If nothing is filled in the sorter, table is sorted by the field name with the name of the sorter - aka sorter should be named as a single table column

Optional attribute source

Optional sql string user to get field from database. Field definiton is evaluated by server and thus can contain

Self User ID

Client checks for field and remind serer that the sql section is defined, but server loads it internally; sql code is not accepted from client

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

Optional mark for field that contains ID of the strange object always invisible regardless if it mark as visible or not, visible only for developer in the debug mode invariant: strangeID == undefined <=> object is native

Optional Mark for column where is hierarchy of the strange object

Optional mark for field with the strange ID object can be filled even for strange object if those are hierarchical (products in the asset table, section in the list of web pages) always invisible regardless if it mark as visible or not, visible only for developer in the debug mode

styles for list-view cells

When true and list is the tree view, the field is indented for child objects Value supported only for string values (name), other types disregards value

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