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

Description Attribute property

Official Content
This documentation is valid for:

The Description Attribute is the attribute that best describes (or represents) a Transaction object. For example, in the Customer Transaction, CustomerName is usually the Description Attribute.

In web applications, the Description Attribute usually has a link to the View Web Panel.

A good description attribute must follow these properties:

  • Uniqueness. An attribute can be Description Attribute of only one Transaction.
  • Just one attribute. A Primary Key can be composed of many attributes, but a Description Attribute must be just one attribute.
  • Meaningful for users. E.g. CustomerName is better than CustomerId.
  • Not ubiquitous. Not all transactions have a Description Attribute.

Because of these properties, a Description Attribute is usually a Candidate Key.


  • There can be a Description Attribute per level.
  • Not all Transactions (or levels) must have a Description Attribute.


Objects Transaction object