Configure Features with Guided Setup
Guided setup walks you through setting up visibility, processes, workflows, record types, layouts, and assignment rules for Salesforce features. From start to finish, guided setup leads you through each step with easy-to-follow directions and navigable links to settings pages.
As long as you have a Partner license, you can access Guided Setup from Experience Workspaces. Click the Guided Setup tile, and select which feature you want to set up.
Over the last few years, GraphQL has emerged as a very popular API specification that focuses on making data fetching easier for clients, whether the clients are a front-end or a third-party.
In a traditional REST-based API approach, the client makes a request, and the server dictates the response.
For example, the client may want only the user’s name and email, and none of the address information.
For single-page apps (SPAs) or other front-end heavy client-side applications, this speeds up rendering time by reducing the payload size. However, as with any framework or language, GraphQL has its trade-offs. In this post, we’ll take a look at some of the pros and cons of using GraphQL as a query language for APIs, as well as how to get started building an implementation.
Getting Started with Enhanced Transaction Security Policies
What if I told you that you could prevent your users from adding fields containing sensitive data to their reports as they build and edit in the report builder? Or that you could require two-factor authentication when a user logs in from an outdated browser version? Well, you’re in luck, transaction security policies are one of the coolest features in Salesforce you might not have known existed! They give you the ability to block the transaction or alert an admin when a user does something that might be suspicious. By bringing together transaction security policies and Apex conditions, we can take our org’s security to the next level.