#Safe Harbor0 discussing

Our Lightning Article Editor Elevates the Authoring Experience to New Heights

I'm happy to announce that we are working on a completely new authoring experience for Knowledge Articles. Our current editor is the #1 recurring theme in feedback we hear from our customers, so that's why rebuilding our editing experience from the ground up is currently our highest priority. View the demo here!

Our goals with this new editor are to:

1. Improve the user experience for knowledge authors
2. Increase knowledge author productivity
3. Increase article quality with built-in tools
4. Enable collaboration between relevant stakeholders  

We aim to do this through a lightning-fast, user-friendly HTML5 editor that supports our customer's most-requested features, like a full-screen mode, seamless copy/pasting from external sources, advanced table support, and the option to export the field contents to PDF. We are also planning some advanced features like an accessibility checker (to quickly flag and fix WCAG violations in your article) and inline collaboration (in 2024).

We can't wait for you to get your hands on this new editor and hear your feedback. The Lightning Article Editor is currently planned for an open beta release in Summer '23.

Safe Harbor: This post contains information that is subject to change. Customers should make buying decisions only based on the products that are commercially available.

Hello SCV community!

Amazon put out a Amazon Connect Customer Advisory around the impact of Chrome third party cookies on authentication to Amazon Connect. It notes that agents will not be able to log into Connect in their custom agent application or CTI Adapter once 3P cookies are blocked.

We are using Service Cloud Voice with Amazon Connect and use Salesforce as the Identity Provider. Does anyone know if this will impact our agent login? Basically, wondering if we are in the 7% use case for agents that do not rely on 3P cookies for authentication. Thanks!

---

For context, here is the exact language from the email from Amazon I received:

Amazon Connect Customer Advisory - Impact of upcoming Google Chrome third party cookies 

Action Required:

 Google Chrome has announced an update that will begin impacting Amazon Connect customers in January 2024. We are proactively reaching out to partners like yourself to provide detailed guidance.

Google Chrome is aiming to begin blocking third party (3P) cookies (i.e., cookies passed between two top level domains) starting with 1% of Chrome users in Q1 2024 and dialing up to 100% in Q3. Approximately 93% of Amazon Connect users (agents/supervisors) rely on the use of 3P cookies for authentication, and those users will not be able to log into Connect in their custom agent application or CTI Adapter once 3P cookies are blocked. Standalone CCP and agent workspace experiences will not be affected.

We are addressing this issue by publishing an updated version of StreamsJS (i.e., our contact control panel APIs) and the Salesforce CTI Adapter, as well as guidance to our customers on how to upgrade their environments. By Jan 2024, if customers have rolled out an Enterprise policy which overrides 3P cookies from being disabled, there is no immediate action required. Otherwise, customers and partners will need to 1) enable an Enterprise policy or 2) upgrade their custom CCP, Customer Profiles, or Wisdom widget with the supported version of Streams and/or CTI Adapter (available late Sept and early Oct). Our recommended approach is for customers and partners to upgrade Streams and/or CTI Adapter. Once upgraded, it is anticipated agents will need to allow 3P cookies from Connect every 30 days. This upgrade will also address 3P cookies for Firefox and Edge.

We will be publishing additional information and implementation guide later this week along with explicit call to actions in late Sept. Please reach out to your AWS or Amazon Connect partner team if you have any questions on this. 

Hi everybody!

It's been more than our normal month between releases so I wanted to give an update and preview the next release.

While we were on an aggressive monthly release cadence since the product went GA in December, we are now starting to see reasons to slow down the cadence a bit. In this particular upcoming release we are making substantial and complex app updates that did not make sense to break up into separate releases, so I decided to delay the monthly cadence to allow the work to mature more. I currently anticipate that this release will ship on August 26. Once this release ships we will most likely shift into a cadence typified by releasing new modules** when they are ready, instead of packaging lots of smaller core-app changes.

So what are we doing in this release? Well, honestly, a huge amount. Here's a preview:

• New global electricity emissions factors from electricityMap (https://api.electricitymap.org) which I am very, very excited for. This is IEA data +++ and it's far more granular than IEA data for a variety of countries (for instance, it splits Japan into 9 grid subregions).
• Building a way for any user to add in 'supplemental' Scope 1, 2 and 3 data into any Energy Use Record or Carbon Footprint record. Now you will be able to add a custom calculation, use a process or flow to insert the results into one of the new supplemental fields, and have the value roll up into the total results.
• A total restructuring of the four business travel scope 3 record types. This affects both the Energy Use Record and the Emissions Factor objects. We are building in new flexibility on units, currency and calculations. For example, on Air Travel records, now you'll be able to define your own definition of short, medium and long-haul flights, you'll enter data in miles or km, and the EA dashboards will show results in either unit. Similar changes are being made for Ground Travel, Hotel Stays and Rental Cars. 
• A re-build of the way renewable energy was being handled. All RE calcs now include hydroelectricity, and we've added a large set of new fields to show RE without hydro. You will choose which fields to show on your page layouts to adhere to how your organization accounts for RE. (For example, Salesforce does not factor hydro into our RE calcs, but most companies do.)
• New record-locking functionality to protect records from edits or future package updates. For instance, you've finished the 2018 inventory? Lock those Carbon Footprint records and they will not be touched by any future package upgrade, even if we change fields or add new emissions factor data.
• Moving 20+ fields from formula fields to apex-calculated fields. This makes the app much more efficient and predictable. Yes, I understand, declarative admins much prefer formula fields. The problem is that when you have a mix of formula and apex fields, you can have unpredictable results in the view state in Lighting Experience when a user views a record (because the formula field will update but the overall record will not). 
• A long list of small updates to the Einstein Analytics dashboards to keep up with the changes above, and other changes we're making.

That's not all, but probably enough for a preview. :)

**New modules??? Oh yes! We are currently working on a Data Gap Filling module that will be a huge addition to the product (shipping Sept. I hope -- #SafeHarbor), as well as a way to estimate your supply chain scope 3 emissions (shipping Oct. I hope -- #SafeHarbor), which will be even huger! More to come.....

Is SEO for the AppExchange supposed to work like this?

Steps to repo;

1. Search for 'Events by Salesforce Labs' in Google
2. Find a result for the desired app

3. Press on the Result

Expected Result: You are taken to the App Page; 

eg. https://appexchange.salesforce.com/listingDetail?listingId=a0N30000005vK3CEAU&tab=e

Actual Result: You can taken to the CTA Tab of the App which loads the Demo Video in full screen 

eg.  https://appexchange.salesforce.com/appxListingDetail?listingId=a0N30000005vK3CEAU&tab=e&cta=demo

This means to actual get 'back' to the App listing itself you have to remove from the URL

&cta=demo

If you use the x from the video screen you just get a blank page with no content or navigation options.