Skip to content

Update Salesforce-Naming-Conventions.md #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
salesforce-john-zz wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update Salesforce-Naming-Conventions.md #23

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions _pages/Salesforce-Naming-Conventions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
##Salesforce Naming Conventions
## Salesforce Naming Conventions

Naming conventions make the application easier to read and maintain. The naming standards documented here cover customization and configuration areas of salesforce. Regardless of the context in which names are used, Names should be descriptive, concrete, and specific rather than general. Having a generalized name such as ProductLine can have different semantics depending upon the context. It’s better to use something the business identifies with and that will not create a potential conflict with other applications; e.g., ReverseMortgage.

Expand Down Expand Up @@ -355,7 +355,7 @@ None

The following are examples of trigger naming naming that should not be used

Validation Rule Name | Reason
Trigger Name | Reason
-----------|:------
UpdateAccountAddresses | The object name should always be before the operation in the name.
AccountUpdateContacts | Is specific to a business function and would allow for other update triggers to be created for the same object.
Expand Down