search results

(...) s in reports and datagrids had been changed. "Standardized functionality of Calculated column of the Link type. From now on, formatting that encompasses "on click" will function solely for Report form fields . For instance: link:www.google.com;displayname:GOOGLE;onclick:javascript:action This type of formatting does not function for Data table form fields and instead "JavaScript" formatting should be util (...)

Hi, Current Situation: Data Sources are typically static and context-independent. Each Data Source is bound to a fixed query or API call, with no native mechanism to pass parameters dynamically. As a result, any variation in use (such as retrieving different columns, filtering by different criteria, or adapting to different workflow contexts) requires creating multiple Data Sources or embeddin

E.g. specifically when updating items lists on forms ! pageload vs on path vs on entry vs on exit ! What is the specific order on how things trigger? Is there another documentation other than the official docs? The docs dont tell me that much about such details for example Following example We have an id and that id can be referenced in 3 other fields! Those ids are saved in a db. The fi

(...) Hi, form fields in the Objects tab of the form rule editor don’t get displayed in standard mode. Only when switching to JS mode the form fields appear. In the form rule editor of a Validate form action the form fields appear in the Objects tab. More details here in the conversation with Jacek: https://community.webcon.com/forum/thread/8410 It would be more consistent and convenient if form field (...)

(...) the form. Now I expected to get all columns shown under "Columns collection" in the "Values" tab. But there is no entry for it. After searching a while I found the entry of this item list A under "form fields " as the only item list. Why don't you just keep the same logic as it is for the collection types "any collection" and "data source" where the "Colums collection" gets displayed? This would be more (...)

(...) ction in the form field editor doesn’t accept form field groups. It would be much more convenient if a whole group could also be disabled (readonly) and enabled instead of having to handle all child form fields . Kind regards Sébastien