So, having taken a look through the physical and logical RPD layers of OACS.  Now lets move onto the presentation layer.   Many people see the presentation layer as a simple ‘this is what the customer sees’ non-entity that has to be produced, however hopefully this post will prove otherwise.  

OACS RPD Presentation Layer Best Practices 

Customizations 

To synchronize all changes between the Business Model and Mapping layer and the Presentation layer, it is best to wait until the Business Model and Mapping layer is relatively stable before adding customizations in the Presentation layer 

Presentation Object Renaming 

Its best practice to rename objects in the logical layer than the presentation layer, if you rename in the logical layer the presentation layer with automatically change.  This makes supporting the RPD much easier.  

Small Presentation Areas 

Keep presentation areas small and focused on the business processes they are supporting, the more tables and processes we add into a single subject area, the more complicated it becomes. 

Hover-Over Descriptions 

Add hover-over descriptions to presentation items. These should explain the data content and any calculation formula (if not too complex).  This greatly helps the end user and minimises helpdesk calls.  Any complex calculations should be put into a custom help page, or a metadata dictionary. 

Child Tables 

Use child tables in the presentation area.  This is useful so break down complicated folder structures. 

Default Permissions 

Be sure to set the default_privileges in NQSConfig, this ensures that you don’t accidentally show something to a user that is not authorized to see it.  Very important for implementations with multiple external customers.  

Order of Objects 

Presentation tables should be listed in the order of: Dates, Dimensions (Alphabetical), Facts (alphabetical).   Columns within date dimensions shold be listed in chronological order, columns within facts and dimensions should be listed in alphabetical order.  Its also sometimes useful to group facts if required. 

Security 

Consider setting object permissions per role, rather than setting permissions for individual columns.  Column level permissions can become messy and difficult to identify for users other than the original developer.  

Presentation Column Aliases 

If you rename a column in the presentation area, it will produce an alias for the column, where possible, when renaming a column, delete the alias to avoid confusion to the end user and naming clashes