In the same way, a repeating table can be bound to a custom field group in a case, repeating tables can also be bound to the field group that is created by a data table.
Data tables differ from case groups in one way. A case group can use the controls in the repeating table to add and remove records. Data tables, on the other hand, require that web methods or SQL queries exist to handle these functions, and update the data source.
In the example below, the form from the previous section is developed further to display a list of employees. There are no add or remove methods in the web service, so the values will be displayed in a read-only format.
First, a repeating table with a column for each output is created, and bound to the data table group.
Next, labels are dragged into the repeating row of the table to display the data table’s outputs. When the label is dropped into the repeating row of the table, the field binding dialog will appear, with a list of the data table’s outputs.
The first_name field is bound to a label in the first column of the table. Then the last_name field is bound to a label in the second column, and id is bound to a label in the third.
Next, text controls are added to the header row. The Repeating Table’s Allow Insert and Allow Delete properties are set to No, because the web service does not have methods for these:
The last step in UI Designer is to decide when you want the data table to refresh. This web service returns the same results every time, so it only needs to refresh once, when the form is first loaded. Click Fields on the left navigation bar to go to the Fields panel, and click the Form name to open the Rule panel for the form. Add an action rule, and add a statement to Refresh Data Table. If the form implemented a way to add/remove employees, the data table would also need to be refreshed when this happens:
The employees from the data table are now displayed in the case folder:
