BlueSkyPart2

Unofficial Content

Practical Course: BlueSky Charters


Following with the Part 1 (Entering data in Web Backoffice) of the practical course...

Intelligence in Control Info:


Now you will see that GeneXus takes the control info into account only when necessary. Enter to the CrewPositions transaction. Although the 'PosId' attribute is a Dynamic Combo box, it is not visualized as such in this transaction. The webform is created as default by GeneXus . Nevertheless, in the 'CrewOnBoard' transaction it does appear as Dynamic Combo Box and besides the description is 'PosDsc' Title.

Descriptions instead of codes (Input Type, Suggest, dynamic combos)


We can apply these features to edit controls or dynamic combos. They are most commonly used in foreign keys.

1. Modify the Passengers transaction so that the country and the city of departure as well as the cities of destination are dynamic combos.

2. Open the Flights transaction and modify the CrewId attribute to "disguise" it as CrewName. Likewise, enable the attribute autocomplete so that the user does not have to remember the exact name of the passenger but only how it starts. Where did you do this, at attribute level or at control level? What's the matter with this attribute in the CrewOnBoard transaction?

3. You can try to modify the grid Rows property in Flights, so that it shows only one line in insert, and you can add a button to add empty lines, one or two at a time (remember the AddLines method and the Rows dynamic property).

4. Modify the description attribute of the Charter transaction for it to be CharterDsc instead of CharterMod, and disguise the CharterId attribute for it to show and accept CharterDsc values as entry.

Update rule

The moment you are entering a flight, you may need to modify the charter model located in the flight extended table.