Components
Uniface application components are interchangeable software modules that handle application processing. They are technology-independent, so compiled components can be run on any operating system.
Uniface components handle most of the processing of a Uniface application. A Component is defined as a main development object. When compiled, it results in a runtime component and a descriptor (known as a signature) that describes the component's public operations and related parameters.
Uniface enables you to define different types of components to suit different requirements. Thus you can define dynamic and static server pages for the user interface of web applications , form components for desktop applications, and services for backend functionality.
Each component contains component entities and fields, which define the data accessed by the component and the user interface used to display and edit the data. In most cases, component entities and fields are references to modeled entities and fields, and they inherit the properties, script, and other definitions from the modeled objects. You can override inherited definitions in the component, if necessary, and add component-specific script to define the component behavior.
It is also possible to define component-specific entities and fields—non-database objects that can be useful if you need to define transient information that does not need to be stored or reused.
Each component has code containers in which you can define component-level triggers and operations using ProcScript. The available triggers depend on the type of component.
