GeneXus 9.0 Upgrade Course
The following sections describe all the improvements made to the Development Environment in order to simplify the developer's life.
The following features are available for editing transaction structures:
While typing an attribute name, the editor automatically completes the name with the first existing attribute that matches the characters typed.
As many attributes may start with the same characters, you may use up and down arrows to scroll among them.
Attribute names usually start with transaction names. For example, in a Customer transaction you have attributes such as CustomerID, CustomerFirstName
and so on. If you type a '.' (period) as the first character of an attribute name, it will be replaced with the transaction name. In the previous example, typing ".FirstName" is equivalent to typing ''CustomerFirstName".
Usually, you realize that you need a Domain when defining an attribute's data type. Selecting Advanced/Domain/etc. to create a new Domain may be somehow annoying, so you can avoid it by typing <DomainName>=<DataTypeDefinition>
in the Type column. The Domain will be automatically defined. For example, Description=VarChar(40)
defines a Description domain with the specified data type.
There is no need to move to the Formula column to type a formula expression. For example, typing InvoiceLineTotal=InvoiceQuantity*ProductPrice
in the attribute definition column is enough.
Use Alt Enter
to go to the definition of the selected attribute.
When searching with the attribute selector, the Pattern
in the Selection Criteria section
applies to the attribute name and now to it's description too.
A new option has been added when defining a Subtype group
based on a transaction structure.
Based on a new heuristic, the insertion automatically defines the subtypes based on the selected attributes. To use it
1. Define a new Subtype Group
2. Select Create subtype for...
from the contextual menu.
3. Select the desired transaction.
4. For each attribute in the selected transaction structure, a new subtype definition is done taking into account the following:
- The subtype is named based on the supertype name using the subtype group name as a prefix.
- If the supertype attribute name starts with the name of the selected transaction, this prefix is changed for the subtype group when defining the subtype.
The Following example creates a Customer Subtype Group
based on the Person transaction structure
Based on PersonId
, the following attributes are created: CustomerId
; in this case the prefix has been automatically replaced. For CityId
; the subtypes added the prefix Customer
to obtain CustomerCityId
When inserting attributes or a transaction structure, SDT Items are automatically based on them, minimizing the time spent in their definition.
New Contextual Menu options have been added:
Text blocks are edited
- Define... enables you to define a variable while coding.
- Define Based On is shown when a variable ends with a Domain name or matches an attribute.
- Edit. for existing variables.
through a new properties option.
The model bar toolbar now has more language options to edit help text. For more information, click here
- Deleting a list of objects has never been so easy.
- If a tooltip is lost (for example, after inserting an attribute), you can retrieve it by pressing ','. You can use the left and right arrows to navigate through it. For more information, click here
- Regarding the new syntax call if the called object has more than one parm rule, the tooltip in the caller object is shown as follows (you can select the desired one with the up/down arrow):
- The tooltip is activated to whatever function, rule or command where the first parameter is an object. It displays information of Business Components Extended and User data types.
- SAC# 17419 : Environment attributes (WINDOWS, WEB) in subroutines and event.
- SAC# 16925 : Recent KB history showed KB of different versions.
For detailed information about the Development Environment, click here