Example:
In the following Transaction, the names of the employees and their managers, who also happen to be company employees, are entered.
Employee Transaction
EmpCod*
EmpNam
EmpManCod sub-type of Manager.EmpCod
EmpManNam sub-type of Manager.EmpNam
EmpManNam is inferred from the same table. Moreover, the referential integrity check of the table is carried out with the table itself in EmpManCod.
3- Updating sub-types that are inferred from the rules of a Transaction or a Procedure is now possible.
E.g.: use of the add and substract rule in Transactions.
4- Establishing an order per inferred sub-type in a For Each is now permitted.
5- Vertical formulas based on attributes that are also sub-types may be defined.
6- Checks upon specification time when defining groups of sub-types have been added. These checks issue alerts if the groups have not been correctly defined, thus making it easy to spot, in a timely manner, the invalid sub-type/super-type combinations that may have been generated. Checks have also been added for the use of sub-types in the objects in order to warn against ambiguous references or sub-types that cannot be instanced.
Moreover, the use of sub-types in the Olimar version has reaped the benefits of the improvements made on the reorganization of GeneXus. After this version, the reorganization will no longer be carried out in two steps, since a super-type will be replaced by a sub-type. Also, possible referential integrity errors will be avoided during reorganization (for instance, upon creating super-types from sub-types).
More information at GXDL:
http://www.artech.com.uy/betas/gxdl/iehelp.htm?English/Genexus_Olimar_Beta_3/DevEnv/Docum/ReleaseNotes/Olimar/Subtipos.htm