Customers / Administrator’s Point of View

1. Be Ready for Multi-Factor Authentication Auto-Enablement: – The requirement to use multi-factor authentication (MFA) when accessing Salesforce products went into effect on February 1, 2022. All users must now use MFA when they log in to Salesforce, whether they’re logging in directly or using single sign-on (SSO). To help customers satisfy this requirement, in the first half of 2023, Salesforce is automatically enabling MFA for direct logins. In fall 2023, Salesforce is enforcing MFA by making it a permanent part of the Salesforce login process. To avoid disruptions to your users when these milestones occur, enable MFA as soon as possible.
   1. Get customizable templates for rollout planning and change management by downloading the MFA Rollout Pack.
   2. To monitor the MFA enforcement milestone schedule, see the MFA Enforcement Roadmap.
2. Let Service Resources Add Multiple Topics to a Shift: – Territory managers and service resources can define the availability of resources for multiple topics by adding one or more topics to a shift. Use Work Type Group to define topics. If the Salesforce Scheduler for Health Cloud option is enabled, then define topics by using Work Type. Salesforce Scheduler shows service resources and available time slots based on the topic that a user selects when creating an appointment.
   1. On the Salesforce Scheduler Settings page, under the Multiple Topics for Shifts section, complete the prerequisites provided in the link (1). Then enable Multiple Topics for Shifts.
3. Review a Custom Report Type’s Structure During Report Creation: – Not sure what custom report type to use when you create a report? You can now view the structure of available custom report types and choose the best one for your needs. The details panel shows the relationships between the joined objects, and tooltips explain the outcome of the joins.
   1. Create a report and select a custom report type. View the object and join details.
4. Do More with Dynamic Related List Filters: – Now when you filter dynamic related lists in the Lightning App Builder, you can select multiple filter values for picklist fields. For example, on the Contact record page, filter a dynamic related list to show all cases with a priority of Medium or High. Previously, you could filter by only one picklist value.
   
5. Get More Options for From Addresses in List Emails: – Make a list email appear like it’s coming from a group, such as sales@company.com, or a tailored user, such as jsmith@company.com. Recipients react differently to emails depending on the sender’s name and email address. For example, something from a support department is more likely to be opened than something from an unknown person.
   1. When a rep chooses from multiple email addresses, replies automatically go to the email address of the sender. Replies to an email from sales@company.com go to that org-wide email’s work queue, while replies to the created email jsmith@company.com support a market attribution calculation
6. Identify Which Sandboxes Get a Preview of the Next Salesforce Release: – View which sandboxes get upgraded early (preview), and which sandboxes are scheduled to be upgraded with production orgs (non-preview) during major Salesforce releases. Preview sandboxes provide early access to new features, so you can test your configurations before the production upgrade. Preview sandboxes are upgraded approximately 6 weeks in advance of production orgs during every major release.
7. Enhance More Object Record Pages With Dynamic Forms: – You can make your account, including person account, contact, and opportunity record pages more robust by configuring them with Dynamic Forms.
   1. In the Lightning App Builder, open an account, including person account, contact, or opportunity record page. Click the new Fields tab, and place fields anywhere on the page. Or automate the process by migrating your Record Detail component to use Dynamic Forms with the click of a button.
8. Manage Your Permission Assignments with the User Access and Permissions Assistant: – Analyze and report on permission assignments with the User Access and Permissions Assistant. Manage your permission set groups easily, and convert to permission sets that you can assign. Previously, this feature was known as Permissions Helper.
   1. To use this feature, download the app from AppExchange. Complete the tasks to enable the Tooling API for the app. And then create and assign permission sets for users who must access the app.
9. Download Data Loader v56 Installer Files From a New Location: – Download Data Loader from https://developer.salesforce.com/tools/data-loader. Previously, the Data Loader installers for Windows and macOS were hosted on GitHub. The download link is also available on the Data Loader page in Setup.
10. Review Prospects with Bot-Like Activity: – To protect the health of your business unit, Account Engagement can pause activity tracking for prospects with an excessive amount of activity. When a prospect’s activity tracking is paused, an icon appears on the prospect list view and an error appears on the prospect record. A prospect’s activity tracking is paused only if it impacts Account Engagement’s performance. Paused prospects who are opted in can still receive marketing emails.
11. Simplify Prospect Opt-Out Status Between Account Engagement and Salesforce: – The prospect Opted Out field now requires a designated system of record, giving you one place to check for a record’s opt-out status. Choose between Account Engagement or Salesforce as the primary value for the prospect Opted Out field. Previously, the Opted Out field inherited the value from the most recently updated record.
    
    1. Edit the default prospect Opted Out field, and select an option under the Sync Behavior dropdown. In business units created after August 26, 2022, the field is set to use Pardot by default.
12. Connect Securely to Amazon Athena and Perform Interactive Queries from Salesforce (Generally Available): – Use the Salesforce Connect adapter for Amazon Athena to integrate AWS data natively with Salesforce and to run interactive ad hoc queries. The new adapter takes advantage of Amazon Athena’s capability to run queries against data directly in Amazon Simple Storage Service (S3), without managing RDBMS infrastructure or ETL tools.
13. Perform Async DML Operations for Cross-Org Adapter with Corrected External Object IDs: – When you initiate asynchronous DML operations on external objects with the cross-org adapter, the correct record IDs are passed to the job placed in the background jobs queue. The record IDs of external objects with the cross-org adapter are now assigned the correct key prefix x00. Previously, the record IDs began with an incorrect key prefix 001.
14. Sell Subscriptions to Customers and Partners in Experience Cloud: – Capitalize on your investment in proven sales channels with minimal additional overhead. Subscription Management powers a self-service storefront for authenticated users in your Experience Cloud channel. Your customers or partners can use your storefront to buy and renew subscription products, while you use Subscription Management to manage your catalog and automate invoicing, payments, and refunds.
15. Access All Omni-Channel Setup Tasks from One Page: – Less searching in Setup, more doing. To learn more about what Omni-Channel components to set up and get a list of all setup tasks, go to the new Omni-Channel setup home. The setup home also provides warnings when items aren’t correctly configured. On that page, you can also view details about and click a link to access every service channel instance defined for your company.
    1. To view Omni-Channel Home, select Omni-Channel Home in Setup.
16. Start Bundling Appointments Quickly: – After you enable Appointment Bundling, your dispatcher can start bundling appointments right away. Field Service gives you all the default configuration that you need to get going. Use the default configuration or modify it to fit your company’s needs.
    1. From Field Service Settings, enable Appointment Bundling. The default policies are created and can be accessed from the App Launcher.
17. Self-Join Nodes in Data Prep: – Self-join nodes in recipes when an object has a foreign key relationship to itself.
    1. In a Data Prep recipe, connect a node to itself and click Join.
18. Take Advantage of the Enhanced Sites and Content Platform (Generally Available): – The enhanced sites and content platform brings together the power of Salesforce CMS and LWR sites. With this flexible new platform, you can create enhanced CMS workspaces in the Digital Experiences app so you can easily create, manage, and publish your content. Manage content in multiple languages, harness the organizational power of content collections, and then share your content with enhanced LWR sites.
19. Help Users with More Targetable Locations and Backdrop: – More granular elements are targetable using targeted prompts for In-App Guidance. To draw more attention to the component being highlighted, targeted prompts now come with a gray backdrop.
    1. You can control what users notice so that they can easily find the item the prompt refers to.
    2. You can now target:
       1. List view dropdown menu, pin, and buttons in the header
       2. App name
       3. App Launcher
       4. Items in the navigation bar, including items in the item’s dropdown menu
       5. Record tabs and subtabs
       6. Record highlight panel fields
    3. All targeted prompts, including targeted prompts created before Winter’23, have a gray backdrop. Users click outside of the prompt to remove the backdrop.
20. Track SSO and MFA Logins to Connected Tenants: – For security, track logins that use single sign-on (SSO) and multi-factor authentication (MFA), including who logged in to a specific tenant and how often.
    1. In the Security Overview panel, under Authentication, select MFA & SSO to open the dashboard.
21. Respond to Customers Faster with Quick Text in Messaging for In-App and Web: – Reduce agent response times and standardize your brand’s voice with Quick Text. Agents can insert pre-written greetings and answers to commonly asked questions into the conversation. All Quick Text features except Folders are supported.
    1. Quick Text is turned on automatically. Agents use the Quick Text button to insert text and create new text.
22. Salesforce CMS
    1. To improve Salesforce CMS performance, each instance is limited to 300 channels. This limit doesn’t include Experience Cloud sites connected to CMS workspaces.
    2. To improve Salesforce CMS performance, each instance is limited to 2,000 workspaces. This limit includes CMS workspaces and enhanced CMS workspaces.
23. Product Renamed
    1. High Velocity Sales Was Renamed to Sales Engagement
    2. Sales Cadences Were Renamed to Cadences
    3. MuleSoft Composer for Salesforce is now Flow Integration.
    4. Salesforce CDP Has Been Changed to Customer Data Platform
    5. myTrailhead Were Renamed to Enablement Sites 

1. Create Overlays with the New Modal Component: – Use modals to interrupt a user’s workflow and draw attention to an important message. A modal, which displays the message on top of the current app window, requires a user to interact with it to regain control over the app.
   1. To create a modal component, import LightningModal from lightning/modal in your JavaScript file. Then, create a component class that extends LightningModal.
      Copy Code Copied Use a different Browser

      
      /* c/myModal.js */
      
      import { api } from 'lwc';
      import LightningModal from 'lightning/modal';
      
      export default class MyModal extends LightningModal {
      
          handleOkay() {
              this.close('okay');
          }
      }
      

   2. This component doesn’t use a lightning-modal tag. Instead, the modal’s HTML template uses helper lightning-modal-* components to make the modal’s header, footer, and body. The lightning-modal-body component is required, and the others are optional.
      Copy Code Copied Use a different Browser

      
      <!-- c/myModal.html -->
      
      <template>
          <lightning-modal-header label="My Modal Heading"></lightning-modal-header>
          <lightning-modal-body>This is the modal’s contents.</lightning-modal-body>
          <lightning-modal-footer>
              <lightning-button label="OK" onclick={handleOkay}></lightning-button>
          </lightning-modal-footer>
      </template>
      

2. Fix Invalid HTML Syntax to Avoid Component Loading Errors: – Invalid HTML syntax in your LWC markup now results in a runtime error. Previously, components loaded without returning a warning even if they included invalid HTML syntax. 
   1. The framework enforces valid syntax in all Lightning web components. In Spring’22, the web console displays invalid HTML syntax warnings to promote standard HTML practices in your code. In Winter’23, these warnings are converted to errors and can prevent your components from loading correctly. Invalid HTML syntax includes:
      • Missing or misplaced DOCTYPE tag
      • Missing or misplaced head start tag
      • Nested noscript in head element
      • Non-matching opening and closing tags
      • Unexpected end of file
      • Unexpected metadata element after head element

      LWC flags invalid markup for you, such as a missing closing tag or an extra closing tag. You can also enable HTML validation in Visual Studio Code using an HTML validator plugin. For example, remove the extra </template> tag in this component example to prevent runtime errors.

      Copy Code Copied Use a different Browser

      
      <template>
          <div>Hello</div>
          </template> 
      </template><!-- Remove extra closing tag -->
      

3. Fix Invalid Template Usage to Avoid Warning When Component Loading: – Loading an LWC component results in a warning if your component includes a <template> element with an invalid attribute. On non-root <template> elements, only for:each, iterator:iteratorName and if:true|false directives are supported.Salesforce recommend that you fix your component template to remove invalid attributes in your <template> element.
   
   In Spring’23, this invalid usage of the <template> element doesn’t render correctly and loading a component that contains this invalid usage will result in an error.For example, the non root <template> element in this example contains an invalid attribute.

   Copy Code Copied Use a different Browser

   
   <template>
       <!-- This template element contains an invalid attribute -->
       <template class="slds-m-around_medium">
           Hello
       </template>
   </template>
   

   To fix the warning and make sure that your component continues to load correctly in future releases, remove the invalid attribute or use another element like <div> or <span>, depending on your use case.

   Copy Code Copied Use a different Browser

   
   <template>
       <div class="slds-m-around_medium"> 
           Hello
       </div>
   </template>
   

4. Remove Non-Global Design Tokens in CSS: – Only design tokens labeled as Global Access (GA) are supported in your Lightning web components’ CSS. Non-global design tokens no longer work after Spring’23.
   1.  After Spring’23, usage of non-global design tokens, such as those labeled as internal (I), results in a validation error No TOKEN named tokenName found during component save for API version 57.0 and later.For example, this usage of the non-global --lwc-heightInput token isn’t allowed and returns the error No TOKEN named force:base.heightInput found.
      Copy Code Copied Use a different Browser

      
      /* This non-global token usage doesn't work */
      div { 
          height: var(--lwc-heightInput); 
      }
      

      
      The following usage is allowed, but it’s invalid because of the non-global --lwc-heightInput token, which is placed inside the calc CSS function.
      Copy Code Copied Use a different Browser

      
      /* This doesn't work after Spring '23 */
      .resultcontainer{    
          height: calc(var(--lwc-height-header) - (var(--lwc-heightInput)));
      }
      

      Replace the non-global tokens in your CSS with a global token or use a custom Aura design token instead.

      Copy Code Copied Use a different Browser

      
      div {
          height: var(--lwc-lineHeightText); /* use a global design token */
      }
      
      .resultcontainer {    
          height: calc(var(--lwc-height-header) - (var(--lwc-lineHeightText)));
      }
      

5. Enable Third-Party Integrations with Light DOM (Generally Available): – Lightning web components render in shadow DOM by default, providing strong encapsulation but posing challenges for global styling and many third-party integrations. With light DOM, your component markup is attached to the host element instead of its shadow tree. You can then access it like any other content in the document host.
   1. To enable a component to render in light DOM, set the renderMode static field in your component class.
      Copy Code Copied Use a different Browser

      
      import { LightningElement } from 'lwc';
      
      export default class LightDomApp extends LightningElement {
          static renderMode = 'light'; // the default is 'shadow'
      }
      

      Use the lwc:render-mode template directive on the <template> tag of your component.
      Copy Code Copied Use a different Browser

      
      <template lwc:render-mode='light'>
          <my-header>
              <p>Hello World</p>
          </my-header>
      </template>
      

      When you enable light DOM on a component, it no longer renders its elements in the #shadow-root tree.

      Copy Code Copied Use a different Browser

      
      <my-app>
          <my-header>
              <p>Hello World</p>
          </my-header>
      </my-app>
      

      A light DOM component can contain a shadow DOM component. Similarly, a shadow DOM component can contain a light DOM component. However, base Lightning components always render in shadow DOM. Restricting light DOM to specific namespaces isn’t supported.

      LWC doesn’t scope styles automatically for you. To prevent styles from bleeding in or out of a component, use a *.scoped.css file to implement scoped styles for a component.

6. Use DataWeave in Apex to Enable Data Transformation to Different Formats (Developer Preview): – DataWeave in Apex is now in Developer Preview. This feature enhances native Apex data transformation support by integrating Mulesoft’s DataWeave library into the Apex runtime. It makes data transformation easier to code, more scalable, and efficient. With this feature, Apex developers can focus more on solving business problems and less on addressing the specifics of file formats.
   1. You can create DataWeave scripts as metadata and invoke them directly from Apex. Similar to Apex, DataWeave scripts are run within Salesforce application servers, enforcing the same heap and CPU limits on the executing code.
   2. This example shows the transformation of an input CSV file into Contact SObjects.
      Copy Code Copied Use a different Browser

      
      // CSV data for Contacts\n
      String inputCsv = 'first_name,last_name,email\nCodey,"The Bear",codey@salesforce.com'; 
      DataWeave.Script dwscript = DataWeave.Script.createScript('csvToContacts');
      DataWeave.Result dwresult = dwscript.execute(new Map<String, Object>{'records' => inputCsv});
      List results = (List)dwresult.getValue();
      
      Assert.areEqual(1, results.size());
      Contact codeyContact = results[0];
      Assert.areEqual('Codey',codeyContact.FirstName);
      Assert.areEqual('The Bear',codeyContact.LastName);
      

   3. The CSV data is transformed to objects using the DataWeave script csvToContacts.dwl.
      Copy Code Copied Use a different Browser

      
      %dw 2.0
      input records application/csv
      output application/apex
      ---
      records map(record) -> {
       FirstName: record.first_name,
       LastName: record.last_name,
       Email: record.email
      } as Object {class: "Contact"}
      

7. Call Invocable Actions from Apex (Generally Available): – Invocable.Action is a new Apex class that allows you to call invocable actions from Apex code.
   1. For example, this class calls the standard invocable action “chatterPost” to post a message to the current user’s feed.
      Copy Code Copied Use a different Browser

      
      public class MyApexClass {
          public void postToChatter(String recordId) {
              Invocable.Action action = Invocable.Action.createStandardAction('chatterPost');
              action.setInvocationParameter('text', 'This is an example Chatter post.');
              action.setInvocationParameter('subjectNameOrId', recordId);
              List results = action.invoke();
              if (results.size() > 0 && results[0].isSuccess()) {
                  System.debug('Created feed item with ID: ' +
                  results[0].getOutputParameters().get('feedItemId'));
              }
          }
      }
      

   2. This class calls a custom invocable action named Doubler that returns a number that’s twice the input value.
      Copy Code Copied Use a different Browser

      
      public class MyApexClass {
          public void doubler (Double input) {
              Invocable.Action action = Invocable.Action.createCustomAction('apex', 'Doubler');
              action.setInvocationParameter('input', 1);
              List results = action.invoke();                                          
              if (results.size() > 0 && results[0].isSuccess()) {
                  System.debug('Result is: ' + results[0].getOutputParameters().get('output'));
              }
      
          }
      }
      

8. Salesforce Flow Enhancements: – There are several enhancements in Salesforce Flow as follows:
   1. Cut and Paste Flow Elements: – Change the order of flow elements in auto-layout faster by using cut and paste. Previously, to move an element on the canvas, you copied and pasted the element then deleted the original element, and then you updated the API name of the pasted element.
   2. Use Formula Builder in Flow Resources and Collection Filter Elements: – You can now use an enhanced formula builder in Flow Formula-type resources and the Collection Filter element. The builder guides you through the syntax so that you can create an expression more easily. Instead of waiting until you save a flow, you can check the formula syntax and catch errors as you work.
   3. Use Record-Triggered Flows to Update Related Records: – Now you can use record-triggered flows to update any records related to the triggering record.
   4. Launch Screen Flows With Lightning Web Components: – Embed a screen flow from any Lightning Web Component with the new lightning-flow component. Developers can supercharge their flows by customizing finish behavior, setting custom styling, or launching flows from their Lightning Web Components. And they can offload complex input collection and branching logic to Flow, saving time and money.
      1. This example shows an LWC component with the Survey_customers flow API name.

         <template>
             <lightning-flow
                 flow-api-name='Survey_customers'
             >
             </lightning-flow>
         </template>

   5. Filter Your Picklists By Record Type in Flow Screens: – Now you only see relevant picklist values when using Dynamic Forms for Flow. Previously, all the picklist values for a field appeared, regardless of whether a record type was provided, and could show irrelevant values.
   6. Select Multiple Records in the Lookup Flow Screen Component: – Now you can search and then select more than one record with the Lookup flow screen component. You can specify a selection maximum and one or more default records.
      1. Add the Lookup component to your screen flow and set the Maximum Selections field to a value greater than 1.
   7. Use In and Not In Operators in Flows to Find Related Records: – With the new In and Not In operators, a flow accesses a collection of primitive values to get related records without using the Loop element. The flow uses fewer SOQL queries and DML statements, and performs faster. The new operators support accessing collections of type Text, Number, Date, Date/Time, Currency, and Boolean. The operators are available in the Get Records, Update Records, and Delete Records elements.
      1. To ensure your flows don’t exceed governor limits, use the In operator. For example, a flow gets all related contacts if their role equals Decision Maker and if their related accounts have a shipping state in California. With the new In operator, the flow executes the Get Records element only three times. That’s three SOQL queries no matter how many contacts the flow finds.
      2. Because the In and Not In operators don’t support accessing values on record collections in this release, the flow assigns the account IDs to a text collection, caAccountIds. The Get Records element gets all related account contact roles if their account IDs are in caAccountIds and if their Role equals Decision Maker.
      3. The Get Records element gets all related contacts if their contact IDs are in contactIDs. And you’re done.
      4. Previously, the Loop element iterated over a collection of values to get related records. Each time the flow got a related record via the Loop element, the flow used one SOQL query. If the flow got over 100 records, the flow failed because it exceeded the governor limit of 100 SOQL queries per transaction. If you debugged the flow, the debug details showed over 100 executions of the Loop and Get Records elements.
   8. Test One, Two, Three, Flow (Generally Available): – Before you activate a record-triggered flow, you can now test it to quickly verify its expected results and identify flow run-time failures. In Flow Builder, you create, save, and run flow tests. Previously, you debugged a flow manually to troubleshoot failures each time they occurred. Now, you create and save a flow test from a debug run. Then each time you modify the flow, you can run the test. Flow tests don’t support flows that run when a record is deleted. This feature, now generally available, includes some changes since the last release. Flow tests now support scheduled paths. Previously, flow tests supported only paths that run immediately. Packaging is now supported.
9. Flow Orchestrator: – There are several enhancements in Flow Orchestrator as follows:
   1. Assign Steps to Credentialed Experience Cloud Site Visitors: – When an interactive step in an orchestration runs, it creates a work item and assigns it to a user, group, or queue. You can now assign or reassign an interactive step to a credentialed Experience Cloud site visitor. You can also assign or reassign an interactive step to a group or queue that includes only credentialed Aura site visitors or credentialed LWR site visitors.
   2. Create Reports with Flow Orchestration Objects: – You can now track your Flow Orchestration usage with Salesforce reports. Create reports that include Flow Orchestration Run, Flow Orchestration Stage Run, Flow Orchestration Step Run, and Flow Orchestration Work Item objects.
   3. Use Subflow Elements with Evaluation Flows: – Create more complex custom entry and exit conditions for orchestration stages and steps with the Subflow element in evaluation flows. And you can reuse your evaluation flows that contain common criteria. Evaluation flows can call only evaluation flows. And evaluation flows can be called only from other evaluation flows.
10. Write Clear and Intentional Apex Assertions: – Improve the readability of your Apex code by using the assert methods in the new System.Assert class that fit the exact conditions that you’re checking for. We still support the existing System class assert methods. But we also recommend that you start using the new ones soon and that you update your existing code to use them.
    1. Apex provides three assert methods. System.assert(), System.assertEquals(), and System.assertNotEquals(). While adequate for many use cases, these methods can result in ambiguous or verbose error messages. For example, this Apex code checks for a null value.
       Copy Code Copied Use a different Browser

       
       System.assertEquals(null, 'null');
       

       The resulting exception is correct, but ambiguous between literal nulls and null strings.

       Copy Code Copied Use a different Browser

       
       System.AssertException: Assertion Failed: Expected: null, Actual: null
       

       The new System.Assert class provides methods that handle all types of logical assertions and comparisons. When you use an assert method intended for a specific condition, the clarity of your Apex code improves. And if the assertion results in an exception, it’s easier to read and understand

11. Secure Even More Apex Code with User Mode Database Operations (Beta): – Run more database operations in user mode with the enhanced user-mode support. The new Database methods support an accessLevel parameter so that you can run the operations in user mode instead of in the default system mode.
12. Prevent Record Duplication with Idempotent Record Writes for UI API (Beta): – Use idempotent record writes to avoid duplication of records and server-side operations.Currently, only the /ui-api/records endpoint supports idempotent record writes for POST, PATCH, and DELETE requests. To make a request idempotent, include an Idempotency-Key value in your request header.
    Copy Code Copied Use a different Browser

    
    curl --location --request POST 'https:///services/data/v56.0/ui-api/records' \
    --header 'Authorization: Bearer ' \
    --header 'Content-Type: application/json' \
    --header 'Idempotency-Key: 12cfe4e6-e477-4de8-aa4e-95d31aa2be24' \
    --header 'Cookie: BrowserId=yVVAfz9GEeuRCtc5jOsncA; CookieConsentPolicy=0:0' \
    --data-raw '{
        "apiName": "ResourceAbsence",
        "fields": {
            "CreatedDate": "2022-12-01T14:52:16.000Z",
            "LastModifiedDate": "2022-12-01T14:52:16.000Z",
            "ResourceId": "0Hnxx0000004C92CAE",
            "Start": "2022-12-02T14:52:16.000Z",
            "End": "2022-12-03T14:52:16.000Z"
        }
    }
    

    The Idempotency-Key header value is in the UUID v4 format. You can use a library that supports UUID v4 generation, including the Java UUID utility.

    We recommend that you use a unique Idempotency-Key header value for each operation. The idempotency key doesn’t provide idempotency indefinitely and auto-expires after 30 days if the same key is reused.

13. Choose Any Name for a Global Value Set: – When you create a custom global value set or global value set translation in API version 56.0 or later, the developer name is appended with the suffix __gvs. You can now create a global value set or translation with any name and it doesn’t conflict with a standard entity of the same name.
14. Filter Your Stream of Platform Events with Custom Channels (Generally Available): – Optimize event processing by receiving only the event messages that match a predefined filter on a custom channel. Create a channel and configure it with a filter expression for CometD clients. With fewer events delivered, subscribers can make more efficient use of the event delivery allocation.
    1. With the Customize Application permission, you can configure stream filtering using Tooling API or Metadata API. To create a channel, use PlatformEventChannel. To add a filter expression for a custom platform event, use PlatformEventChannelMember.This example shows a filter expression value in the PlatformEventChannelMember.FilterExpression field.
       Copy Code Copied Use a different Browser

       
       (City__c LIKE 'S%' OR City__c='New York') AND Has_Shipped__c=true 
         AND Delivery_Date__c>2022-07-21T09:30:11-08:00
       

15. Develop Event-Driven Apps with Pub/Sub API (Generally Available): – Publish and subscribe to platform events and change data capture events using Pub/Sub API, a secure, highly performant, and scalable API based on gRPC. Use one of the 11 supported programming languages, including Python, Java, Go, and Node. Get peace of mind with final publishing results instead of intermediate queueing results. And with subscription flow control, fine-tune the number of event messages that you receive based on your event processing speed.
    1. gRPC requires defining a service, which specifies the methods that can be called remotely with their parameters and return types. The server implements this interface and runs a gRPC server to handle client calls. The client has a stub that mirrors the methods available on the server.
    2. Pub/Sub API uses protocol buffers as the Interface Definition Language (IDL) and as the underlying message interchange format. The Pub/Sub API service is defined in a proto file, with RPC method parameters and return types specified as protocol buffer messages. Within those protocol buffer messages, the payload of the published and delivered events is encoded in binary Apache Avro.
    3. This proto file example is based on the Pub/Sub API proto file, but we shortened it in this illustration. This proto file defines the service by listing the methods to publish, subscribe, get the schema, and get the topic information.