What Not To Do on Salesforce скачать в хорошем качестве

What Not To Do on Salesforce

10 Tips You Can Use To Avoid Common Pitfalls on Salesforce. Tip 10: Form Factor Awareness 🚫 Don’t underestimate the overhead it takes to manage form factors. ✅ Do use standard lighting pages templates whenever possible. If you expose custom components in App Builder declare supported form factors in their respective design files and implement width-aware styling patterns. Learn more: https://sfdc.co/DP0aY 💫 Tip 9: User vs. System Context for Automations 💫 🚫 Don’t build an automation without understanding what context (system or user) it will run in. Ignoring this detail can result in a multitude of issues, including a loss of data integrity. 💡 Do remember that different automation tools will or will not run in different contexts: 👩🏽‍💻Apex will run in system context by default. As of Spring ’23 you can now specify user mode for database operations. https://help.salesforce.com/s/article... 🌊 Flow has no single default behavior. A flow will run in user or system context based on how the flow is launched. You have the option to enforce sharing in system context. https://help.salesforce.com/s/article... 🚧 Processes Builders run in system context without sharing considerations (don’t use them!) Learn more: https://sfdc.co/vlhTA Tip 8: Transaction Handling for External System Operations 🚫 Don’t assume that all operations can be rolled back. Synchronous callouts or actions that access external data aren’t included in any platform rollback behaviors. ✅ Do take advantage of platform rollback behaviors when working with external systems by using async Apex methods, asynchronous paths, or invocable actions. Learn more: https://sfdc.co/vlhTA Tip 7: The Build-Buy Spectrum 🔨 💰 🚫 Don’t only consider short-term savings. ✅ Do evaluate long-term app maintenance savings against the recurring costs of subscription-based apps. Avoid scenarios where you have to pay recurring costs for lots of functionality your business stakeholders will never use. Learn more: https://sfdc.co/obXRJ Tip 6: Maintainability 🚫 Don’t assume that a small change is harmless. 💡 Instead, remember that no customizations are trivial. Over time, every change has consequences. If you need to implement a custom solution, you can mitigate the inevitable technical debt your system will accrue by choosing to use low-code technology whenever possible, and by creating composable units in your implementations. Learn more: https://sfdc.co/obXRJ Tip 5: Sharing & Visibility 🚫 Don’t assume that Private OWDs are the optimal approach in every internal sharing use case. ✅ Do evaluate the sensitivity of the data and adjust your OWDs accordingly. If Private is not truly justified by the business need, use Public Read Only instead. Remember that CRUD permissions and field-level visibility aren’t actually controlled by OWDs. Learn more: https://sfdc.co/bbMrDg Tip 4: Lock Down Connected App Access 🚫 Don’t overlook API access control. Did you know that anyone with a valid set of credentials can connect any app to your org, even if the connected app isn’t pre-configured or installed? 💡Enable API Access Control to lock down all connected apps’ access to Salesforce APIs, then approve (allowlist) specific connected apps. Grant approved users for specific apps using permission sets. Learn more: https://sfdc.co/bcnHVN Tip 3: Session Security for Devices 🚫 Don’t underestimate the risks inherent to portable devices. If a mobile device is stolen and its wireless connection is disabled, OAuth tokens can’t be revoked. ✅ Enable passcode lock protection on the mobile connected app to require PIN/passcode unlock after inactivity. Learn more: https://sfdc.co/Pfi9H Tip 2: Authorization for API-based Logins 🚫 Don’t skimp on security for API-based logins. 💡 Instead, create a unique user for each integrated system to adhere to the principle of least privilege. Utilize the new Salesforce Integration user license, API Only System Integrations profile, and relevant permission sets and permission set groups to grant the integration user access to the org and data while restricting that access exclusively to API operations. Learn more: https://sfdc.co/bA1eHj Tip 1: Authorization for UI-based Logins 🚫 Don’t create bespoke permission sets for individual users. 💡 Instead use permission sets to describe jobs to be done, and permission set groups for personas. Mute permissions inside of a group to extend you existing permission sets even further. Learn more: https://sfdc.co/bA1eHj Connect with Salesforce Architects: Website: https://architect.salesforce.com/ Twitter: https://twitter.com/SalesforceArchs?s=20 LinkedIn:   / salesforce-architects