Naming Conventions

Business Object IDs

Convention: Upper camel case (Pascal case)

Examples:

Process:

• EditAccount
• Change
• StartAccountOpening

Script Function:

• PostVacancyReport
• TimeTrackerReport
• ExportMyPhoneList

Catalog:

• Currencies
• CaseTypes
• ReportCategories

Data class:

• Person
• AccountTypes
• Id
• AccountId
• NewNamedClass

Note: We advise against using project IDs or client names as you might want to reuse your project. Business Object ID Refactoring is anyway possible.

Process and Screen Names

Convention: Descriptive free text, using a dash to separate sections

Examples:

• ProjectId — SectionName — Tool
• ProjName — Account Opening — Enter Address

Data Class Attributes

Convention: Lower camel case

Examples:

• accountNumber
• id
• idType
• externalEmployee
• goLive

Note: When using Oracle, the maximum length is 30 characters. Oracle with History enabled only allows for a maximum of 26 characters.

Data Class Functions

Convention: Lower camel case

Examples:

• getNumber()
• getAllAccountTypes()
• isNumeric()
• filter()

Labels

Convention: Lowercase, words separated by dots

Examples:

• [LABEL:insert.name]
• [LABEL:name]
• [LABEL:perform.ultimate]
• [LABEL:kyc.check]

Process Designer: Connection Labels

Convention: Lower camel case

Examples:

• next
• back
• end
• cancel
• forwardTransaction
• undoInvoice