Coding standards

Naming standards

Code naming standards

Package / naming placement

Class naming

Naming convention follows Java standard

In addition the following are recommended

Database naming standards

Table naming

System tables should follow this syntax

Reserved prefixes include

Table attribute naming

General rules

Changelog attributes fixed names

Compliance standards

The platform must be able to run on

Safety standards

Review standards

The following changes requires a formal code review

Solution staging

  1. Transfer solution
    • Source: Make backup, view XML, copy
    • Target: Add repository item, create this item
  2. Transfer templates
    • Source: Check solution setting for Template (if not Default)
    • Source: Download template file / Copy template content
    • Target: Add new template and upload template file / paste content
    • Target: Update solution setting for Template (if not Default)
  3. Transfer stylesheet
    • Source: Check solution setting for Stylesheet (if not Default)
    • Source: Copy stylesheet content via stylesheet page (recursive)
    • Target: Add new stylesheet and paste content
    • Target: Update solution setting for Stylesheet (if not Default)
  4. Transfer media files
    • Source: Check files referred in stylesheet
    • Source: Check files referred in links
    • Source: Download files
    • Target: Create media file and upload files
    • Target: Update file references (TEMPORARY)
  5. Transfer wrapper
    • Source: Check interface setting for Wrapper (if not Default)
    • Source: Copy wrapper content
    • Target: Add new wrapper and paste content
    • Target: Update interface setting for Wrapper (if not Default)

Test cases

Test cases Fields