Naming Conventions

It makes sense to apply the same naming conventions and organization of the Implementation folder to all your Designer projects. This makes reading a model much easier.

Agree on one language for names and documentation. This can be your native language or English for international projects.

Suggestion for a naming convention:

	Convention		Example
General	upper or lower camel case		`MyClass`, `myObject`
General	for signal, exception, send signal action, scheduler, event observer, ports, RFC ports: Use element name in the name		`ApprovalSignal`, `MyScheduler`, `MyPort`, `MyRFCPort`
Classes	upper camel case		`MyClass`
Attributes	lower camel case		`myAttribute`
Operations	lower camel case		`myOperation`
Services	Don't use service in the name, except for base services.		`BaseService_Salesforce_01`
Services	Use a project specific pattern.		`Intelligix_Outbound_01`
Aliases	upper camel case		`SQLAlias`
Model Names	upper camel case		`MyService`, `IdeaManagement`
Model Names	Libraries	Lib suffix	`FTP_Lib`