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


Unofficial Content
GeneXus 9.0 Upgrade Course

Noaccept in Multiple Attributes


Languages: All
Objects: Transactions, Work Panels, Web Panels
Interfaces: Win, Web


Sometimes you need to specify several NoAccept rules without any conditions, and several NoAccept rules with the same conditional expression. Now on, this can be done in a unique NoAccept rule for multiple attributes/variables.


Until GeneXus 8.0, to specify a NoAccept rule for several attributes and variables you had to write down a rule for each one where the NoAccept rule applied.
If the NoAccept rules were conditional, you also had to write the condition several times. As a result, the rule space of the objects was unnecessarily filled with redundant information.
Now on, the NoAccept rule allows to specify a list of attributes or variables.

The syntax is as follows:

Noaccept( {att1|&var1}, ... , {atti|&vari} ) if cond ;

atti, &vari: attributes (in Transactions) or variables (in Work and Web panels) that won't be accepted if the condition cond is satisfied.


Consider the following rules that were written as follows in previous versions:

NOACCEPT(PrdDsc); // Unconditional NOACCEPT

NOACCEPT(CreditLimit) if CustomerCat = 1; // Conditional NOACCEPT
NOACCEPT(CreditBalance) if CustomerCat = 1;

The same rules can now be written in only two lines as shown below:
NOACCEPT(PrdDsc, PrdCat); // Unconditional NOACCEPT
NOACCEPT(CreditLimit, CreditBalance) if CustomerCat = 1; // Conditional NOACCEPT

Comments & Collaboration

Interesting links

NoAccept Rule in GeneXus 8.0 Help System