Table of contents


Development Environment

Web Development and Improvements in user experience

(Productivity and Enterprise-level Application Development Features)

Ajax Overview, [[21759|GeneXus' target='_blank'>Ajax' target='_blank'>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

Official Content

The Description attribute is the attribute that has the greatest semantic meaning in a Transaction object.

In other words, it is the attribute that best describes (or represents) the Transaction.

By default, the first attribute in the Transaction structure with a character data type is defined as Description attribute.

The icon with a magnifying glass stands for the Description attribute:


For example, in the Category Transaction, the CategoryName attribute is the Description attribute.

You can define a different attribute as the Description one using the corresponding pop-up menu, or define no Description attribute at all.

 A good Description attribute must follow these properties:

  • Uniqueness. An attribute can be the 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. For example, 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.

The Description attribute is automatically considered and used when GeneXus generates applications. For example, when applying the Work With Patterns to Transaction objects, the Web Panel objects and Panel objects that are automatically generated show the Description attributes with a link that opens a layout that displays more information related to the record involved. 


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

Last update: April 2024 | © GeneXus. All rights reserved. GeneXus Powered by Globant