View node has the following properties:

Category Property  
General Properties Caption ViewImg02
Master Page
Use As Search Viewer
Form Theme Class
Generation Options Update Object
Web User Experience
Base Web Form

General Properties


Specifies the title that will be set to the View object's web page. If we want to set certain fixed value to it we must recover the value with the symbol '. For example: if we want to show Persons as the title of the form, we must set 'Persons'. 

Master Page:

Specifies the master page that will be assigned to the selection object. If we assign <default> means that this value will be taken from property View of node Master Pages of the WorkWithPlus setting. If we assign <none> means that the View will not have Master Page.

Use as search viewer:

Set the object View as Search Viewer for the associated transaction.

Form Theme Class:

Specifies the theme class that will have the form.


Specifies the type of View object that will generate. The options are 'view with tabs' and 'expanded view'. The first option will set each tab generated (Tabular an Grid tabs) into a tab, and the second option will set each tab in a panel each one at the bottom of its previous.

Type: 'view with tabs':


Type: 'expanded view':


It is important to mention that user can set if the panel of each tab will be collapsible and if it will be collapsed by default or not.

Properties Of Category Generation Options

Update Object:

Specifies the way in which the View object will be updated after re applying the pattern. The alternatives are:

  • Do not update:
    It won't update any of the view's elements (webForm, Events, Rules) when re applying the pattern. It is like the View object was no more linked to the pattern, unlike the other objects of the instance.
  • Create default: 
    Each time we apply the pattern, the form will be created and the Rules and Events updated according to the pattern instance. The user code and the content inside user tables will remain intact after re applying it.
  • Only events and rules:
    Each time we apply the pattern, the Rules and Events will be updated according to the pattern instance, but the View form will not be created from the instance, it will remain as it was before.
  • Overwrite:
    Each time we apply the pattern, the Rules, Events and the form will be overwritten. All the content inside user table and the user code will be cleaned.

Web User Experience:

Specifies the the web user experience of the View object. The options for this property are 'Use model property', 'Smooth' or 'Previous versions compatible'. When the property has the value 'Use model property', it will take its real value from the property 'Web User Experience' of the actual version of the KB:


Base Web Form:

Specifieswhether the base of the Web Form will be HTML or an Abstract Layout. Then, depending on the type of the tables inside the form, the Form may contain some HTML controls or Layout controls. The options of this property are: 'Use model property', 'Abstract layout' or 'HTML'. The value 'Use model property' will take its real value from the property 'Default Web Form Editor' of the actual version of the KB (Image above).

Example: Base Web Form 'Abstract Layout' with some HTML controls inside


Example: Base Web Form 'HTML' with some Layout controls inside


Actions on View node


Provides an example of how the View form will be generated, without the need of re applying the pattern or running our program to picture it. This preview does not include the tabs and its web components associated, but each tab has its own Preview action.

If you want to read more information about Preview action, follow this link: Preview