Noca | Changing Element Types in Applications Noca | Making Word Tables in Documents Smarter with Conditional Logic

Changing Element Types in Applications

Designing forms and interfaces often involves choosing the right type of element—such as text inputs, checkboxes, or selection controls. But in many cases, requirements evolve, and the structure of an interface needs to change over time.

Instead of rebuilding elements from scratch, it is now possible to change an element’s type while preserving the overall structure of the interface.

Adapting Elements Without Rebuilding

Rather than deleting and recreating components, an existing element can be transformed into a different type.

For example, a text input can be converted into a selection-based control. This makes it easier to adjust interfaces as needs change, without disrupting the rest of the design.

Supporting More Flexible Selection Inputs

When working with multi-select elements, additional flexibility is available for defining available options.

These options can be:

  • Defined manually as static values
  • Retrieved dynamically from a workflow or data source

This allows selection fields to adapt based on context, data, or external logic.

Why This Matters

This flexibility simplifies interface design and maintenance:

  • Faster adjustments to existing forms and screens
  • Less need to rebuild components from scratch
  • More dynamic and data-driven selection options
  • Easier experimentation with different UI patterns

More Adaptive Interface Design

By allowing elements to change type instead of being recreated, interfaces become more adaptable and easier to maintain. This supports a more iterative approach to building applications, where changes can be made quickly and efficiently as requirements evolve.

Back to top