Java/Universe interface

• When changing Universe programs, try to remove redundant screen-specific AREV code. Only attempt this if you understand the code being removed. Commands like LFS.WINDOW, REDISPLAY etc are not required for browser screens. Before removing a piece of code please ensure that it is not used. In some instances references to this code from the calling program may also need to be removed.
• Browser screen based function names in Universe must start with LFI.
• The naming convention for class method functions in Universe is LFI.{ClassName}.{MethodName}.
• LFI.* programs should NOT be called from other Universe programs – they are to be called from Java methods only.
• Create one function per one method in a class – one to one relationship. These methods do not necessarily have to be used by a Browser screen, could be used by a data import process.
• Browser Screen validation – All Lifefit database based validation in a Browser screen should be done in Universe i.e. Validation checking against a policy, plans, client etc. Basic validation like numeric, date etc should be done in Java.