Segments (segment-stereotyped classes) generally function as the top-level definition of your application. They are sometimes referred to as a ‘component’, and own all the model entities that the application consists of.
Segments have inherent behavior related to:
Control of application user connection and disconnection.
Control of database connection and disconnection.
Persistence of session state for the Ispec cycle.
Control of the segment cycle, which includes:
Unpacking of input messages to sufficiently identify their source and the ispec to be invoked
Invoking the ispec and its Process method with indication as to which part of the segment cycle the session is in
Assembling and delivering the output message
Enacting Recall and SwitchTo actions
Invoking public methods
Transactional integrity.
Segments have the following inherent members:
Built-in Segment Attributes, such as Glb.Status, Glb.Error, Glb.User, and so on.
Built-in StartUp, CloseDown, and ProcessMsq segment methods:
Startup is called on application start up
CloseDown is called on application close down
ProcessMsq is called to perform the segment cycle
A model can have multiple segment members.
Entities within a segment can be grouped using folders.
The default window is Members. Refer to Segment Properties for properties applicable to Segments.