4.1.4 Process & Function Guidelines

The following are some additional guidelines for working with processes and functions:

• Process and function names should follow site standards. Be sure to define, publish and enforce your site standards.

• LANSA RDML provides a set of FUNCTION characteristics which can be standardized and made part of application templates. Review and use the FUNCTION options. For example, all functions must be *DIRECT if developing in a Visual LANSA environment.

• Use developer code reviews as a means of training new developers and as a means of checking that site standards are being followed.

• Use the LANSA application templates and customize these templates to meet your site standards. Templates are a quick way to ensure that all screens and reports have the same look and feel. (Refer to  Using Application Templates.)

• Create help text for all processes and functions. Because of LANSA's development security, you can even have users enter help text.

• Use the impact analysis tool to help control changes and assess what changes need to be performed. Impact analysis can save a significant amount of time testing and rebuilding your application. Impact analysis can also create lists for group objects.

• No process should contain more than 20 functions, unless it is a special subroutine or prompt key "grouping" process.

For details about designing processes and functions, refer to Processes and Functions in the LANSA Application Design Guide.

Also See

4.2 Developing with Processes and Functions