01es

### Description From the navigation perspective, each Entity Centre is represented by a single module menu item, which can be either accessed from a module menu or from the menu...

### Description Selection criteria for union properties of the same union entity have `OR` semantics – conditions applied to corresponding selection criteria are combined using `OR`. However, such an OR-group...

### Description Saving of modified and new entity instances happens in a database transaction. Transactional scope is demarcated by `@SessionRequired`. Hence, in TG applications, transactions are referred to as "sessions"....

### Description Offline mode for modern Web Apps is a must and the platform should support it out of the box. It is unclear at the moment how generic such...

### Description With advanced filtering and ordering, pagination through a dataset from page to page is usually sufficient. However, there are use cases where it would be convenient to jump...

### Description Insertion Points (IPs) have their designated placement as part of the overall Entity Centre layout. They can be resized vertically and expanded to full screen. As the next...

### Description Currently, when running Entity Centres, all insertion points with embedded Entity Centres, cances selection criteria values that might have been entered by the user. This behaviour ensures that...

### Description Attachments could be of any supported files. However, image files, which in many practical cases originate from mobile devices, contain useful metadata. In order to take advantage of...

### Description In TG there is a concept of "hyperlinks", which are strings that represent valid URLs. Hyperlinks are modelled with type `Hyperlink`, which has a single public constructor `Hyperlink(value:...

### Description TG supports running applications in a predefined timzone where both the server and the client sides work as if they were in the same timezone. The calendar view...