Exciting stuff for Salesforce Admins at 2025 TDX regarding AI in Setup. The link below is the the full 14 minute video. If you can’t spare that time start around 7:22 to see what it can do and what it will do. Short list also posted below.
https://www.salesforce.com/plus/experience/tdx_2025/series/agentforce_at_tdx_2025/episode/episode-s1e13
Examples of Agentforce for Admin Setup capabilities:
Help – How do I deactivate a user?
Report Types – Create a custom report type to do something
Connected Apps – Explain this connected app
Permissions – Explain a user’s access to objects & features. Compare the permissions of user A and user B.
Flows – Summarize this flow. Agentforce will summarize the flow and give you the option to add the summary to the flow description or remake the summary shorter.
Flows – As an admin you may need to review an existing flow to know what it does. Now Agentforce can give you a head start! Open your flow, click the Agentforce button, then the Summarize flow button.
—
Here’s a longer summary of the “Add Case Comment” flow.
This is a Auto-Launched Flow.
This flow first checks if a case for a given customer exists. If it does, the flow proceeds to create a case comment with the provided comment text, sets it as published, and assigns the Parent ID to the Case ID. If no case exists, the flow skips the comment creation step. The outcome message is then set to indicate whether the comment was successfully added or not.
Several objects and their fields worth mentioning. Below are the details (the format is given as: object_name – field_name: interaction)
- Case – Id : Used to check if a case exists and as the Parent Id for the case comment
- CaseComment – CommentBody, IsPublished, ParentId : Used to create a new case comment record
———-
Here’s another example from a screen flow:
Selected Summarize Flow
Here’s a longer summary of the “Add or Modify Service Appointment Attendees” flow.
This is a Screen Flow.
This flow begins by setting the ServiceAppointmentId variable to the current service appointment’s record ID. It then presents a screen where users can select contacts, leads, or person accounts to add as attendees. After saving the attendees, it checks if the flow execution mode is ‘Individual’. If yes, it displays a summary screen showing the number of added, updated, and removed attendees. The flow interacts with ServiceAppointment, Contact, Lead, and PersonAccount objects, updating their respective attendee records.
Several objects and their fields worth mentioning. Below are the details (the format is given as: object_name – field_name: interaction)
- ServiceAppointment – ServiceAppointmentId : Used to set and retrieve the service appointment ID
- Contact/Lead/PersonAccount – Name, Email : Used to select and add attendees to the service appointment
- ServiceAppointmentAttendee – Added, Updated, Deleted Count : Used to track changes made to attendee records
- Flow – flowExecutionMode : Used to determine if the flow is running in individual mode
———-
Future Agentforce for Setup functionality:
Formulas – Create a Formula to do something
Objects & Fields – Create an object to store job applications
Navigation – Where should I go to create a validation rule?
Auth Providers – Create an auth provider to login via Google