Development Environment

Web Development and Improvements in user experience

(Productivity and Enterprise-level Application Development Features)

Ajax Overview, [[21759|GeneXus'>Ajax'>Ajax Overview, [[21759|GeneXus and Ajax]]

Business Components

Business Component - Publication as an Enterprise Java Bean

Practical course: Bluesky Charters

Application Localization

Application Localization
Translation Tool
Help "in any language"
Practical course: Bluesky Charters


About this topic
Patterns based development
Built in Patterns
Work With Pattern
Demo: Work With Pattern
Practical course: Patterns

Better data model

Null handling optimizes navigations
Nulls property


User experience

New options on rightclick in win

Reverse Engineering

Database Reverse Engineering Tool

New Platforms

.Net Mobile Generator
More J2EE support than ever

Data Types and Methods

Message Queue handling data types

LDAP Data Type

URL access Property
New IIF function
New byte count function
New Methods for attributes, variables and enumerated domains!
XSLTApply Method
Procedures can now call web objects
Web Services: Grouping Locations
News about model, object, and control properties

Insertion of a Business Component variable in a Layout

Official Content
This documentation is valid for:

It is possible to insert a Business Component variable in a Layout by selecting the Insert > Variable option from the GeneXus main menu or by dragging the control from the Toolbox.

The following dialog appears and you can clear the properties that you don't want to show in the Layout:


If the Business Component variable has nested levels (as the previous image shows), they will be inserted in grids. For example, if the &Invoice Business Component variable is inserted in a Web Panel Layout, it looks as follows:


As the variables in Web Panels are editable by default, all the &Invoice properties are editable as well.

Now, suppose you want to allow the user to enter an invoice ID value, and load all the invoice data by pressing a button. The following implementation solves this scenario: 


Event 'Get'