Winter '24 Abridged

• DevOrgs
  no

  longer support sms authentication

, using U2F seems to be the easiest way for devs to go forward if you have tons of orgs. External Client App are basically connected apps but packageable and deployable, seem to now be available LWC now support Dynamic Imports, which TL;DR lets data drive which component to use. Note the performance overhead indicated in the notes, because… The LWC Workspace API allows you to programmatically open, close, refresh, and otherwise modify tabs in a Console environement. LWS virtualizes CustomElementRegistry, which ties to your ability to use Third Party Web Components (with heavy limitations, etween EcAMScript exclusions and Experience builder exclusions), but does in fact highlight a future of heavy customizations Custom Property Editors now available for non-LWR sites Component-Level API Versioning now allows you to have more tech debt instead of properly using release cycles or Release Updates. Bad Admins rejoice. Event Monitoring now follows Insufficient Access cases, but only for account, case, contact, and opportunity. Salesforce does love Object-specific development. EM also gets Component Level Monitoring which is nice due to the other releases The usual Web Standards changes lead to DOM Structures changing CSS scope tokens change formats, querying them now preferable via template refs. LWC Offline gets NFC Readability, and Biometrics Integration. As long as we’re about Offline, you can now attach images to records and search for records offline on Mobile. You can now set Queuable Max Depth and delay via the new System.enqueueJob()overload, and also set a Queuable Duplicate Signature allowing you to better avoid eating up all your DailyAsyncExecutions limit APEX logging is slightly better but you still should use nebula logger Events get relays on Hyperforce Salesforce Ids don’t change Length but do have minor structure change with serverId going from 2 to 3 characters, taking one of the “previously reserved” characters UTAM (Or UI Test Automation Model if you don’t remember every single SF Acronym) gets a few QoL Updates, I’m just re-highlighting that the entire concept exists. LWR Sites get defaulted to enhanced because CMS Contentis available in Enhanced, get component variations and better visibility rules, admin-suitable css update powers (and better global CSShandling, an action bar, dynamic redirects, better static resource protection. The most interstnigintersting one is Record Detail Component coming in - this is the first time I’m sensing a proximity to “hey we might replace all Aura sites soon with LWR”. If you don’t know what all this means “Salesforce has, in roughly a year, built out a brand new Framework that should allow much better Experience management and thrid-third-party compatibility thanks to the Web Components standard, and you should see first impact in roughly another 6 months IMO.” If you can’t use LWR, you can now still use refreshView via LockerService Headless Authentication gets udpates that make it easier to leverage it or set it up Domain addition in SF now does more checks with better error messages (but also make adding a domain harder if you don’t know wtf you’re doing) You write shit html code, it won’t work no more. sadge. You write shit http headers, also sadge no more worky.