Features

  • Winter ’20 Release brings new Salesforce Mobile App

    While not the most obvious of changes when reading the release notes, behind the scenes Winter ’20 Release brings new Salesforce Mobile App which aligns the mobile experience with Lightning Experience on desktop. Let’s take a quick look at what you can expect, and how to make the transition a smooth one for your users.

    Why the change?

    The short answer is, that Salesforce1 (or Salesforce Mobile) hasn’t changed much since it was released in late 2014.

    The slightly longer answer though adds a bit more nuance. After Salesforce1 brought in a new way of navigation and accessing your data, Salesforce then turned its focus to building out a new desktop experience, which ultimately led to Lightning Experience.

    Before this, users were able to use the Salesforce1 app via their desktop instead of using what is now referred to as Salesforce ‘Classic’ UI. The main benefit of this was to test how something would look on Mobile or to use it via browser on an iPad or similar device.

    But with Lightning Experience, Salesforce has had its hands full migrating all products and features over, and ensuring improvements were delivered. Certain elements were similar across mobile and desktop now, so there wasn’t a huge need to update/refresh.

    That was until late last year, when Salesforce and Apple announced a strategic partnership. With the partnership aiming to integrate voice commands (ie Siri) with Salesforce Mobile and rollout a Salesforce SDK for developers, which integrates with Swift (the preferred programming language on Apple devices).

    Introducing the new Salesforce Mobile App

    And so, here we are – with a new Salesforce Mobile App heading our way.

    The primary focus of the app appears to integrate the mobile vs desktop experiences further. This will allow for more admin control over what is made available to users, with mobile navigation introducing the App Launcher:

    A Lightning app's desktop navigation items are reflected in the mobile app
    App Launcher coming soon to new Salesforce Mobile App.

    Key improvements to navigation:

    • Navigation Bar at the bottom of screen will now feature Favourites, Search and Notifications . This is a change from the global / quick actions.
    • App Launcher finally appears on Salesforce Mobile. Allowing users to select standard/custom apps, and display the related tabs.
    • Personalisation of Nav Bar, will be reflected for users on Lightning Experience (aka Desktop) and Mobile App.

    What other changes are coming?

    Changes to Page Layouts are also included, and now the same page will display for Lightning Experience or Mobile App. Admins will only need to create one page now.

    What does this mean in the real world? It means you will have control to hide components which don’t make sense on either desktop or mobile experience.

    Voice Commands

    “Hey Siri, show me my dashboard.” and now Siri will actually listen… With the new Salesforce Mobile App opening up your dashboard page.

    The new Salesforce Mobile App will also (and obviously) tie into the recently announced Einstein Voice and Einstein Platform Services, which will allow users to dictate notes, get Einstein recommended updates, etc on Apple/Google/Alexa devices.

    What do you need to do?

    This new mobile experience is opt-in, so even if users get the new mobile app – from the App Store/Play Store – without the new permissions, they will not experience any changes.

    Salesforce has given control to admins to prepare for the transition, similar to Lightning Experience Transition.

    From a high level, Salesforce recommend the following steps:

    When will the new app be available?

    This should become available globally, starting from October 14th 2019. Users will

    Additionally the new User Permissions will be available as part of Winter ’20 release, which should be rolled out globally (for majority of orgs) by the 14th October.

    Resources

  • Winter ’19: Top Sales and Service Cloud Features

    The first release of 2019 is almost here… Yes, I typed that right, 2019!  I was sitting in a meeting today, and we were planning the roadmap out to 2021.  It’s crazy to think…  But as the seasons change, we hit the start of the three-releases-a-year cycle with the Winter ’19 Release from Salesforce.

    winter19 - snowboarding Astro
    Winter ’19 – Snowboarding Astro

    Now I have to admit, I was caught a little off-guard by the release.  It wasn’t until I saw the new snowboarding Astro in a developer sandbox, that I realised I had completely missed the normal pre-release build up. :-O

    Where did the last 2 months go?!

    At least there is plenty of time until Dreamforce 😀

    Is it just me…?

    I struggle to be “wowed” with this release.  Now don’t get me wrong, there are some nice usability tweaks for sure.  And some additional features which do really help make Lightning a more robust and complete user experience.

    But I am left wondering, where is the “Salesforce magic”?

    Maybe there is more to be announced shortly at Dreamforce?  But what about Dreamforce last year?  Where is “myTrailhead” (there is an answer buried in the FAQ)?

    I assume the strategy for this year must be revolving around bedding-in the various acquisitions and general improvements to Lightning Experience.

    Top Features of Winter ’19 Release

    Stepping down from my little soap-box now…  And I will admit there are some really useful and cool usability features coming our way!

    So let’s have a look at the top features focusing on improvements to Sales/Service Cloud.

    Search List Views & Bulk Change Records

    List views have received some attention this release, and now have a cool ‘Search this list’ feature.  Such a simple idea, but I am hooked to using it now in my sandbox environment.

    Winter 19 Release: Search List Views

    You can now also do a number of bulk actions from the list view too, such as selecting multiple records and changing the owner.  This now brings yet another ‘small’ but useful feature from classic into Lightning Experience.

    Enhanced Run Page in Reports (Beta)

    Another cool feature – albeit a ‘beta feature’ – is the new Enhanced Run Page within Lightning Reports.  You can easily adjust what is displayed in the report, without having to edit the report and re-run…

    Also drilling down into a group/column is now a whole lot easier, matching Classic.

    winter19 - Enhanced Run Page in Reports
    Enhanced Run Page in Reports

    Joined Reports in your Dashboards

    Finally!!! Joined Reports can now be used as components on a Dashboard….

    Winter19 - Joined Report as a Dashbaord component

    Forecasts

    From memory it has been a little while since the last touch-up to Forecasts.

    Winter 19 will bring a number of new features, including the ability to now forecast by territory.

    Email tracking for your Sales and Service users

    In Lightning you can now track email responses, seeing if the email has been opened.  And actually displaying this information back in the Activity Timeline within Lightning, presenting this back in a way that is easy to view.

    Winter 19 - Email Tracking

    Live Agent Setup in Lightning

    You will now be able to setup Live Agent in Lightning Experience.  Another small thing, but one less reason to have to switch back to Classic!

    Bonus: Flow Builder

    So although not technically part of the Winter ’19 it was announced alongside the Winter ’19 release…  Early next year (likely Spring ’19 release), we will have a new Flow Builder.  Which will get a much-needed redesign.

    Removing the dependency on Adobe Flash is a huge benefit and one of the things I am most excited about.  It feels like every second day, I have to update Flash before I can then use Flow Designer.

    Salesforce's new Flow Builder
    The new Flow Builder… Coming soon!

    Wrap Up

    So aside from me being a little jaded, there are some nice usability features being added in this release which add a bit more flesh onto Lighting Experience.  (And if you haven’t migrated to Lightning yet, what are you waiting for?!)

    There are a lot of new features overall to the platform, and I am not sure if it is just the sandbox instance we are using or if it is the release… But Lightning Experience does feel a bit more responsive overall too.

    What are your top features?  Have I missed something?  Feel free to tell me / yell at me in the comments 😀

    Resources

    Other resources to help get #releaseready with the upcoming Winter 19 release.

    Salesforce Official resources:

    And the blogosphere:

  • What is the difference between Process Builder and Workflow?

    Recently the Force.com Developer certification was retired, and all certificate holders were encouraged to switch to the Platform App Builder certification. Which is exactly what I did. One of the things that stuck out to me though, was ‘what is the difference between Process Builder and Workflow’?

    Both tools have now been around for a while. Though a lot of admins still aren’t sure about the difference between the two. So in this post, we will look at the difference between the two and more importantly when you might choose one over the other.

    What is Process Builder and Workflows?

    So let’s start at the beginning… What exactly are Process Builder and Workflows? In short, they are two features within Salesforce which allow you to build process automation within the system.

    Process Builder versus Workflow, which should you use?  What is the difference between Process Builder and Workflow?
    Process automation, helps simplify the user experience

    Both, Process Builder and Workflows, are very similar in the fact they allow you to define criteria and then do ‘something’ automatically without the need to code. This is what is called Declarative Development, or in Salesforce speak ‘clicks-not-code’ may be something you may have heard.

    You may have a process requirement you can automate for your users. For example when an Opportunity is updated to ‘Closed Won’, you then need to create another record (like a Contract) and send a notification to the Fulfilment team. This type of process can easily be done using the process automation tools within Salesforce, with no coding skills required.

    This is one of Salesforce’s strengths in the CRM space. A large number of other CRMs out there, typically did not (and still don’t) allow any users within the system access to this type of process automation. Instead requiring custom development / coding to setup or buying additional expensive add-on packages.

    Salesforce Workflows Rules & Actions

    Salesforce Workflow Rules & Actions have been available in the system now for a long time. Dating back many, many years – they were even available in the system before I started using Salesforce (all the way back in 2011). Workflow rules on custom objects were released back in Winter ’06… That is over 12 years ago now!

    Workflows Rules allow you to define a set of criteria. And then you control when the rule might fire (eg when a record is created, or every time it is updated).

    Additionally when the rule fires, it can be set to complete a number of the following actions:

    • Field Updates
    • Email Alerts
    • Create Tasks
    • Send an Outbound Message

    As a result, most Admins can then automate business processes with simple clicks-not-code.

    Salesforce Workflows: A Workflow Rule and Action

    But there was still a ‘wall’. This would be the point that you would have to move over to Apex triggers and classes to continue automating more complex processes…

    Additionally, there was no easy way to follow the entire process within the system. If you had multiple workflows firing at different steps, there was no way to see these easily. Diagnosing issues in a process become very complex. And Process Builder was born!

    Salesforce Process Builder

    Process Builder, or Lightning Process Builder as it is now called, started life as a beta in the Winter ’15 release. And one of its main goals was to allow Admins to create the entire process in one place, rather than using multiple workflow rules.

    So the big ‘win’ here how you can connect different steps together to make a single process flow. And it is very visual.

    Also by creating a complete process, you can also control which step is executed when. This was an issue with Workflow Rules, you couldn’t specify the order in which a workflow rule would be processed. At least not without a lot of cumbersome customisation work (new fields, extra workflows, field updates, etc).

    Process Builder simply allows you to drag and drop your rule criteria. Meaning you can have more control over the order things are processed:

    Process Builder, drag and drop criteria to rearrange order

    Add into the mix, some of the more advanced features which Process Builder now allows Admins to do:

    • Create Records (not just task records)
    • Update fields on any related record
    • Post to Chatter
    • Invoke other processes
    • Launch a Flow
    • Submit a record for Approval
    • Call/invoke an Apex class

    This is where we start to see some of the key differences between Process Builder and Workflows.

    And you can start to see why Process Builder has been created. It continues to drive the ‘clicks-not-code’ philosophy further, and continues to bridge the gap between what Admins can do versus Salesforce Developers.

    So, what is the difference between Process Builder and Workflow?

    To give you a high level breakdown between the two, let’s compare them side-by-side:

    Difference between Process Builder and Workflow... Which should you use?
    Process Builder vs Workflows… Which should you use?

    Additional Consideration: Bulk Record Updates

    There are one additional thing to consider though, namely existing automation within your org. Especially around support when bulk inserting or updating records (eg when updating 30,000 records via Data Loader). The good news is that Process Builder was ‘bulkified‘ (as of Winter ’16). However there can be issues when the code may not be setup in a way which accounts for Process Builder. This is something that Workflows handle without much further consideration…

    Existing Triggers, Workflows, etc may need to be reviewed to ensure Process Builder will work nicely alongside. Here is a detailed breakdown from David Liu over at SFDC99. It is a guide to when to code versus when not too, but it is aimed at advanced admins/developers.

    Update: 23rd July – Bulkification for Process Builder 

    The way Process Builder manages bulk requests is a point worth considering before implementing Process Builder.  A bulk request can be from importing contacts into your CRM, or an integration which updates a number of records as part of its process.

    When designing your solution, you should also focus on scalability and overall robustness of the design.  What do I mean by scalability?  I am referring to the the ability of your solution to handle increased volumes of data in the future.

    This article from ShellBlack (refer Rule #4), dives into the topic of Bulkification and Process Builder further.  And advises on some of the points you should consider before choosing Process Builder vs Workflows.

    A further discussion point on the Trailblazer Community Idea also expands on this topic.

    Want to learn more?

    For a full breakdown of the automation tools within Salesforce, you can view the list in Salesforce Docs.

    And if you want some hands-on practise, around implementing an end-to-end solution, there is a Process Automation Specialist Superbadge on Trailhead. These Superbadges cover the relevant theory but also gives you a use case and business requirements that you then need to solve and create the correct solution.

    Alternatively, if you don’t feel like completing the Superbadge at this stage – you can always go direct to the Trailhead quick-start module on Process Builder.

     

    UPDATED 23rd July 2018: to expand on the issue of bulkification and Process Builder

  • Summer ’18 Release: Top Sales & Service Cloud Features

    Time marches on and 2018 continues hurtling towards summer (or winter for the southern half of the planet).  But it is that time of year again where we get to investigate and plan for the Summer ’18 release from Salesforce, which is due to be released to most orgs within the next month.

    Additionally, we see Lightning continue to be the primary focus for Salesforce with a number of key new features, as predicted, being included as part of this release.

    Release Notes – New breakdown

    Firstly, you may notice a subtle but helpful new format of the Release Notes.

    New sub-headings in the Summer '18 Release Notes
    New sub-headings in the Summer ’18 Release Notes

    Most features and changes included in the release notes, now appear to be broken down into easier to digest sub-headings covering the all important: Where/Why/How/When/etc.

    It is a subtle but useful change, given the volume of information in the 478 page document!

    Summer ’18 Release: Features Breakdown

    As with any Salesforce release nowadays, there are thousands of new features, and narrowing them down to a is getting harder and harder!  But let’s dive on in, and take a look at the Top Sales & Service Cloud Features.

    1) Lightning Console – To feature parity and beyond…

    With Summer ’18 Release, we see Lightning Console pretty close to matching Classic Console, with some additional new features added in for good measure.

    Now I know I am cheating in the top 10, as I am going to group a couple of features together in this one… But it will be worth it 🙂

    For the console changes, click here.

    Console specific features in the release include:

    Guided Engagement with Flow

    But the pièce de résistance though is the new Guided Engagement Console feature.  Allowing you to combine the power of Console and Flows, to give your users guided forms/scripts to work from:

    Summer '18 Release: Lightning Guided Engagement
    Lightning Guided Engagement

     

    2) Reports & Dashboards

    Summer ’18 Release from Salesforce includes a bonanza of features and updates for all things Reports & Dashboards… So again, I am grouping a few distinct features under one topic here – otherwise my top 10 would just be reports and dashboards!!

    For all Report & Dashboard features, click here.

    Lightning Report Builder

    First up, Summer ’18 Release sees Lightning Report Builder come out of beta, and become Generally Available.  With a few extra tweaks since Spring ’18 also added in!

    Summer '18 Release: Lightning Report Builder

    One thing to note: the user permissions have changed due to the feature becoming ‘generally available’, and this now allows you to hide Classic Report Builder from users, if you wish to…

    Lightning Joined Reports (Beta)

    Additionally, we see Joined Reports enter public beta within Lightning!  There are a few limitations listed in the release notes, but the biggest appears to be having to use the Salesforce Classic Report Builder

    Summer 18 Release: Joined Reports now available in beta
    Joined Reports (beta)

    Get organised: Folders and sub-folders

    I have to admit, this one makes my inner Salesforce geek very happy!  And I wrote about it in the predictions post back in January… As soon as I heard it was on the roadmap for this year, I have been eagerly awaiting this feature!!!

    Sub-Folders, within Folders!  OMG! 😀 😀 It is Lightning Experience only – but this has been a pain in the backside of many Admins, since even before I started working with Salesforce!

    Summer '18 Release: Report Sub-Folders
    Report Sub-Folders

     

    Export reports & keep your formatting

    Lightning Experience now allows you to export your report and keep the formatting of the report.  Simple…

    Filter History Reports by Old and New Values

    In Classic, another bug-bear of mine (and many others) was the fact you could not filter a History Report by the old or new field values…  It would only display them in the report or the history related list if the field was tracked.

    This ended up with a lot of reports being exported and then working with the data in Excel… GRRR

    But GRRR no more! With the ability to now filter by these values!

    Salesforce Summer '18 Release: Filter by Old or New Values on History Reports

    Thank you Salesforce!

     

    3) Lightning Experience improvements

    Another area with a number of smaller feature improvements, Lightning Experience continues to get refined with each release.

    Click here for all of them…  Otherwise, read on!

    Speed up your search

    Summer ’18 Release will allow your users to search by specific objects, from the global search bar…

    Summer '18 Release: Search by specific object

    Boom!

    Dependant picklists and Path

    Path is an amazing feature, allowing you to guide users through almost any process just based on a single picklist.  But with Summer ’18 release, any dependant picklists will now also prompt users when they move steps.

    Summer '18 Release: Update dependant picklists

     

    Group by Topics

    Topics are now available in Lightning Experience!

    Many users used Topics in Classic, and it is great to seem them ported over to Lightning Experience now.

    If you haven’t used them before, it allows your end-users to group and organise records, by a topic.  Imagine it like a #tag on Twitter/Facebook/LinkedIn/etc, allowing you to then search for the topic and get all related records.

    Salesforce Summer '18: Topics now in Lightning

    4) Privacy (Support for GDPR)

    With the upcoming GDPR changes, Salesforce has continued to add in features to assist businesses (and us Admins) to get ready.

    Changes to Individual object

    The Individual object was a little limited when it was first released in Spring ’18.  The object wasn’t like a standard object, meaning access was very limited.  And creation of records/etc Apex coding was required…

    But no more!  In Summer ’18 the object is now a standard object with all the bells and whistles that comes with that – including the ability to now use workflows/process builder!

    You will be able to now:

    • Create custom actions, buttons, and links for Individuals
    • Create different Individual record types
    • Undelete an Individual that you had deleted
    • Use Individuals with workflows or with Process Builder

    Make a Users’ personal data unusable

    As part of the new privacy regulations, and the ability to request your personal information is removed from a system, presents a bit of a challenge for anyone who has a user record within Salesforce.  These could be community users or internal users…. And is due to the fact you cannot delete a Salesforce user record, ever.

    So to get around this, Salesforce is now including a new system method ‘obfuscateUser()’ , which will scramble user information.

    This one definitely falls into the ‘advanced’ category, as it requires Apex knowledge (or how to invoke Apex via Process Builder/Flow).

    And would require planning and testing, as Salesforce is warning: that it cannot be reversed!

    Scramble user data before and after

     

    Summer ’18 Release: Key Dates

    There are a number of key dates you need to know for Summer ’18 Release.  So to help highlight what they are, here is a handy infographic from Salesforce.   Remember the dates shown below are in US date format though…

    Summer 18 release - key dates

    What is the release date for Summer ’18 Release?

    The release weekend for your org will depend on the instance it is on, but the release will occur on the weekend between the 18th May – 8th June 2018.

    Summer ’18 Release: Additional Resources

    Official Salesforce resources

    Other blog resources

  • Time to prepare for Summer ’18 Release

    It only feels like a few months since Spring ’18 release… Oh wait, it was.  As time marches on, we are now due for the next release from Salesforce with Summer ’18 release.  Over the coming weeks we will start the normal release readiness prep, but what are the key dates of the release?  And when will Summer ’18 be released? Additionally what features might we expect to see from Salesforce Summer ’18 release?

    Summer ’18 Release: Key Dates

    As with every release, there are a number of key dates you have to be aware of.

    Most of this is sourced from the Release Readiness Group and you can download a handy infographic here (source: Salesforce).

    April 19th – Pre-release orgs are available to preview the new release.

    April 23rd – The Preview Release Notes will be published.

    May 4th – Sandbox cutoff date.  Remember to check here for instructions on which sandbox instance a refresh will land on.

    May 18th, June 1st, June 8th – there are three release windows for Summer ’18 into production environments.  Which depends on your Salesforce instance.  You can check the dates relevant for your instance, here.

    There will also be a number of Release Readiness webinars, and sessions which will be posted via the Release Readiness Group in the Trailblazer Community.

    Summer ’18: Possible Features

    Because I am not one to generally wait…  Impatient, I know…  So I started searching the product roadmaps to see what is likely to be released as part of the Summer ’18 release.  Combined with a number of webinars I have watched, this is a list of some of the features likely to show in this release.

    But please note – this list isn’t definitive or guaranteed list.  And we will get official confirmation within the next week as the Pre-Release Orgs & Preview Release Notes become available. 

    So let’s jump in and speculate as to what we might see…

    Lightning Report Builder & Dashboards

    We are likely to see a lot more features being rolled out to the new Report Builder feature.  These are likely to include:

    • Joined Reports, finally in Lightning – albeit this is likely to be a beta/pilot release
    • The ability to create field to field filters. This will allow you to compare two fields directly within the report builder, without needing to build report formulas or custom fields. For example you could run a filter where Created Date equals any custom date field on your object.
    • The ability to create reporting sub folders.  So you could setup a ‘Sales’ folder, but then have sub folders for each sales team within it.
    • Ability to sort columns based on a summarised/aggregated value.
    • Setting dashboard schedules for multiple users

    Files

    Files is likely to see the introduction of a Library-type functionality.  This will be no doubt be a nudge for users still on Content/Libraries to move over to the newer Files functionality.

    Platform Enhancements

    The rollout of branding/themes started with the last couple of releases.  We will likely get the ability to now theme/brand each app individually (rather than one theme applying org wide).

    List views will also see Mass Quick Actions rolled out to more objects too.  While Persons Accounts should get the ability to create custom Quick Actions on the object.

    And Product Schedules should finally become available in Lightning Experience.  This should stop users having to switch back to Salesforce Classic to enable product schedules, or to establish/modify schedules for products.  Which is something one of my orgs uses alot, and has blocked Lightning roll-out for that team.

    Wrap up

    We will see if these possible features are actually included in Summer – and no doubt there will be a number of other additions which haven’t been included here… There are always 1,000s of features in each release – so I know we only touched the surface here!

    Appendix

    If you want to know more, one of the most helpful videos outlining some of the new features on the roadmap, is this one: True to the Core, which was originally included in my last post Dreamforce 2017 roundup.

    Also the Lightning Roadmap is available here, but a little out of date now Spring ’18 is in preview, it is available here.

    Hope that helps with exploring in more detail.

  • Cutting the Clutter: Maintaining a Clean Salesforce Org

    Maintaining a clean Salesforce org, doesn’t need to be a battle. Recently, I was watching a great webinar by Kelly & Leanne entitled ‘Cut that Clutter‘. And it got me thinking about how the problems faced by a cluttered Salesforce, and how it can easily consume an Admin’s time and effort. And it not only affects us as Admins, but also our end users! So in this post I am going to recap some of the awesome tips shared in this webinar, and also see offer some additional FREE tools to tackle the problem that so many of us face!

    The War Against Clutter

    Ok, ok. I admit that this header is full of hyperbole.

    Maintaining a Clean Salsforce, shouldn't be a battle...
    Don’t raise the white flag, in the war against clutter!

    But a cluttered Salesforce creates a lot of frustration and anxiety for me. And I assume most it does for most of you reading this too! My personal vendetta against clutter drives me to ensure I am always improving the org for my end-users…

    I have previously written about how we started to tame the Technical Debt beast haunting our primary orgs and removed over 2 million records from an org (hint: very manually).

    But there is still so much to do…

    It is a seemingly never-ending fight. But as Admin’s we are always looking for tools and resources to help us in our day to day Admin Superhero duties. And to help us in maintaining a clean Salesforce org…

    Cut that Clutter! – The Recap

    Now before we get much further. If you have a spare 30mins I strongly recommend that you watch the webinar as I am only going to briefly summarise it here…

    The session covers the Three-S’s. These are the primary areas to focus on, to ensure your CRM is kept in tip-top shape.

    • Security – making sure you know who can see what in your CRM
    • Structure – does the setup of Salesforce ensure data security and meet any data governance requirements
    • Strategy – how to plan and scale while ensuring you don’t have to keep doing ‘big clean-ups’ each year

    If you want to hear more, then please check out the video.

    Cut that Clutter: Resources mentioned

    Next up, the ladies mentioned some great tools to help you in maintaining your Salesforce org.

    From Salesforce:

    • Salesforce Optimizer (aka Optimiser in non-US/Canada countries 🙂 ) – I am in LOVE with Optimizer reports. It is such an amazing tool to help you analyse and understand where the Technical Debt is likely to be hiding within your org. This should be your first port of call, in maintaining a clean Salesforce. That is how much I love it!
    • Security Health Check – helps you understand any vulnerabilities you may have within your Salesforce. This covers areas like Password Policies, Critical Updates, etc.

    From AppExchange:

    • Field Trip – this tool is one I install in every org I have managed now for a number of years!! It is a great tool to help analyse and understand just which fields are being populated and used by your end users. It is worth noting, that if you have a field that is always updated automatically by a trigger/workflow… Then it will obviously show as being used, even if that trigger/workflow update isn’t actually required. But overall it will help you understand your org in very tangible way.
    • The Permissioner – can help you when mass assigning/removing Permission Sets from your users.

    From Trailhead:

    Additionally the ladies have set up an Admin Trailmix.

    This covers a number of modules covering: Salesforce Profiles/Permission Sets, User Authentication, Data Quality, Data Management and finally Reporting & Dashboards.

    Help with maintaining a clean Salesforce org

    Extra, extra! Two more tools to add to your Salesforce Cleaning toolkit…

    Now for the bonus round.

    There are always so many tools and ideas out there helping admins when maintaining a clean Salesforce org. And I am only skimming the surface with these next two tools…

    Compare Permission Sets & Profiles

    When watching the webinar, albeit not live, I started shouting at my screen.

    During the Security section, there was a point around Profiles/Permission Sets. As an admin it is a mammoth task to compare all profiles/permission sets and what they might grant access to within your org. This can be kryptonite to Salesforce Superadmins…

    There was a recommendation to switch off Enhanced Profile View, and then compare the permissions… But why do that? Especially, when there is a secret weapon at your disposal?

    Perm Comparator by John Brock is that secret weapon!

    Seriously… More people need to know about this tool! And I am not even on commission! 🙂

    Stop duplicates in their tracks…

    Salesforce hasn’t always been an admin’s best friend when it came to cleaning an org…And without getting all ‘back in my day’-ish…

    But there was a time Optimizer, Security Health Check and those tools simply didn’t exist.

    There was also a time Salesforce didn’t have an easy way to prevent duplicates… Admins had to either buy other tools to identify and manage duplicates, or create complex formulas and validation rules to try and prevent exact match duplicates.

    But when planning your strategy for maintaining a clean Salesforce, you should investigate the in-built duplicate management tools from Salesforce.

    After all, what good is cleaning up your security (profiles, access policies, passwords) and clearing out fields you don’t use any more – if your end users are still swimming in duplicate records?!

    The in-built feature will take care of the basics, but depending on your use case, there may still be a reason to buy a tool like Cloudingo or DemandTools (just to name a few).

    What is in your toolkit?

    De-cluttering your Salesforce can be so rewarding!
    De-cluttering can be so rewarding!

    As I mentioned I only skimmed the surface here… And this is a topic I can (and will likely) write more about in the future. I have rambled more than enough for now…

    So to wrap up the post, feel free to add any other suggestions or recommendations for your ‘Cleaning Salesforce Toolkit’ into the comments section below.

  • Secrets of Spring ’18: Hidden Formulas

    Spring ’18 is now live for most orgs, but there appears to be some changes included in the release which haven’t been documented :-O The great news for us Admins, the changes actually resolve a number of ‘simple’ problems we have when trying to calculate values in formulas.  So in this quick update we look at some of the new ‘hidden formulas’ included with Spring ’18 and some of the use cases where you might be able to apply them…

    Update: 26/Feb  – Eagle-eyed Ekaterina has pointed out in the comments, there are even more additional formulas available!  Here is a link to her blog if you want to read more…

    Update: 01/Mar – Salesforce have now scheduled an update to the Known Issue and scheduled an update via the Spring ’18 Patch 11.0.  To see what’s included, click here.

    Hidden Formulas: ADDMONTHS

    The first of the hidden formulas included in Spring ’18 is the new AddMonths function.

    Imagine you need a formula to calculate a date, which based off another date entered on a record.  For example, you could see this in action in Contract End Date (contract start date + 2mth duration = contract end date).

    The formula to add 2 months, while only using point and click Admin features, is quite little long winded (if you want to accurately account for Leap Years):

    IF(
      MOD( MONTH( date ) + 2, 12 ) = 2,
      IF(
        DAY( date ) > 28,
        DATE( YEAR( date ) + FLOOR( ( MONTH( date ) + 2 ) / 12 ), 3, 1 ),
        DATE( YEAR( date ) + FLOOR( ( MONTH( date ) + 2 ) / 12 ), 2, DAY( date ) )
      ),
      IF(
        OR(
          MOD( MONTH( date ) + 2, 12 ) = 4,
          MOD( MONTH( date ) + 2, 12 ) = 6,
          MOD( MONTH( date ) + 2, 12 ) = 9,
          MOD( MONTH( date ) + 2, 12 ) = 11
        ),
        IF(
          DAY( date ) > 30,
          DATE( YEAR( date ) + FLOOR( ( MONTH(  date  ) + 2 ) / 12 ),
           MOD( MONTH( date ) + 2, 12 ) + 1, 1 ),
          DATE( YEAR( date ) + FLOOR( ( MONTH( date ) + 2 ) / 12 ),
           MOD( MONTH( date ) + 2, 12), DAY( date ) )
        ),
        IF(
          MOD( MONTH( date ) + 2, 12 ) = 0,
          DATE( YEAR( date ) + FLOOR( ( MONTH( date ) + 2 ) / 12 ) - 1, 12, DAY( date ) ),
          DATE( YEAR( date ) + FLOOR( ( MONTH( date ) + 2 ) / 12 ),
           MOD( MONTH( date ) + 2, 12), DAY( date ) )
        )
      )
    )

    GULP!!

    But, now you will be able to use the AddMonths formula…

    So you want to add 2 months, to a field containing the start date of the contract, it is now as simple as:

    addMonths(date, 2)

    To see more details, until the official documentation is available, visit Ekaterina’s post here.

    Hidden Formulas: WEEKDAY

    Salesforce WEEKDAY formula
    Salesforce WEEKDAY formula

    Also in Spring ’18, and a little more obscure, is the new WeekDay function.

    It allows you to return a number (from 1-7) which indicates the day of the week, based on a date field within Salesforce.

    Before, once again, you could retrieve this information – but it was again a bit cumbersome:

    CASE(
      MOD( DATEVALUE(CreatedDate) - DATE(1900, 1, 7), 7), 
         0, "Sunday", 
         1, "Monday",  
         2, "Tuesday", 
         3, "Wednesday", 
         4, "Thursday", 
         5, "Friday", 
         6, "Saturday",
         "Error"
    )

    But now – simply use:

    WeekDay(date)

    And it will return for you, a number which represents the day of the week:

    1 = Sunday
    2 = Monday
    3 = Tuesday
    4 = Wednesday
    5 = Thursday
    6 = Friday
    7 = Saturday

    Hidden Formulas: CURRENCYRATE

     

    Salesforce CURRENCYRATE formula
    Salesforce CURRENCYRATE formula

    The next hidden formula in Spring ’18, is CURRENCYRATE.

     

    This formula will return the conversion rate used for a record’s currency code.

    So for example, if you have the default currency as USD.  But the record’s currency is GBP – you can now retrieve what the conversion rate is between those currencies.  And then display it as a formula field or use it in reports.

    CURRENCYRATE(IsoCode)

    As a possibly obvious tip, Currency Management will need to be activate in your org before you can use this…

    The returned value will be a number showing the currency conversion rate, eg 0.717412 (but you will be able to control how many decimals are shown).

    Hidden Formulas: MFLOOR & MCEILING

    Salesforce MCEILING formula
    Salesforce MCEILING formula

    These two final formula functions go hand in hand.  And now also available in Spring ’18!!

    Previously, we did have access to ROUND function:

    Round(decimalNumber, 2)

    Where you could round a decimal number to the number of decimals you specified in the formula.  But you couldn’t force Salesforce to round up or down… Until now!

    MCEILING will round a number up to the nearest positive whole number.  Whereas the MFLOOR will round down to the nearest positive whole number.

    Both functions will return 0, if the input number is a negative.

    So for example, if you have a number field which contains decimals but you want to round up or down, you can control this with these functions.

    To round up, to nearest whole number:

    MCEILING(number)

    To round down, to nearest whole number:

    MFLOOR(number)

     

    Found any others?

    No doubt Salesforce will be updating all relevant documentation and the Help site soon.  But if you have found any others, add them to the comments below!

  • How to Plan Your Move to Lightning Experience

    For many businesses, now is the time to move to Salesforce Lightning.  But moving to Lightning can feel like a daunting task.  Where should you start?  How to you make sure you don’t disrupt the business?  So in this first post, we will take a look at how to plan your move to Lightning Experience.

    In the next post, we look at how to implement your plan and go-live!  But in the meantime, if you have any tips of your own, feel free to add them in the comments section below.  And let’s start planning…

    Planning your move

    migrating to Lightning is all about planning

    Before we start, let’s just clear the air.

    As an #AwesomeAdmin you probably already know there is planning required to make the switch over.  The old adage – ‘failure to plan, is planning for failure’ – is never truer than when changing how a user works within a system.

    But driving user adoption and making the transition as smooth as possible, doesn’t need to be overly complicated process though.  And by planning your transition you set yourself up for the best possible result.

    So let’s get started.

    WIIFM?!… What’s In It For Me?

    One of the first steps to planning any change should to be understand the ‘what’s in it for me’.  It is the first question most users want to know about any change…

    Salesforce Lightning adoption - answer 'What's in it for me' from your end-users point of view
    Understanding ‘What’s In It For Me?’will help drive adoption…

    Sure Lightning Experience looks great.  You can now customise the colours to match your company identity…

    But that doesn’t really engage end-users in using the platform.  After all we want them to use the system once we make the change, don’t we?…

    Be honest with yourself.  Would a typical sales, customer service or partner really care about that?

    Answering this question for each type of stakeholder is one of the best ways to ensure everyone buys-in to making the move.

    A great example is dealing with a stakeholder from Sales.  Lightning offers many new features which benefit most sales users.  Here are a few…. Sales Path to guide on what to do in the system to move to the next stage.  Kanban board for managing your pipeline with drag-and-drop ease.  What about Sales Console?  Use of macros practically anywhere in Salesforce?

    The point here is to you need to demonstrate you understand your end-users by understanding their problems.  If you understand the problem, you can effectively position a feature or benefit that solves it.  And this helps engage these stakeholders early on…

     Why should we invest in making this change?

    The next step is to develop a business case.  It sounds horrible, but it can really help in convincing your senior stakeholders on why they should support the change.  And to drive adoption when launched, you need their support…

    Salesforce Lightning Experience across multiple devices
    Even Astro loves Lightning Experience…

    This may not be applicable for all business, but I always try to work out a rough cost/benefit to any changes my team make.  Even if it is just an estimate.  And this loops back to understanding the WIIFM within your business.

    Every business problem – and in turn the potential solution – have a potential time/cost associated with them.

    This is the gold dust in developing your business case to answer the question most senior stakeholders within business would ask,

    As an example, a simple cost-to-benefit calculation could be based on decreasing sales admin time.  By improving the time taken to process and close a contract within the system, you can quantify the potential upside to the business.

    So if an average salesperson closed an extra 2 deals a day/month/year due to improving the sales workflow in Lightning, how much is that worth to your business?  (average contract value * extra deals per day = potential upside).

    Keep in mind, this is only an estimate.  But it can be a useful way to engage the business and to capture metrics relating to the success of the project once completed.

    Mind the gap…?

    Salesforce has spent the last couple of years attempting to make Lightning match the features of Classic.  But there are still some gaps between Classic and Lightning Experience.

    The next item on our list is to check what these gaps actually mean your org.  By doing so you ensure your users can still use all key features they need.

    If there is a feature gap or limitation, the next step should be to look at the publicly available roadmap.  This outlines the upcoming features planned for release and may cover the feature that is a priority for you.

    Also each published version of the release notes now include a section on what is and what is not included in Lightning Experience.  For the Spring ’18 section, please have a look here.

    Side note: The roadmap is scheduled to be updated after the Spring ’18 release, but a handy video to watch about the Force.com platform and upcoming features is the True to the Core video.  Or there is a breakdown of the expected features in the 2018 predictions post here.

    Resources

    Salesforce is clearly invested in supporting all orgs to move to Lightning Experience.  Releases now introduce most new features as Lightning Experience only.  But to help, there is a wealth of content available for free to sink your teeth into.

    For starters there is a great Trailhead module specifically on getting hands-on with a Lightning Experience roll-out.  There is also a quick overview of the steps on the Admin blog.  But personally I highly recommend jumping to the Power of Us site, which has been setup to cover best practice for making the jump to Lightning.

    Each and every org now also has the Lightning Readiness Check built-in.  And the check gets an update every release to give you more and more insight into your org’s compatibility into making the change.

    If you want more information about how to take a business-first approach to rolling out Lightning, I found this article over on SalesforceBen.

  • Spring ’18 Deep Dive: Reports & Dashboards

    Spring ’18 release brings with it a swag of new features.  But it also brings with it a big makeover for reports and dashboards.  In this post we are going to take a deep dive into reports and dashboards in Spring ’18, and see what is coming our way.

    Additionally (and most excitingly) this is the starting point for new reporting and dashboard features within the Lightning.  With another more features heading out way over the coming releases.  To see what this includes, check out feature predictions for 2018 here.  Otherwise let’s get started!

    Dashboards in Spring ’18

    Coming in Spring ’18 your users will now be able to subscribe to dashboards easily within Lightning.

    By setting up a subscription schedule (either Daily, Weekly or Monthly), Salesforce will then schedule a refresh of the dashboard and send out an email update to the user.

    Subscribe to Dashboard in Salesforce Lightning
    Subscribe to a dashboard. Source: Salesforce

    And keeping with the myLightning ability to theme and customise your Lightning instance, dashboards now support more customisation and personalisation by selecting a colour theme.

    Additionally you can then choose the theme by individual component to highlight sections.

    Set a colour pallette for your Dashboards
    Colour your dashboards whichever way you want! Source: Salesforce

     

    Report Builder (Lightning)

    Lightning Report Builder was first introduced in the Winter ’18 release.  But the new report builder is in beta, meaning there are a number of known limitations.  Reports and dashboards in Spring ’18 starts to bridge that gap.

    Most features in Spring ’18 release are migrated Classic features.  But these features are reworked to operate in a very Lightning way.  After all what good is it having a new user interface, and not take advantage of reworking how users can use the system?

    Most importantly it is easy to see how this is a stepping stone to the future for Reports & Dashboards in Lightning Experience.

    Summary Formulas, Buckets & Cross-Filters

    As mentioned above, these aren’t specifically new features.  But they are new for the new Report Builder and operate a little differently.

    For example being able to create a summery bucket on a column, simply select the column dropdown and create:

    Report Builder and creating a Bucket column
    Creating a summary bucket within the Lightning Report Builder. Source: Salesforce

    Or creating a cross-filter, which is also easily done now within the new Report Builder:

    Create a Cross-Filter within the Lightning Report Builder
    Create a Cross-Filter within the Lightning Report Builder. Source: Salesforce

    How to activate the new Lightning Report Builder

    To get access to all of the new features of reports and dashboards in Spring ’18, you will need to first activate the new Report Builder.

    A note before we start, there is a key dependency to activating Lightning Report Builder… That prerequisite is  enhanced folder sharing needs to be enabled.

    If your org was created after the Summer ’13 Salesforce release, you already have enhanced folder sharing. If your org isn’t already using enhanced folder sharing, see Turn On Enhanced Sharing for Reports and Dashboards in the Salesforce Help.

    Go to Setup -> Reports and Dashboards Settings -> Enable Lightning Report Builder (beta):

    Enable Lightning Report Builder (Reports and dashboards in Spring '18)
    Enable Lightning Report Builder

     

    Once enabled, remember to also update either a profile or permission set to include access to the Report Builder (Lightning Experience) too:

    Enabling Report Builder Lightning Experience
    Enabling the Report Builder (Lightning Experience) on a profile

    Remember, if you don’t see this option, you need to check your Folder Sharing rules within Salesforce.  And you will have to check via Classic Setup…  The irony isn’t lost – this dependant setting is only available via Classic Setup menu currently. 🙂

    Before enabling though, ensure you are aware of the implications of doing so.  Especially how this will impact end-users within your org.  When you are ready, jump back into Classic UI and then go to: Setup -> Folder Sharing -> “Enable access levels for sharing report and dashboard folders”.

    Wrap up

    The changes to reports and dashboards in Spring ’18 gives us an insight into where Salesforce is taking the analytics features of the platform.  Along with the added flexibility the Lightning Experience grants.

    Overall reports & dashboards within Salesforce are finally getting much deserved makeover…  And there is more to come over the next few releases!

  • Spring ’18 Deep Dive: GDPR Features

    Simple put, GDPR is inescapable for those dealing with individuals within the EU.  In the last post we took a look at what GDPR is and how to start preparing for it.  Additionally, within the next month we also have Spring ’18 release going live.  So the good news is there is a number of GDPR features included to assist Admins prepare…

    Recap: What is GDPR?

    General Data Protection Regulation, otherwise known as GDPR, is the new privacy regulation coming into force in 2018.  It will replace the EU’s previous Data Protection Directive, and align privacy laws and regulations across all EU member states.

    Part of the GDPR is the retention and removal processes re: personal data after a period of time.  Companies should only retain personal data for as long as needed.  So for example, if you have contact details of a person which is linked to contract data you may need to retain it for 7 years.  Versus simply having a contact on a mailing list, retaining the data for this long may not be justifiable.

    For more details, take a look at my last post for the what/when/how of GDPR.

    GDPR: Be Prepared

    GDPR is ultimately an update to a number of data/privacy regulations across the EU.  But the easiest place to start for most companies is to map out and understand the following: 

    • where your data comes from. (eg web-to-lead, email-to-case, data.com, users entering in the data),
    • how it gets used/stored. (eg are there integrations which also use the data, is it stored outside of Salesforce, are records stored in standard and custom objects within Salesforce),
    • what business processes which clean up or remove data. (ie how long does your company need hold onto personal data for (and for what purpose)? Is there already a process to remove personal data?)

    Once you understand there where, how and what of your data, you will then understand where the following features and changes may help and support you.

    Spring ’18 & GDPR Features

    Salesforce Data Privacy Record - aka Individual Record
    A sample Salesforce Data Privacy Record – aka Individual Record in Spring ’18 Preview Sandbox (click to view full image)

    Data Privacy Records (aka Individuals)

    Spring ’18 release brings with it a new setting under Company Profile within Setup.  The setting to enable Data Protection and Privacy, will expose the new object ‘Individuals’ within your org.

    This new object connects to either a contact or lead record within Salesforce to store data privacy settings for that person. So for example you can store the customer’s preference re: soliciting products and services.

    A key note here is that in the preview instances of Spring ’18, Individuals it isn’t treated like other objects and doesn’t have a standard tab available to access the object.

    But a gentle word to note before we go through how to set this up.  As with any changes to a production system, it will require planning before setting this up to ensure it works for your processes.  A number of these changes below may also require assistance from a developer or changes to your marketing platform via API.  This is not entirely a point and click setup…

    1. Activate the feature within Setup

    Lightning: Setup -> Company Settings -> Data Protection and Privacy
    Classic: Setup -> Company Profile -> Data Protection and Privacy

    This will expose the new Individual object, with the standard fields within your org.  Most of these fields are created for the purpose of tracking opt-out requests and personal preferences.

    Some examples include:

    If a contact opts-out of geo-location tracking, you can store that preference here.

    You can even store the D.O.B of the person and indicate if they are considered a minor or not.  (You might need to do this as minors carry different standards for elements like data retention under GDPR.)

    And good news is you can also add custom fields to this object if you wish to.

    2. Update Page Layouts

    Add field to relevant page layouts on contact & lead objects.  Salesforce also suggests to rename the field label from ‘Individual’ to something more meaningful to your users.

    3. Existing Contacts/Lead Records

    There is a code-based solution to create data privacy records for existing contacts & leads within your Salesforce, which also includes code for handling person accounts.

    I won’t go through the code here.  But if you are interested, you can take a sample of the code here.  Remember you will need to execute this somehow (ie start the code running), so you may need help from a developer friend(s).

    4. New / Changes to Preferences

    Finally, you will also need to plan how new records get managed within Salesforce.

    Will an Individual record be created when a contact or lead is created?  What about field updates / etc?  Do you do this via a trigger in Salesforce or via API from your email platform?

    And what do you get at the end of this?  A new record of course … 🙂

     

    bad data quality ahead

    Data Quality & Duplicate Jobs

    GDPR features in Spring also come in the form of expanded functionality.  Spring ’18 release provides an update for its out-of-the-box duplicate management to allow Admins to run a duplicate job.

    Previously matching rules would run when a record was being added or updated by a user.  This would then either alert the user or block the user, depending on how the Admin had set it up.

    But in Spring ’18 release, us Admins can now run a “Duplicate Job“.  This allows you to use (or create) a matching rule and then run a search within Salesforce to find duplicates.  Once a Duplicate Job completes, you will be able to take action by comparing and merging records, right from the summary page.

    Duplicate Job within Spring 18 release
    Duplicate Job within Spring 18 release.

    Changes to Web to Case and Web to Lead

    Spring ’18 release also brings another GDPR feature.  This time there is a slight update to how failed Web-to-Case and Web-to-Lead emails are handled.

    When a Web-to-Case and Web-to-Lead fails an email is generated automatically to advise.  This email will no longer include any personal data inserted by a third-party application.

    Data.com for UK/Ireland Contacts

    This only impacts users who are using Data.com Prospector or Clean.

    Data relating to contacts stored within Data.com Connect (only UK & Ireland) will now be removed from the Connect database.

    Also the Clean Status field on a Contact/Lead records will be changed to ‘Not Found’.

    Wrap Up

    As you can see there is a lot to cover, and Salesforce is enabling businesses to become GDPR compliant with all the GDPR features in Spring ’18.  There is still more to read in the Release Notes for Spring ’18 if you are using other tools like Pardot, Inbox or a developer (specifically around Event Logs).

    There is support at hand, and if you haven’t already I would strongly recommend completing the Trailhead modules setup for GDPR Basics (and there is also a trail for US Privacy Basics too).

    Additionally Salesforce has a new section in the Help for Data Protection & Privacy.

    And finally there is a basic scenario guide, which looks at a number of common requests and suggested actions/things to consider to be compliant under the various privacy laws (including GPDR).

Back to top button