In Web Experience Factory (WEF), all data display and input forms are built using what we call the “Page Automation” framework of WEF. There are four primary builders that are used to construct UI using the Page Automation framework. These are:

• Data Page
• View & Form
• Input Form
• Data Services User Interface (DSUI)

Given the multiple builders that are available for creating your data displays and forms, we are often asked which builder to choose. This article outlines the considerations for selecting among these builders.

First, let me say that all of these builders are good choices. With any of them, you get a whole set of benefits that come with using the Page Automation framework. Here are some of the key features you get with any of the four builders:

• Automatically generate pages based on the data schema, including all the code for mapping data fields to UI. Both data display and input forms are supported, including server-side validation
• Easy, automated, control of all the rich behavior of all your data fields. Using Data Field Settings, for example, you get easy centralized control over formatting, validation, UI controls including Dojo, visibility, labels, lookup tables, and more.
• Complete control and customizability of UI design and layout. There are a number of ways to handle UI design and layout that can be used with any of the four Page Automation builders: (1) you can use an automated layout, where schema fields are laid out for you (this is the default); (2) you can customize an automated layout using graphical tools in Design view or by using “modification builders” such as Data Heirarchy Modifier or Data Column Modifier; (3) for repeating data, you can use the Data Layout builder for a wide variety of nice-looking layouts; and (4) you can use custom HTML designs, perhaps coming from a design team.
• Easy centralized control of look and feel using WEF UI Themes. Themes let you control CSS styles, layout rules for page fields (HTML templates), data table behavior such as row highlighting, data paging style, and more.
• Support for mobile and multi-channel rendering. You can use WEF mobile-related features such as Data Layout builder, mobile UI themes, and device type profiling with any of these Page Automation builders.

For deciding which builder to use, we'd suggest first keeping in mind this general best practice guideline for WEF builders: Use the highest-level builder suitable for the job.

That guideline will help you get the most benefit from WEF's builder automation. For example, a in model that displays service results, using the lower-level Data Page instead of View & Form means that you'll need at least three builders instead of one, and you'll need to correctly configure quite a few more builder inputs.

However, the decision is not always simple. For example, you might find that in some situations, using Data Page makes it easier to implement customizations that are difficult with the View & Form builder, when you want something different than what View & Form generates by default. And DSUI is the most automated builder (complete CRUD with a single builder!), but also the most rigid in terms of the patterns it generates. So there is some trade-off between automation and flexibility.

Here is a table that compares different characteristics of these four Page Automation builders. The general ordering is from lower-level (Data Page) to high-level (DSUI). Data Page is the core Page Automation builder, and the other three builders all use Data Page under the covers. Note that this is a high-level summary of key functionality for these builders; there are many other detailed features and differences not mentioned here.

Builder	Description	UI patterns supported	Key automation provided	Data Service dependencies
Data Page	Adds XML data to an existing page, for display or input.	Patterns: Any structured data display or input on any existing page	Generates code that maps data fields to UI and and saves submitted data	None - can work with an XML variable or with any Data Service input or result parameters.
View & Form	Generates fully-functional pages and navigation for viewing data from a Data Service, with optional input, details, and update pages.	Patterns: View page for service operation results (repeating data or single-record) Input, Details, and Update pages (optional)	Imports the base pages where data is placed. Uses Data Page for all data views and forms. Adds navigation buttons and links. Generates methods that call services before displaying result pages. Optionally generates “main” method.	Can be used with any Data Service operation that returns results. Typically used with operations from the Service Consumer builder. Can also be used with a Variable.
Input Form	Generates an input form for a Data Service operation that doesn't return results to display.	Patterns: Input page for service operation with no results	Similar to View & Form builder, but just for an input page.	Similar to View & Form builder, but just for an input page
Data Service User Interface (DSUI)	Generates a fully-functional CRUD (create, read, update, delete) application from a Data Service that has logical operation information defined. Generates all UI and navigation.	Patterns: Complete or partial CRUD application List page with optional Filter form Search inputs and results pages (optional) Details, Update, and Create pages (optional) Separate List and Details portlets that use events to communicate	Imports the base pages where data is placed. Uses Data Page for all data views and forms. Adds navigation buttons and links. Generates methods that call services for all CRUD operations. Generates optional eventing support, using portlet wiring or client-side events. Optionally generates “main” method.	Requires “logical operation” information for Data Services, to identify the role of each operation and any key fields. Logical operations can be defined in the Service Definition builder. Typically used with a Data Service from the Service Consumer builder.