Since eCASE uses a “Data First Approach” to build case applications, the data model must be well defined before using the UI Designer to create any form.
The UI Designer will load out of the box (core) fields, custom case fields, field groups, case actions, choice list relations, application roles and Web Services when selecting Form Type on the UI Designer’s Welcome Page. Case fields are either single value fields or multi valued fields defined as part of a field group. Multi-valued case fields can only be bound with repeating table fields, and single valued case fields can only be bound with single value fields in the form. Fields in the form that are not bound to any case field are treated as unbound fields. Values of unbound fields are not preserved with form reload operations.