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 
Projects & Solutions
We do not have any naming conventions for Projects. They do not need a prefix, and as long as they are suitably descriptive, that is acceptable.
As Projects do not have any kind of ‘Caption’ that may be used for presentation, it is actually very important that the names of Projects are not garbled. It will not make the system more readable or understandable, and it can cause confusion.
Solutions can be named anything you like as long as it does not violate Windows file naming conventions, as far as we are aware. The Solution name is also not important like the Procedure name used to be in Version 7 and earlier. It is merely a container for the Project and Library files.
Top