In LANSA, a process is a group of related functions (programs). A process can be thought of as a container which holds RDML functions. It also provides an interface or menu to the functions it contains. Every LANSA function must be defined as part of a process. If you are developing with components (such as Forms, Reusable Parts or WAMs), you will not require a LANSA process.
When used in an interactive environment, a process appears as either a menu with a selection of user options, or as an action bar. (Refer to 4.2.2 Process Style.) A process can be thought of as an interpretive control table or menu used to access functions. It is not a "coded" program (it has no RDML) , but it must be compiled. When used in a batch environment, a process usually consists of only one function or a group of closely related functions (such as related reports).
Following are some important characteristics of processes:
The design of the application system will determine how many processes are required and what functions will belong to a given process. The process/function structure in LANSA is an important part of modular design, which helps to build maintainable systems. (Refer to Processes and Functions in the LANSA Application Design Guide.)
Platform Considerations
Also See