List & Table Control

list control the list control is a versatile component designed to showcase a collection of items within a form it empowers users to effortlessly navigate through structured data while offering extensive customization options 1\ display of items visually presents items in a vertically stacked list format supports multiple controls within each item option to add multiple fields for enhanced data representation placeholder state when no controls are present at design time renders all items from the data source at design time for multiple controls in an item there will be a toggle “add multiple fields” under the data “source value” which must be on also the “source value” for multiple fields is expected to be an array of objects each item in the list can consist of field controls, list control, or a combination thereof if no control is dragged in the item list at design time, there will be an empty placeholder state, with different messages according to the value of “add multiple fields“ all items in the data “source value” will be rendered at design time if source is empty there will be by default one item rendered if you have a list control and inside it, there is another control that is empty, if you check the +add option, in view mode, you will be able to click on the button in the picture to add the control if no control is dragged in the item list at run time the control will not be shown 2\ data source connects to a json or url data source dynamically updates content based on changes to the underlying data configurable options for modifying the data source for a list with a single control inside the iterator container, “add multiple fields” is expected to be off and the data “source value“ to be a list of primitives for example \ \[“first entry“, “second entry”] \ or \[1, 2, 3] \ or \[“first entry”, 2, "3", false ] for a list with multiple controls inside the iterator container, “add multiple fields” is expected to be on and the data “source value“ to be an array of objects for example \[ { "id" 1, "name" "john doe", "address" "123 main st" }, { "id" 2, "name" "jane doe", "address" "456 elm st" } ] data “source value” must be available in the control variable 3\ data binding enables seamless synchronization between controls and data source automatic binding for lists of primitives when "add multiple fields" is off manual binding by naming controls to match keys in the data source recursive binding for nested lists the list controls binds to the data source, dynamically updating its content based on changes to the underlying data this ensures that the list remains synchronize with the latest information from the data source each control dragged inside an iterator container can be bound to an item or a key of an item inside the data “source value” as stated above, if the data source changes the ui value/text of the control should update as well for field controls dragged inside the iterator container, if the user inputs new data or edits existing one the data “source value” should update as well if the data “source value” is a list of primitives and “add multiple fields” is off, the control dragged inside will be bound automatically to the list item if the data “source value” is a list of objects and “add multiple fields” is on, the binding is done manually by the designer by naming the control the same as one of the keys inside the list item for example in the following image the iterator container contains a number field and two text fields and data source has two items, each with 3 keys/properties none of the controls are bound to the data source because they have the default names (numberinput1) in order to bind the number input to the “id” key we have to name it “id” as soon as we name the control to one of the keys of the data source it synchronizes with it you can do this recursively as many times as you want by dragging a list structure control inside the iterator container and bind it to a property which is also a list just like the parent list it can bind to a list of primitives or a list of objects data “source value” will remain empty for list controls of type children if used as described above data binding is available for field controls and list 5\ customization and interaction allows customization of item layout, styling, and themes supports interaction through various actions like clicking, dragging, or tapping integration with other controls for comprehensive form design customize item layout, styling, and themes to align with design preferences interact with items through various actions at run time properties bar general customize properties such as label, tooltip, and visibility name & id assign unique identifiers for easy reference data source specify the type of data source (json or url) configure source value and options for multiple fields min & max define minimum and maximum element limits for data source modification can add & can remove enable/disable options for adding and removing items from the list add text label & add label customize labels for add buttons and item labels with the list control's robust features and intuitive interface, managing and presenting data within your forms becomes seamless and efficient table control work in progress overview the table control allows you to visually represent tabular data within your forms it provides a grid like structure where you can view and interact with rows of data data table the primary wrapper of the table control can be dragged anywhere in the form designer by default, populated with an instance of "dynamic table rows" and two instances of "table row" can have children such as "dynamic table rows" and "table row" static table row a static row draggable only inside a table control by default, contains as many columns/table data/cells as defined on the data table, each with a grey empty rectangle you can add any fields or structure controls in a table data/cell, except for the approval control dynamic table rows combines features of "table row" and "list" control maps the iterator container over a data source, allowing dynamic population of rows can be nested within other rows or added directly to the data table header support headers can be configured on all table controls headers can be defined sections for the table to display additional information such as column titles interaction features pagination navigate through multiple pages of data if the table exceeds a certain number of rows per page summary functions perform calculations on columns like sum, average, count, etc , to derive meaningful insights from your data sorting arrange rows based on column values in ascending or descending order for easier data analysis filtering apply filters to columns to display only the relevant data based on specified criteria adding and editing data easily add new rows to the table or edit existing data directly within the table cells multiple items action perform bulk actions on selected rows, such as delete, edit, or export data binding and data source data binding within the table control establishes a connection between the table structure and the underlying data source this ensures that changes made to the data reflect in the table display and vice versa the data source defines the information to be displayed in the table control it can be static data entered directly into the form builder or dynamic data retrieved from external sources such as apis or procesio processes the data source is defined within the "dynamic table rows" control it can be a url returning json data, a json, or a static list generated based on the column definition the data table above has a “dynamic table rows” control the iterator container has a “dynamic table rows” as a child table control the expected data source for the first “dynamic table rows” is { "columntitle" "value", "startedon" "value", "lastupdate" "", "submittedby" "", "children" \[ { "columntitle" "value child", "startedon" "value child", "lastupdate" "", "submittedby" "" } ] } each object represents a row in the table the keys represent the columns, and the values represent the data in each cell nested objects under the "children" key represent additional rows within a row, forming a hierarchical structure 3\ data binding process automatic binding if the value associated with a table row cell is a primitive data type (text, number, boolean, file), data binding is automatically established with the cell if a table row cell has only one child control, the value binds automatically to that control multiple controls in a cell if multiple controls are desired in a cell, the value associated with that table row cell should be an object/json/data model/list each control in the cell should be named the same as the keys in the object to which it binds primitive value binding to keep the value associated with a table row cell as a primitive data type but bind it to one of the controls, the control should be named the same as the "keyname" defined in the "define column" property 4\ approvals integration if the "approvals" section is populated, a new key called "approvals" will be added to the row's value, containing an array of booleans corresponding to custom approval controls added as columns in the table 5\ customization the data source structure can be customized based on the specific requirements of your application and the layout of your table assignee & approvals specify assignees and approvers for columns and rows using dropdown controls with header values customize approval controls and assign them automatically to columns in the table design and placement flexibly manage columns within the table by dragging and dropping "static table row" and "dynamic table row" controls arrange controls directly into the data table or between rows, inside cells (nested table control), or at the bottom of rows (child table control)