Best practice representation classes
The purpose of this document is to provide best practice guidelines when developing in Version 7.
The following rules are considered ‘best practice’ when developing a representation class:
Be consistent. Use the same code throughout the development process. A representation class should have the same code as the main data table and the data class. For example, if the data table code is 'MYCODE', use 'MYCODE' for the data class code and the representation class code.
A representation class for mobile should have the same code as the main data table and the data class but with a suffix. For example: if the data table, data class and representation class code is 'MYCODE', use 'MYCODEM' for the mobile representation class code. This will ensure the representations for a class are listed together when you are performing a search.
Be consistent. Use the same name for representation class properties as used for the data class properties and the data table properties.
Even if it is not technically mandatory, assign a single code to a property in the data table, the data class, and the representation class. It is easier to understand and to maintain.
A representation class for mobile must include all the mandatory properties. Be selective with any additional properties to ensure your representation can fit on a mobile device.
Data management can be handled using processes. You can add all the nice-to-have screen handling to the representation class.