Uncategorized

Time Flies!

It’s that time of year again! Salesforce Winter 2025 release is starting its rollout, and like every year, it is just in time for Dreamforce. (Are you attending this year?)

As always, the winter release is packed with exciting new features to enhance the already powerful Salesforce platform. Here are some of the exciting enhancements the team here at CloudFirst Labs are looking forward to!

Send Email Action Upgrades

The simple Send Email component in Flow Builder is getting a major power-up! Before this release, you were limited to a maximum of 5 recipients.  That has now been bumped up to an impressive 150! Wow!

Another amazing update to the component is the ability to CC and BCC recipients. This was such a highly requested feature, Bob, our CTO, had to build a custom solution to support this. However, starting with Winter ’25, this will become a standard OOB feature. We are very excited to put this new ability to work!

Find out more about this amazing update here.

Action Button Screen Component Becomes Generally Available

At our core, we’re committed to sticking with out-of-the-box (OOB) Salesforce solutions as much as possible, leveraging the power of standard features. We avoid beta products because we understand how much things can change between a beta and a final release.

While a popular, unofficial Salesforce site has offered ways to add a button in screen flows, it involved custom solutions—and that comes with security risks.

The great news? With this release, the action button is now generally available, providing a secure, native option within Salesforce.

So what does it do? Let’s see it in action!

As a #flownatic this is HUGE! I can’t wait to start enhancing solutions with the new screen component for Flow Builder.

Read more about it!

Apex Event Monitoring

While stakeholders typically focus on business optimization, admins and devlopers are always seeking ways optimize system performance. In Salesforce there are so many processes going on behind everything, it can be hard to pinpoint bottlenecks and detect the true source of issues. Not to mention the difficulty in getting an End User 360 view for auditing and adoption.

Enter Event Monitoring…

Prior to the release, it was apart of Salesforce Shield, or could be added as a subscription. But now, with Winter ’25, ALL orgs will have access to  free-tier of Event Monitoring. Time to take your troubleshooting to the next level!

Learn more.

Control Who Can Perform Authenticated Callouts

The Winter ’25 release brings a game-changer for admins with the new external credential permissions feature. Now, admins can fine-tune which users have access to external systems, tightening security and keeping everything in check.

Now, most standard permission sets and profiles have access to the User External Credentials object by default.

With better control over who can connect where, admins can breathe a little easier knowing their data and integrations are secure and compliant with company policies. It’s a small update with a big impact on day-to-day security management.

Here’s the rundown of the update.

Dynamic Highlights Panel

Lightning Record Pages are becoming more dynamic! Previously configured through Compact Layouts, now you can customize the Highlights Panel from the Lightning App Builder.

Take note, that this feature isn’t available on all objects yet.

This feature was delivered because of votes in the idea exchange, so we know Salesforce does listen to the community.

This update will give more control over what fields users find most important.

Learn more about the Dynamic Highlights Panel here!

While new features are being added, sadly, some are being Retired

Standard-Volume Platform Events Are Being Retired

https://help.salesforce.com/s/articleView?id=release-notes.rn_messaging_standard_volume_retirement.htm&release=252&type=5

 

Cadence Builder Classic (1.0) is Being Retired

The cadences of Sales Engagement, formerly known as High Velocity Sales enables users to really take control of their sales workflows.  The Classic builder is unfortunately getting retired for the more streamlined Cadence Builder 2.0. This means less complexity, less effort, and more positive conversions!

Here’s what it looked like before:

This is the overhaul:

Find out more about the change here.

And if you are in need of training for the new Cadence Builder, or Cadence Conversions while getting your reps up to speed, feel free to reach out to Cloud First Labs! Our team has enabled clients with over 200 cadences to streamline their Prospect outreach.

That’s all for now!

This is just a small glimpse into what this release has to offer. Check out the full release notes for the complete rundown of all that’s coming in Winter ‘25 to Salesforce.

Don’t forget to pop in to the Release Readiness Live sessions that go over all the latest and greatest enhancements and have the opportunity to get some of your questions answered. If you’re excited to see more, you can also hit this trail for additional information on some of the highlights in the release.

Have a fun and safe Dreamforce!

Talk to the Professionals!

To learn more about our Salesforce services,  MuleSoft IDP, or MuleSoft RPA, please visit our website or fill out a Contact Us form here.

 

 

Overview – You aren’t stuck using the MuleSoft Sharepoint Connector

It is important to note that MuleSoft provides numerous other ways to integrate with Sharepoint; this post shows only one example. For example, if an organization has an Anypoint Platform subscription, a MuleSoft application can be used to easily monitor and/or integrate with Sharepoint using the handy and robust MuleSoft Sharepoint Connector. This connector has dozens of operations available to handle these needs.

But that’s easy, and we wanted to show the full functionality of MuleSoft and RPA processes that can be used to handle a wide variety of use cases and can be triggered from all sorts of common applications, and in this case, a MuleSoft RPA process that is triggered from Sharepoint by the creation or upload of a new file in a specific folder in Sharepoint.

If you’re a Sharepoint and MuleSoft shop, follow along with this post and see how an organization can be enabled to automate activities based on Sharepoint files and Power Automate, connecting to MuleSoft RPA without even needing to utilize the rest of the MuleSoft Anypoint Platform.

Set up Automation in Sharepoint

Create a New Power Automate Flow

Within Sharepoint, go to Integrate -> Power Automate -> See your flows :

From there, click New flow -> Automated cloud flow.

Our use case will be named ‘Call MuleSoft RPA process on File Upload’ and the trigger will be ‘Sharepoint – When a file is created (properties only)’.

Click Create:

Create Trigger Action

Click the auto-generated action step and set the Site Address and Library Name as desired. Under Advanced parameters, set a Folder name (e.g. /Shared Documents/Testing). By default, Power Automate will check for new files every 3 minutes:

Create HTTP Action for OAuth Call

Add a new action underneath the trigger of type HTTP. This will be used to make an HTTP request to get an OAuth access token used to authenticate and authorize the call to the RPA API. For URI, set https://anypoint.mulesoft.com/accounts/api/v2/oauth2/token. For method, do POST. For Headers, add one for Content-Type = application/json. And add one more for Authorization = Basic <base64-encoded client_id:client_secret value>.

For Body, set a simple JSON payload of: {“grant_type”:”client_credentials”}:

Create Parse JSON Action for Getting OAuth Token from Response

Add a new Action underneath the OAuth HTTP call. The Type should be “Parse JSON”. This is needed to be able to use the access_token from the previous HTTP step in the upcoming HTTP step for authentication.

Set Content = Body from the prior “HTTP Call to Get OAuth Token” step.

And for schema, use the “Use sample payload to generate schema” link and paste a sample payload into it to generate the appropriate JSON schema:

Create HTTP Action for RPA API Call

Finally, a step is needed to make the actual HTTP call to the MuleSoft RPA API URL. Get the URL from Anypoint Exchange after publishing the RPA process as an invokable run configuration in Production phase.

Set URI = <URL from Exchange>

Set Method = PUT

Create 2 headers. One should be Content-Type = application/json. The other should be Authorization = <“Basic ” + <Parse JSON – Body access_token>>

For Body, set executionId = <whatever ID is desired for identifying the RPA process execution> (in this case, Name from the trigger step is used). Then set any inputArguments as required. In this case, sharepointFileName is set equal to the “File name with extension” from the trigger step:

With this in place, the overall Power Automate flow should look like this and it can be saved:

Upon saving, it can be tested. Alternatively, a file can be dropped in the configured location and the flow will trigger, calling the MuleSoft RPA.

See it in Action

After uploading the screenshotted CSV file to that Sharepoint location, the RPA process was kicked off. It ran successfully, updating another application with the data from that CSV:

 

This is how easy it is to trigger a MuleSoft RPA process from Sharepoint instead of using the MuleSoft Sharepoint Connector! Part 2 of this post will contain the details on setting up the actual RPA process used here.  For a guided tour of getting this set up, check out my YouTube video:

Talk to the Professionals!

To learn more about our MuleSoft RPA, MuleSoft and EDI, or Salesforce services, please visit our website or fill out a Contact Us form here.