Skip to content
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.

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

Trigger Naming Conventions #15

Open
miklane opened this issue Jan 3, 2017 · 0 comments
Open

Trigger Naming Conventions #15

miklane opened this issue Jan 3, 2017 · 0 comments

Comments

@miklane
Copy link
Member

miklane commented Jan 3, 2017

Update Trigger naming conventions to [appname][object Name][Operation]

Triggers should have one trigger handler per object and then before insert/update and after insert/update triggers per app

|Process Name | &lt;Event that fired the approval&gt; Note that this is not the action or actions being performed but the original event that will trigger the entry criteria. This allows the approval actions to change over time. <br/>Including the salesforce object in the rule name is unnecessary as there is a standard field in the list view that can show this and filter on it. Whole words should be used and use of acronyms and abbreviations should be limited.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant