For those Salesforce organizations, especially those who store PII (personally identifiable information) or PHI (protected health information) data, security requirements may dictate that Salesforce access is locked down and users are to only use SSO (single sign-on) to authenticate into Salesforce. However, having the “Is Single Sign-on Enabled” system permission does result in some limitations… Continue reading Temporarily Remove a Permission Set w/ Process Builder & Flow
Need to temporarily grant system administrator access to a user? Learn how to do this with declarative actions.
I want to give a shout out to Bryan James, developer at MapAnything, for assistance on identifying the MapAnything customized user settings. Thank you for your help, Bryan! You’re the best! Here are a few lessons learned from implementing this use case: Learn how to automate package license assignment or removal on other criteria that is… Continue reading Automate the Assignment/Removal of MapAnything License and User Settings Based on User Role
This blog post was inspired by Randi Thompson. Here’s to you, Randi! Here are a few lessons learned from implementing this use case: Learn how to invoke flow from process builder. Use custom labels to avoid hardcoding Salesforce record type Ids in flow. Provide descriptions, where provided, in Salesforce. This may be tedious step, I… Continue reading Create a Person Account For New Email-to-Case
The list of Summer ’17 features below only apply to both Salesforce Classic and Lightning Experience. There are additional Summer ’17 features available to Lightning Experience only and Salesforce Classic only. Visit the Summer ’17 Release Highlights post. 1.Remove the ability for users to switch back to Classic. By enabling the “Hide Option to Switch to Salesforce Classic” on… Continue reading Summer ’17 Salesforce Classic & Lightning Experience Highlights
The list of Summer ’17 features below only apply to the Salesforce Lightning Experience. There are additional Summer ’17 features available to both Lightning Experience and Salesforce Classic and Salesforce Classic only. Visit the Summer ’17 Release Highlights post. 1. Search Enhancement: Find the right opportunity by searching for opportunity name plus the account name. 2. Success message from… Continue reading Summer ’17 Salesforce Lightning Experience Only Highlights
Southeast Dreamin’ has brought me to Atlanta, Georgia for the first time. And my first experience with southern hospitality. The people are so sweet, polite and super nice. It’s quite refreshing. I was excited to have a travel buddy, fellow MVP Matt Bertuzzi, for the trip to and from Boston to Atlanta. It’s always nice to… Continue reading Southeast Dreamin’ 17 – A Community Event w/ a Sprinkling of Southern Hospitality
Developers know that it is not a best practice to hardcode IDs in code, as documented in the Salesforce Developers site. https://developer.salesforce.com/page/Best_Practice:_Avoid_Hardcoding_IDs It is a big pet peeve of mine when I see hardcoded IDs in formulas, validation rules, process builder, flow, etc. The same best practices apply on the declarative side as with the development… Continue reading Did I Just See You “Hardcode” a Salesforce ID? Aw, Hell No!
Here are a few lessons learned from implementing this use case: Automate the profile assignment and role removal of a deactivated user via process builder. Use a custom label to store the profileID for the Inactive User profile versus hardcoding the ID in your process builder. This blog post was inspired by Ashley Papp who… Continue reading Automated Cleanup When User Is Deactivated – Assign to an Inactive User Profile and Remove Role
Here are a few lessons learned from implementing this use case: Automate the removal of permission sets from a deactivated user. Understand the structure of permission set and permission set assignments. Use process builder to invoke flow. Strengthen your flow from faulting by adding decision elements. Provide descriptions, where provided, in Salesforce. This may be… Continue reading Automated Cleanup When User Is Deactivated -Remove User from Permission Sets