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:

Procedures can now call Web objects

Scope

Languages: Java, .NET
Objects: Procedures
Interface: Web

Introduction

As from GeneXus 9.0 procedures can now call web panels and web transactions.

Description

If the procedure has been called from a Web Panel or Web transaction or via HTTP (i.e. property Call Protocol is HTTP), it can also call or link to a HTTP URL (i.e. call a web panel or a web transaction).
Note that the call will not be executed sinchronously. It will be exectuted as a redirect to the called object at the end of the web execution.

Examples

pprc01:
call(hwbp01)
for each
 A=B
endfor
pproc02:
call(hwbp01)
..
call(hwbp02)
Event 'one'
pprc01.call()
EndEvent
Result: hwbp01 will be executed before the "endevent", after the for each
Event 'two'
pprc02.call()
EndEvent
Result: hwbp02 will be executed before the "endevent"
Event 'three'
pprc02.call
hwbp03.call()
EndEvent
Result: hwbp03 will be executed before the "endevent"

Why does it work that way? Internally, at each call statement  an internal variable is set with the object name to which, at the end of the execution in the server, the redirect goes.

Considerations

A procedure called via command line, for example, cannot call a web panel. But it could do an opendocument() function to open a URL in the browser.
Last update: April 2024 | © GeneXus. All rights reserved. GeneXus Powered by Globant