3 Form field event binding, user-defined rendering
1 Field value change trigger event
Field value change will trigger the bound function, can be bound multiple times BindFieldChangeEvent:function (fieldMarkStr, funobj)
Parameter Description
2 Detail table field values trigger event
Binding for newly added detail line fields and loaded fine line fields, and value changes trigger bound event bindDetailFieldChangeEvent:function (fieldMarkStr, funobj)
Parameter Description
3 Field area binding action event
Recommend to use this method to develop, because this interface click, double-click and other actions are not bound to the field element, the interface bound to the cell All functions can be implemented in a formula
bindFieldAction:function (type, fieldids, fn)
Parameter Description
Example
4 User-defined proxy single-line textbox field rendering
Minimum version requirements :KB900190407
this interface is effective only for single-line text-box field types, Database field type is varchar
Display effect, events, field value could be controlled by each other, The editable field values modified through interface 3.3 will also be recorded.
System will pass in relevant props, React Developer Tools could used to grab data, Call on demand
proxyFieldComp:function (fieldMark, el, range)
Parameter Description
Example
5 User-defined Additional Render Form Field
Minimum Version Requirements : KB900190407
Add addtional user-defined rendering for after Method Based on Standard Fields Display Content
This interface parameter description and usage is similar to interface 4.4
afterFieldComp:function (field Mark, el, range)
Example
6 User-defined form rendering with functions
Minimum version: KB900190701
Customize render form fields with function return values, support all field types, implement add/override/relayout based on original components, etc.
It is recommended to combine ecode together, to call before module loading, use JSX, to customization
This interface related to form field rendering with a higher priority than 4.4,4.5, that is, fields using this interface proxy, such as 4.4,4.5 will be invalid immediately
proxyFieldContentComp:function (fieldid, FN)
Inteface Parameter Description
Function Parameters of Proxy
Example
7 Get field component by field id
Minimum Version: KB900190701
Get the field component according to the field identification, that is, the field component can be extracted separately and rendered anywhere. Note that the read-only editable properties of the field still need to be set up in the background in advance
It is recommended to work with the ecode, using the JSX, and then combined with the designer custom properties or interface 4.6, can achieve a certain area custom typesetting layout rendering multiple form field
generateFieldContentComp:function(fieldMark)
Interface Parameters Description
Example
Last updated