Home 
 1. Designer User Interface 
 Themes 
 Ribbon Menu 
 Window Panes 
 Customisation 
 Navigation 
 2. Process Design 
 Styles 
 Sub-Processes 
 Business Objects 
 Naming Conventions 
 Layout 
 Integrated Help 
 3. Form Design 
 Form Properties 
 Fields 
 Fields and Variables 
 Option Lists 
 Field Grouping 
 Field Layout 
 Tab Order 
 4. Multi-Language Support 
 Adding Languages 
 In the Client 
 Dynamic Options 
 Conclusion 
 5. Business Objects 
 Architecture 
 System Business Objects 
 Custom Business Objects 
 Using Business Objects 
 6. Naming Conventions 
 Variables 
 Processes 
 Solution Tables 
 Roles 
 Forms 
 Business Objects 
 Admin Groups & Forms 
 Stages and Actions 
 Visual Script Activities 
 Flags 
 Projects & Solutions 
 7. Writing Code 
 8. Reports 
 9. Component and Code Reuse 
 10. File structure 
 11. Web Client 
 12. Administration Tools 
 13. Summary 
Solution Tables
graphic
When we define Solution Tables we employ the same naming conventions as we use in the Process Tables.
graphic
We do not, however, use the name eFolderId in Solution Tables that relate to Process tables using the Folder ID. If you do this, you end up with an extremely confusing schema that anyone who did not design the system cannot determine from the names alone.
We use a convention of <ProcessName>Id for these fields, so that it is clearly not a Process Table, and the related table is clearly identifiable. Given the same table prefix, this is rarely difficult to work out at a glance.
Go to:
Roles (Next topic)
Top