Table of contents

Introduction

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
Demo
Translation Tool
Help "in any language"
Practical course: Bluesky Charters
 

Patterns

About this topic
Patterns based development
Description
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

MySQL
.Net Mobile Generator
More J2EE support than ever
 

Data Types and Methods

Message Queue handling data types

DirectoryDataType
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


Unofficial Content
  • This documentation is valid for:

GeneXus 9.0 Upgrade Course

Introduction

As of GeneXus 9.0 you can name the levels of a transaction's structure. GeneXus then takes this information to name Business Component - Publication as an Enterprise Java Bean and tables. In addition, Patterns uses it to improve user experience and GXquery uses it to better group attributes and also improve user experience.

Description

All levels but the first can have user-defined names (*). Each level has a Name, Type, and Description.
The Type is used to name Business Component - Publication as an Enterprise Java Bean and the Description is used by Patterns (GX 9.0) to name tab dialogs and views.
To name the associated table, GeneXus concatenates the names of the levels up to the first one (in the example, the Lines table default name would be "InvoiceLines"). The description of the table is the description of the corresponding level.

(*)Note that the first level is named by GeneXus , as it is the transaction's name.

Example

Invoice transaction and associated Business Component - Publication as an Enterprise Java Bean

 

 

 

 

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