![\"\"](\"https:\/\/d259t2jj6zp7qm.cloudfront.net\/images\/20191119110921\/evergreen-blog-image-gradient-e1574186986199.png\")
\n\t\t\t <\/span>\n\t\t\tDelightful and cohesive digital experiences make for happy customers, partners and employees, and building those modern experiences requires direct and seamless access to Customer 360 data and business logic. That\u2019s why we\u2019re excited to announce Salesforce Evergreen \u2014 a new addition to the Customer 360 Platform that brings in serverless functions based on fully-managed Kubernetes, support for open programming languages and commonly used high-performance data stores. Evergreen is the best way to build the deep and engaging digital experiences that your customers have come to expect.<\/p>\nEvergreen supports technologies and architectural patterns that make development teams productive and happy:<\/p>\n
- \n
- Functions-as-a-Service<\/b> for writing business logic and event processing in languages like Node.js, Java and Apex, using the full power of those languages\u2019 package ecosystems. Functions can be triggered directly from Apex or using Platform Events, with many more invocation types and event sources to come.<\/li>\n
- Microservices<\/b> for building serverless HTTP apps and APIs that can be quickly evolved by small agile teams and composed into complex, engaging digital experiences. Services and functions are serverless, consume no resources when idle and automatically and elastically scale with traffic.<\/li>\n
- Managed data stores<\/b> like Postgres, Apache Kafka and Redis that complement the Salesforce Data APIs for high-performance persistence and real-time eventing.<\/li>\n<\/ul>\n
As an industry first, these features come with built-in customer context, driven by the Salesforce data model and low-code components. Evergreen is a seamless part of the Salesforce platform and no extra authentication or networking setup is required. For example, developers can invoke functions directly from Apex, run logic with org-context and query and write-back updates.<\/p>\n
\n\t\t\t \n\t\t\t
![\"\"](\"https:\/\/d259t2jj6zp7qm.cloudfront.net\/images\/20191121175241\/02-v11-1.png\")
\n\t\t\t <\/span>\n\t\t\t<\/p>\n<\/p>\n
Evergreen is based on Kubernetes and balances control and access to scalable container technology by providing a fully managed serverless service operated by Salesforce. This service lets you focus more on innovation rather than infrastructure operations. Evergreen opens Salesforce development to any development team because apps, functions and services can be built using common open languages, tools and technologies.<\/p>\n
At the Dreamforce 2019 Developer Keynote<\/a>, we showcased how Salesforce customers like Caesars Entertainment can build a modern guest check-in experience using Evergreen. In the keynote demo, the Lightning Platform is used to quickly create an employee-facing iOS app for managing housekeeping and room-readiness and that is seamlessly extended with event-driven functions running on Evergreen. When housekeeping marks a room as ready using the employee app, a platform event triggers a Node.js function that uses guest-context to send a tailored real-time notification letting the guest know that the room is ready for early check-in.<\/p>\n
At the end of the stay, the Salesforce Flow powering the guest checkout can call out to a different function with invoicing details. The Node.js function can use the invoice details and an npm PDF module to quickly generate a bill. Here\u2019s the sample function that receives the request as a CloudEvent<\/a> fetches additional data, generates a PDF and adds a link to the PDF from the guest booking record:<\/p>\n
import { UnitOfWork, SObject } from '@salesforce\/functions';\r\nimport { PDFDocument } from 'pdfkit';\r\nimport * as fs from 'fs';\r\n\r\nmodule.exports = async function(event, context, logger) {\r\n const folioPayload = event.payload;\r\n\r\n \/\/ Creating a new Unit Of Work instance\r\n const uow = UnitOfWork;\r\n\r\n \/\/ Run SOQL query to fetch folio data\r\n const query = `SELECT Id, Description__c, Amount__c, Date__c FROM Booking_LineItems__c WHERE Reservation__c = \r\n '${folioPayload.recordId}'`;\r\n const folioLineItems = await context.sfApi.query(query);\r\n\r\n \/\/ Call function to generate PDF and store in external data store\r\n \/\/ for Files Connect\r\n const pdfFilesConnect = await generatePdf(\r\n folioPayload.recordId,\r\n folioLineItems\r\n );\r\n\r\n \/\/ Update the booking object\r\n const ReservationObject = new SObject('Reservation__c');\r\n ReservationObject.Id = folioPayload.recordId;\r\n ReservationObject.Status__c = 'Paid and Folio created';\r\n uow.registerModified(ReservationObject);\r\n\r\n \/\/ Update data\r\n uow.commit();\r\n};\r\n\r\nasync function generatePdf(id, lineItems) {\r\n # generate and store folio PDF\r\n}<\/pre>\nFunctions running on Evergreen idle when not in use and automatically scale to handle any invocation load or event throughput. Functions are easy to build from source with Cloud Native Buildpacks<\/a> and developers are free to use any supported programming language and to pull in any package or library that\u2019s going to help them get their job done.<\/p>\n
Evergreen is the latest addition to the Salesforce Platform, combining Heroku\u2019s decade-long experience building scalable container runtimes and high-performance data stores with Lightning tools and features. The unique combination of serverless, elastic container technology and seamless access to customer data and low-code business logic makes Salesforce the obvious place to build and run the differentiated digital experiences that impress your customers, partners and employees.<\/p>\n
A limited access developer preview of Evergreen will be available with the Spring \u201920 release in February. Sign up to get Evergreen updates<\/a>. You can also watch the Dreamforce Developer Keynote recording<\/a> to see an Evergreen demo. If you\u2019re joining us on-site at #DF19, drop by the Dreamforce Evergreen booth at Platform Park in the Trailhead area (At Moscone West) to learn more, or join us for these Evergreen-focused Dreamforce breakout sessions:<\/p>\n
- \n
- Build More on the Salesforce Platform with Evergreen Functions: An Elastic Runtime for Node.js<\/a> – Wed, Nov 20, (2:30-2:50pm), Moscone West (Surfside Theater)<\/li>\n
- Salesforce Evergreen and Evergreen Functions: Build evented serverless consumer apps<\/a> – Thurs, Nov 21 (3-3:40pm), Moscone West (Room 2007)<\/li>\n
- Evented enterprise app architectures with Salesforce Evergreen and Evergreen Functions<\/a> – Thurs, Nov 21 (5-5:40pm), Moscone West (Room 2024)<\/li>\n
- Salesforce Evergreen and Evergreen Functions: Build evented serverless consumer apps<\/a> – Fri, Nov 22, (12-12:40pm), Moscone West (Surfside Theater)<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
Delightful and cohesive digital experiences make for happy customers, partners and employees, and building those modern experiences requires direct and seamless access to Customer 360 data and business logic. That\u2019s why we\u2019re excited to announce Salesforce Evergreen \u2014 a new addition to the Customer 360 Platform that brings in serverless functions based on fully-managed […]<\/p>\n","protected":false},"author":3537,"featured_media":192838,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2489,2530],"tags":[2674,2662,2288,2655,2661,2663],"coauthors":[],"class_list":["post-192806","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-announcements","category-data-cloud","tag-customer-360-platform","tag-functions","tag-microservices","tag-november-2019","tag-salesforce-evergreen","tag-serverless"],"podcast_audio":{"audio_url":"","duration":""},"featured_image":"https:\/\/d259t2jj6zp7qm.cloudfront.net\/images\/20191115174440\/trailhead_module_salesforce_platform_basics.png?w=200","related_posts":[{"post":{"ID":203077,"post_author":"3557","post_date":"2024-09-03 09:30:24","post_date_gmt":"2024-09-03 15:30:24","post_content":"The Winter \u201925 release<\/a> starts rolling out to your sandbox and production environments from September through October 2024. Get ready \u2014 this release is packed with product updates and new features that will enhance your development experience. Whether you're looking to add AI capabilities to your business, build a solid data foundation on Data Cloud, or work with platform features, you'll find some significant new capabilities in this release.\r\n\r\nLet\u2019s take a look at the highlights for developers.\r\n
Apex enhancements<\/h2>\r\n
Preventing collection modification during iteration in Apex<\/h3>\r\nIn Apex, modifying a set while iterating over it used to be allowed before API version 61.0 (Summer \u201924). However, this often led to unpredictable issues, like the iteration might skip elements, process elements multiple times, or throw an error. To prevent these problems, starting from API version 62.0, Apex now restricts these actions. Attempting to modify a set during iteration throws a \u201cSystem.FinalException: Cannot modify a collection while it is being iterated\u201d<\/b> <\/b>exception. This change ensures more reliable and consistent code execution.\r\n
Set<String> names = new Set<String>{'Alice', 'Bob', 'Charlie'}; \r\n for (String name : names) { \u00a0 \r\n if (name.startsWith('A')) {\r\n names.remove(name); \/\/ This throws a System.FinalException in API v62.0 \u00a0 \u00a0 \r\n } \r\n}<\/pre>\r\nImproved error messages for invalid SOQL<\/h3>\r\nWe now provide much more user-friendly error messages for invalid dynamic SOQL and SOQL issued via APIs. Go through the <\/span>list of error message changes <\/a>and be sure to update any code that depends on old SOQL error messages. <\/span>\r\n
Support for negative currency values in dynamic SOQL<\/h3>\r\nWe also now support negative currency values in dynamic SOQL queries and queries executed via APIs. Below is an example query that previously would have errored out, but now works in dynamic Apex and via APIs. Note that this is still unsupported if you are writing a static SOQL.\r\n\r\nThe code snippet below now works if you have orgs with MultiCurrency enabled.\r\n
System.debug(Database.query(SELECT Amount FROM Opportunity WHERE Amount < USD-5000));\r\n<\/pre>\r\n
Track Apex Unexpected Exceptions with free-tier Event Monitoring<\/h3>\r\nWe notify you of unhandled exceptions via email. However, there's a limit of 10 emails per hour per application server, which is shared across multiple orgs. Due to this limit, you might not always receive these emails. To address this, we are offering a free tier of Event Monitoring<\/a> in this release, providing access to Apex Unexpected Exception event logs. You can now troubleshoot your Apex code by analyzing the information captured in the event log files for the Apex Unexpected Exception event type<\/a>.\r\n\r\nYou can download the CSV file to uncover the error using the event browser, as shown in the screenshot below. Turn on Event Monitoring for your orgs to discover the logs.\r\n\r\n
![\"Image](\"https:\/\/developer.salesforce.com\/blogs\/wp-content\/uploads\/2024\/09\/Screenshot-2024-08-21-at-1.13.14\u202fPM-2000x804.png\")
\r\n\r\nAdditionally, we now ensure that exceptions triggered by transactions with entry points, such as @AuraEnabled<\/code>,@RestResource<\/code>, and@InvocableAction<\/code> annotations are captured in the Apex Unexpected Exception event type.\r\nMock SOQL tests for external objects<\/h3>\r\nYou can mock SOQL query responses for external objects in Apex testing using SOQL stub methods and a new test class. Look at the <\/span>example code<\/a> to learn how to extend the new
system.SoqlStubProvider<\/code> class and override thehandleSoqlQuery()<\/code> class method. <\/span>\r\nLWC enhancements<\/h2>\r\n
Develop LWC faster with Local Dev (Beta)<\/h3>\r\nLocal Dev (Beta) is now available in Winter \u201925 sandboxes and scratch orgs for now. It allows you to preview your LWC instantly as you code \u2014 there is no need for page refreshes or reloads. We use hot module reloading and WebSockets to let you locally preview your LWC for LWR sites, mobile apps, and the Lightning Experience. To learn how to set up tooling and work with this feature, check out the documentation<\/a>.\r\n
LWC API version 62.0 updates<\/h3>\r\nWith API version 62.0, we are bringing much-needed enhancements to LWC. You will need to update a component's API version in its
.js-meta.xml<\/code> file to update the component version. Note that the features below work only if your LWC component version is 62.0 or above.\r\nClass object bindings for managing styles<\/h3>\r\nIn LWC API version 62.0 and later, you can provide multiple classes on an element with a JavaScript array or object. By using class object binding, you no longer have to concatenate strings to pass in multiple classes.<\/span>\r\n\r\nHere is an example code showing class object bindings <\/span>in action. Let\u2019s say you have a button component with the HTML markup below:\r\n
<div class={computedClassNames}>Evaluate some classes here<\/div>\r\n<\/pre>\r\nAnd below is a JavaScript class that returns thecomputedClassNames<\/code> as arrays with object types.\r\nimport { LightningElement } from \"lwc\";\r\n\r\nexport default class extends LightningElement {\r\n position = \"left\";\r\n fullWidth = true;\r\n hidden = false;\r\n\r\n get computedClassNames() {\r\n return [\r\n \"div__block\",\r\n this.position && `div_${this.position}`,\r\n {\r\n \"div_full-width\": this.fullWidth,\r\n hidden: this.hidden,\r\n },\r\n ];\r\n }\r\n}\r\n<\/pre>\r\nThe above code would render the HTML as below with 62.0 and beyond.\r\n<div class='div__block div_left div_full-width'>\r\n Evaluate some classes here\r\n<\/div>\r\n<\/pre>\r\nIn version 61.0, this would render as below:\r\n
<div class='div__icon,div_left,[object Object]'>\r\n Evaluate some classes here\r\n<\/div>\r\n<\/pre>\r\nThe docs provide a <\/span>handy table<\/a> showing how class bindings render in API version 62.0 and beyond vs. 61.0 with different data types.<\/span>\r\nNew <\/span>
this.style<\/code> <\/span>property<\/h3>\r\nStarting with version 62.0, you can access a component's hostCSSStyleDeclaration<\/code> (see docs<\/a>) directly usingthis.style<\/code>, regardless of whether you're using light DOM or shadow DOM. In earlier versions (61.0 and before), you had to usethis.children[0].parentElement.style<\/code> for light DOM andthis.template.host.style<\/code> for shadow DOM. With 62.0,this.style<\/code> simplifies this process. Here's an example component showing how to set the style using this new property.\r\nimport { LightningElement } from \"lwc\";\r\n\r\nexport default class extends LightningElement {\r\n static renderMode = \"light\"; \/\/ default is 'shadow'\r\n\r\n setStyle() {\r\n this.style.setProperty('color', 'red');\r\n this.style.setProperty('border', '1px solid eee');\r\n console.log(this.style.color); \/\/ logs \"red\"\r\n }\r\n \r\n renderedCallback() {\r\n this.style.color = 'red';\r\n }\r\n}\r\n<\/pre>\r\nNew <\/span>
this.hostElement<\/code> <\/span>property<\/h3>\r\nIn LWC API version 62.0 and later, you can access the parent element using <\/span>this.hostElement<\/span><\/code> in a <\/span>renderedCallback<\/span><\/code> or in another callback. This is a convenient syntax for<\/span> <\/span>this.template.host<\/code> in shadow DOM that now works with light DOM too. Here is an example showing the usage ofthis.hostElement<\/code>:<\/span>\r\n\/\/ c-light\r\nimport { LightningElement } from \"lwc\";\r\n\r\nexport default class extends LightningElement {\r\n static renderMode = \"light\"; \/\/ default is 'shadow'\r\n\r\n renderedCallback() {\r\n console.log(this.hostElement); \/\/ logs \r\n console.log(this.hostElement.tagName); \/\/ logs C-LIGHT\r\n }\r\n}\r\n<\/pre>\r\nUpgrade your ESLint dependencies to prevent deployment-time issues<\/h3>\r\nIn LWC API version 62.0 and later, there are strict rules for exports and imports. We allow only named imports and exports going forward. Below are some export and import statements that are not allowed anymore.<\/span>\r\n
\/\/ Don\u2019t do this\r\nimport 'lwc';\r\nexport * as lwc from 'lwc';\r\nexport {} from 'lwc';\r\nexport { privateFunction } from 'lwc';\r\n<\/pre>\r\nGraphQL wire adapter is now supported in Experience Cloud sites<\/h3>\r\nThe GraphQL wire adapter
lightning\/uiGraphQLApi<\/code> is also now supported in LWCs built for Experience Cloud LWR sites. Check out LWC Recipes<\/a> to learn how to build withlightning\/uiGraphQLApi<\/code>.\r\nManage list views with new Lightning Web Component (LWC) wire adapters<\/h3>\r\nList views render faster with this release, thanks to the LWCs. We have moved list views from Aura to LWC, and we want to share this love with all developers. Working with the list views is easier with new wire adapters added to
lightning\/uiListsApi<\/code> (see docs<\/a>). You can get a list view's record data and update a list view's preferences. You can also get the list views associated with an object, or the metadata for a list view object. To explore more, check out the new adapters listed in the release notes<\/a>.\r\nSupport for Event objects in form base components<\/h3>\r\n
lightning-record-form<\/span><\/code>, <\/span><\/b>lightning-record-edit-form<\/code>,<\/span> <\/span><\/b>and <\/b>lightning-record-view-form<\/code> <\/b>LWC base components now support Event objects. You can read more in the <\/span>docs<\/a>.<\/span>\r\nOther miscellaneous updates<\/h3>\r\n
- \r\n \t
- We now allow components with larger JavaScript files. The previous limit was 128KB, and we now support up to 1MB for JavaScript bundles.<\/span><\/li>\r\n \t
- We improved accessibility for base components<\/a> like
lightning-input<\/code>.<\/li>\r\n \t- Lightning Web Security auto enablement<\/a> is postponed for now as we heard customers need more time.<\/li>\r\n \t
- Enabling and disabling LWS distortions can give you further insights into your component. Read the <\/span>docs<\/a> to learn how to use your browser console to do this. Additionally, <\/span>new distortions<\/a> are added with the Winter \u201925 release.<\/span><\/li>\r\n \t
- In Winter \u201925, additional components were adapted to prepare for native shadow DOM<\/a>. This may affect your UI tests. If you use the UI Test Automation Model (UTAM) for your UI tests, make sure to update to get the latest UTAM Page Objects.<\/li>\r\n<\/ul>\r\n
TypeScript support for LWC (Developer Preview)<\/h3>\r\nAre you a TypeScript<\/a> lover? Starting in Winter \u201925, you can author your LWC components using TypeScript. Instead of JavaScript, you\u2019ll build your code in TypeScript and run the TypeScript compiler to compile a JavaScript file. Below is an example component build using TypeScript with types.<\/span>\r\n
import { LightningElement, track } from 'lwc';\r\n\r\nexport default class DynamicButton extends LightningElement {\r\n @track variant: string = 'primary';\r\n @track position: string = 'right';\r\n @track fullWidth: boolean = false;\r\n @track disabled: boolean = false;\r\n @track showTooltip: boolean = false;\r\n @track icon: string = 'utility:check';\r\n\r\n get computedClassNames(): (string | { [key: string]: boolean })[] {\r\n return [\r\n 'button',\r\n `button_${this.variant}`,\r\n `button_${this.position}`,\r\n {\r\n 'button_full-width': this.fullWidth,\r\n 'button_disabled': this.disabled,\r\n 'button_with-icon': Boolean(this.icon),\r\n }\r\n ];\r\n }\r\n\r\n get tooltipClass(): string {\r\n return this.showTooltip ? 'tooltip tooltip_visible' : 'tooltip';\r\n }\r\n\r\n handleToggle(): void {\r\n this.variant = this.variant === 'primary' ? 'secondary' : 'primary';\r\n this.icon = this.icon === 'utility:check' ? 'utility:close' : 'utility:check';\r\n }\r\n\r\n handleMouseEnter(): void {\r\n this.showTooltip = true;\r\n }\r\n\r\n handleMouseLeave(): void {\r\n this.showTooltip = false;\r\n }\r\n}\r\n<\/pre>\r\nThis feature is in Developer Preview, and we want to hear your feedback via the <\/span>Trailblazer Community<\/a>. Check out the <\/span>docs<\/a> and let us know about your experience as we bring these features to production.<\/span>\r\nData Cloud release highlights<\/h2>\r\n
Data Cloud sandboxes (Beta)<\/h3>\r\nData Cloud sandboxes are now available in Beta. The docs<\/a> explain which features of Data Cloud these sandboxes support.\r\n
Vector search and hybrid search in Data Cloud<\/h3>\r\nYou can bring unstructured data into Data Cloud and create a search index for vector and hybrid search. Vector search produces semantically aware query results, while hybrid search combines vector search with keyword search to handle domain vocabulary and provide users with the most relevant results.\r\n\r\nYou can run vector search queries using <\/span>Query API<\/a>. This feature was released as a part of the August 2024 release. Below is an example query for all similar cases with the subject \u201cline power failure\u201d from unstructured case comments vectorized and indexed in Data Cloud.<\/span>\r\n
SELECT\r\n v.score__c, c.SourceRecordId__c\r\nFROM \r\n vector_search(table(CaseComments_index__dlm), 'power failure', '', 10) v\r\n JOIN CaseComments_chunk__dlm c ON v.RecordId__c = c.RecordId__c\r\n JOIN CaseComments__dlm casecomment on c.SourceRecordId__c = casecomment.Id__c\r\nORDER BY 1 DESC\r\n<\/pre>\r\n
Retrieval Augmented Generation (RAG) in Data Cloud<\/h3>\r\nRetrieval Augmented Generation (RAG)<\/a> is now available in Data Cloud, enabling AI models to generate more accurate and contextually relevant responses by leveraging unstructured data. With RAG, you can ground AI prompts using data sources like call notes, emails, video transcripts, and knowledge bases. This means that when Einstein AI generates a response, it can retrieve and incorporate relevant information from these unstructured data sources, making the responses more precise and aligned with your specific context, thus improving the response quality.<\/span>\r\n\r\nWe also provide capabilities to <\/span>manage retrievers<\/a> now. A retriever returns relevant facts from textual data \u2014 which is indexed in the vector database \u2014 to augment a large language model (LLM) prompt. By augmenting prompts with accurate, current, and pertinent information, retrievers improve the value and relevance of LLM responses for users. Note that the RAG and retrievers were released as part of the August 2024 release. To learn more about how to use RAG with Data Cloud, refer to the <\/span>documentation<\/a>. <\/span>\r\n
Lock and protect your custom metadata in a data kit<\/h3>\r\nData kits are how you package metadata for Data Cloud. You can now lock custom metadata in a data kit to prevent your subscribers from modifying it. This feature will be available in September.\r\n
Establish dependency between Data Cloud packages and Salesforce Platform packages<\/h3>\r\nWhile a managed package can't contain a mix of Data Cloud and other metadata in a single package, you can now create separate packages with dependencies in your orgs. We will provide more info on how to do this in September.\r\n
Cross-cloud Data Cloud updates<\/h3>\r\nA number of cross-cloud updates are coming in the Winter '25 release. Refer to the <\/span>release notes<\/a> to explore these features like support for <\/span>more events capture from Experience cloud sites to Data Cloud integration<\/a> and support for<\/span> unified knowledge<\/a> in Data Cloud for service cloud use cases. These features become available as part of the September release.<\/span>\r\n
Agentforce features<\/h2>\r\nAgentforce is Salesforce's portfolio of AI agent technologies. In the Winter '25 release, we are launching Agentforce Agents, which are AI systems that can understand user inputs and take actions to accomplish a goal autonomously using Salesforce Platform capabilities. Agentforce provides developers with tools and capabilities for building Agentforce Agents and Einstein Copilots on the Salesforce Platform.<\/span>\r\n
Agentforce Agents<\/h3>\r\nAgentforce Agents<\/a> can understand inputs, plan tasks to accomplish a goal using LLMs, and take actions using Salesforce Platform capabilities to complete tasks autonomously. They come in two types: <\/span>Einstein Copilots<\/a> <\/span>(an assistive type of agent, already available since Spring \u201924),<\/span> which assist humans collaboratively, and fully autonomous Agentforce A<\/span>gents<\/span> (available in Winter \u201925 ) that work independently with safety measures in place and can hand off a task to humans when needed.<\/span><\/span>\r\n\r\nIn Winter \u201925, we will release pre-built agent templates shipped by Salesforce to address various jobs across Sales, Service, Commerce, and many others, with pre-configured roles, topics, and actions. You can customize these using Agent Builder (formerly known as Copilot Builder).<\/span>\r\n
Agent Builder updates<\/span><\/b><\/h3>\r\nCopilot Builder is now Agent Builder. With Agent Builder, you can customize out-of-the-box<\/span> <\/span>Agentforce A<\/span>gents<\/span> and copilots by defining topics and actions using prompts, flows, and Apex. This also includes the Advanced Planner, which is used to test the agent\u2019s responses and plan of action. We will have more enablement sessions and content for you at <\/span>Dreamforce<\/a>.<\/span>\r\n<\/span>\r\n
Introducing topics in Agent Builder<\/h3>\r\nBuilding copilots and agents is about to become even more efficient with the introduction of topics<\/a>. When a user enters a question or request, instead of going through a list of all actions, the agent will now select a relevant topic and then launch one or more actions included within that topic. This enhancement will significantly improve the agent\u2019s decision-making process, making it more accurate and generating more relevant, predictable responses. To learn how to build topics to group your actions, check out the documentation<\/a>.\r\n<\/span>\r\n
Advanced Planner<\/h3>\r\nWith the introduction of topics, we've enhanced the planner service in Einstein Copilot and Agentforce Agents. Rather than generating a single plan based on a user request, the new advanced planner now empowers your copilots and agents to make more frequent, iterative decisions that continuously adapt to user input. This reactive and dynamic approach not only increases the frequency of decision-making, but it also significantly enhances the accuracy of responses, instilling greater confidence in the copilot's or agent's ability to guide you effectively.\r\n<\/span>\r\n
Models API (Beta)<\/h3>\r\nThe <\/span>Models API (Beta) <\/a>provides Apex classes and REST endpoints that connect your application to large language models (LLMs) from Salesforce partners, including Anthropic, Google, and OpenAI. These APIs became available in July. <\/span><\/span>\r\n\r\nTo learn more about working with the Models API, watch our video <\/a>and explore these APIs using the Salesforce Postman Collection<\/a>. In the upcoming Winter release, we plan (safe harbor) to bring this to GA.\r\n
Platform development tools<\/h2>\r\n
Einstein for Developers (Beta) updates<\/h3>\r\nIntroducing our all-new Dev Assistant (Beta<\/a>), part of Einstein for Developers (Beta)! With Dev Assistant (Beta), you can now ask Einstein to explain the code, provide instructions for Apex and LWC code suggestions, explain and document code, and request suggestions for code fixes. We are also using Retrieval Augmented Generation (RAG) to give you a response that is contextualized with your org\u2019s metadata. You can learn more about the new Dev Assistant at Dreamforce 2024<\/a>. <\/span>\r\n
Salesforce CLI updates<\/span><\/h3>\r\nThe Salesforce CLI receives updates every week. Check the Salesforce CLI <\/span>release notes<\/a> weekly for helpful updates. Recent major improvements include:<\/span>\r\n
- \r\n \t
- You can now export up to five levels of child objects in a query when using <\/span>
data export tree --plan<\/code>.<\/li>\r\n \t- The <\/span>
data import tree --plan<\/code> <\/span>command can now handle files that contain more than 200 records.<\/li>\r\n \t- When you run <\/span>
data import tree<\/code> <\/span>with the <\/span>--file<\/code> <\/span>flag, the command uses parallel uploads, which improves performance.<\/li>\r\n \t- There is a new command for uploading files<\/span>. Here is an example command that shows how to upload a file and relate to a parent object via the CLI
sf data create file --file astro.png --title Astro.png --parent-id a03fakePIA3<\/code>.<\/li>\r\n \t- We have made Salesforce CLI installation faster.<\/span><\/li>\r\n \t
- There is also a new beta <\/span>command <\/span>
api request rest<\/code> to send REST calls to your org.<\/span><\/li>\r\n<\/ul>\r\nSalesforce Code Analyzer<\/h3>\r\nThe Code Analyzer VS Code extension is now generally available and bundled with the Salesforce Extension Pack (expanded<\/a>). Code Analyzer scans your code using multiple rules engines to produce lists of violations that you can use to improve your code. You can use Code Analyzer with the Salesforce CLI as well.<\/span>\r\n
APIs and integrations<\/h2>\r\n
- \r\n \t
- You can now process platform events in parallel in Apex triggers. The <\/span>documentation<\/a> explains how this works, how to implement this in Apex, and how to configure the partition settings.<\/span><\/li>\r\n \t
- Remember to update the<\/span> instanced URLs<\/a> in your API calls to your My Domain login URL before October 12, 2024. <\/span><\/li>\r\n \t
- The <\/span>
- We improved accessibility for base components<\/a> like
- Salesforce Evergreen and Evergreen Functions: Build evented serverless consumer apps<\/a> – Thurs, Nov 21 (3-3:40pm), Moscone West (Room 2007)<\/li>\n
- Microservices<\/b> for building serverless HTTP apps and APIs that can be quickly evolved by small agile teams and composed into complex, engaging digital experiences. Services and functions are serverless, consume no resources when idle and automatically and elastically scale with traffic.<\/li>\n