Best Practices - Representation Classes

The purpose of this document is to provide best practices when developing a representation class.

Representation name

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.

Representation name for mobile

A representation class for mobile should have the same code as the main data table and the data class, 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.

Representation property names

• For each property, use the same name as the one used for the data class properties and the data table properties.
• Assign the same code in the data table, the data class, and the representation class. While this is not mandatory, it makes it easier to understand and maintain.

Representation properties for mobile

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

Data management can be handled using processes. You can add all the nice-to-have screen handling to the representation class.