IdeaExchange

Hi Team, 

I would like to submit an idea request regarding the Outlook Integration for Salesforce. 

Currently, when creating an Event in Salesforce and selecting the All Day Event

option, the system automatically pre-fills the Start Date and End Date fields, providing a seamless user experience. However, this behavior is not available in the Outlook plug-in. 

On behalf some of the users who has noticed this, we would like to request an enhancement to automatically prefill the Start Date and End Date (or corresponding all-day event timing fields) when a user selects All Day Event

within the Outlook plug-in. 

This improvement would provide several benefits:

• Ensure a consistent user experience between Salesforce and the Outlook plug-in.
• Reduce manual data entry and save time for users creating all-day events.
• Minimize the risk of incorrect or incomplete event dates being entered.
• Align event creation behavior across Salesforce platforms and integrations.

We would appreciate any information regarding the feasibility of this enhancement and whether it could be considered for inclusion in a future release.

Thank You

💻 Recap of True to the Core Deep Dive: Lightning Design System 2 (SLDS 2)  

Thank you to everyone who joined True to the Core Deep Dive today, and to Salesforce Product Managers @Adam Doti, @Cliff Seal, and @Fiona Tang for sharing updates and answering your questions on SLDS 2. 

🎥 Missed the session? 

You can watch the full session on demand here. 

💬 Still have questions? 

Drop them in the comments below. We’ll do our best to get you answers! 

📝 Vote on future TTTC Deep Dive topics! 

Please take a moment to fill out this quick survey here to help shape future sessions. 

🔗 Resources shared during the session: 

🔹 Blog: The Admin Guide to Preparing Your Org for Dark Mode with SLDS 2

🔹 SLDS Linter Information

🔹 Design Systems on the RoadmapExchange

🔹 Trailhead Module: Dark Mode in SLDS 2: Quick Look

Have feedback on SLDS 2? Complete this survey to join the Salesforce Research Program and participate in SLDS 2 research. #True To The Core @IdeaExchange #AwesomeAdmins #Salesforce Developer #Architects #DreamDesigners #DesignersMind

@Salesforce Admins Live Sessions, @* Release Readiness Trailblazers *, @* Salesforce Platform *, @* Trailhead Official *, @Trailblazer Community Cove, @Admin Addicts, @* Salesforce Developers *, @TDX for Admins, @Architect Trailblazers

💬 Have a question about DevOps Center? Bring it to our next True to the Core Deep Dive on June 16. 

Join Salesforce product experts @John Belo, @Gilson Canario, @Karen Fidelak, and @Srikrishna Padmannagari for a Q&A-focused conversation on the future of Salesforce DevOps and what it means for admins. 

Here’s what you can expect: 

💬 Open Q&A with Salesforce product experts 

🚀 Insight into upcoming features and enhanced delivery experiences 

⚙️ Practical guidance for evolving your deployment strategy 

💡 A chance to share feedback directly with the product team 

➡️ RSVP and join the conversation. ⬅️ #True To The Core @IdeaExchange #AwesomeAdmins #Salesforce Developer #Architects

@Salesforce Admins Live Sessions, @* Release Readiness Trailblazers *, @* Salesforce Platform *, @* Trailhead Official *, @Trailblazer Community Cove, @Admin Addicts, @* Salesforce Developers *@TDX for Admins, @Architect Trailblazers

⚙️ That DevOps question you've been meaning to ask? Save it for June 16. 

One week from today, we're bringing together Salesforce product experts @John Belo, @Gilson Canario, @Karen Fidelak and @Srikrishna Padmannagari for a True to the Core Deep Dive with plenty of time for live Q&A. 

➡️ RSVP and join the conversation. ⬅️ #True To The Core @IdeaExchange #AwesomeAdmins #Salesforce Developer #Architects

@Salesforce Admins Live Sessions, @* Release Readiness Trailblazers *, @* Salesforce Platform *, @* Trailhead Official *, @Trailblazer Community Cove, @Admin Addicts, @* Salesforce Developers *@TDX for Admins, @Architect Trailblazers

Idea/Suggestion

Activity-Level Timing & Count Visibility in Automations: 

It would be highly beneficial to have detailed timing and record count visibility for each activity within an automation. 

Proposed Feature: 

For every activity in an automation: 

Display Start Time 

Display End Time 

Show Number of records processed 

Suggested UI Behavior: 

When hovering over an activity, a tooltip or popup should display: 

Start time of the activity 

End time of the activity 

Total records processed by that activity 

Example Scenario: 

If an automation contains 3 activities, each activity should independently show: 

Its execution time (start → end) 

Count of records processed 

Benefits: 

Easier performance monitoring 

Faster issue identification and debugging 

Better transparency into data processing within automations