As Salesforce users with every release comes exciting new treats that we look forward to three times a year. Nonprofit Starter Pack users are even more special as there are bi-weekly product specific releases.
Thanks to some amazing volunteers, the Nonprofit Starter Pack now provides out of the box Spanish translations. This setting applies to standard objects, fields, and the Setup menu. Before implementing Spanish Translations for your organization make sure you are aware of limitations and best practices, outlined in the title link above. Overall this is a great step toward making this product more widely available. This is also a great initiative to help diversify the Salesforce ecosystem.
In-Kind Donation Management is now preconfigured on the latest version of the NPSP. Users have access to In-Kind specific Opportunity Stages, Sales Process and Record Type, Custom Fields, Page Layout. There is also some automation available to rollup the Fair Market Value amount Field up to the Contact or Account record. A little goes a long way and this functionality will make reporting and tracking much easier for In-Kind Gifts. If you have an earlier version of the NPSP, you will have to enable these features, but there is great documentation to walk you step by step on how to do so.
When working for a nonprofit organization you have to be extremely resourceful, be able to figure things out, and to deliver solutions all within a tight budget and under tight deadlines. Apart from the amazing Salesforce community and all the documentation available, Trailhead also continues to evolve and keep its content up to date. One of the new Trailhead modules that caught my attention, and could be helpful for nonprofits, is the Expand Your Reach with Communities.
Walkthrough is great because it walks you through a task or feature directly in your org. As a visual learner this is a great tool especially for those solo admins out in the Salesforce world. That being said, users should be aware and take precautionary measures by testing this feature out in the Sandbox first to avoid any issues, or jeopardize any production data.
What are some features you find will be helpful to your organization? Please feel free to share them on the Salesforce Success Community, on our Facebook page, or directly at me on Twitter @msespinal90.
Once again Salesforce has delivered on ideas! Some of these are a “nice to have” and some are long overdue. Let’s dive in and take a look at the ides delivered with this latest release:
Create and Edit Lightning Experience Record Pages (Generally Available) - Now administrators are able to create a record page either from scratch or copy an existing page from the setup menu. There are two ways you can create a record page; select edit page on a record page in Lightning Experience from the setup menu or click new from the Lightning App Builder in either Salesforce Classic or Lightning Experience. Ideas delivered on this were:
- Switch Tab Position for Feed-based Page Layouts (2810 pts)
- Add text box for instructions / reminders to the page layout (1260 pts)
Home: Customize Home for Different User Profiles (Generally Available) - Do you have different types of users that need access and see different things on the home page? Using the Lightning App Builder you can now create custom home pages for different profiles. You can always set a default home page for those who don’t have a customized homepage assigned to them. The idea, Allow customization of the Lightning home page (990 pts), was delivered for this feature.
Export Reports as Files from Lightning Experience - Just as in Salesforce Classic, you can now export reports in the Lightning Experience via a list view or from viewing a report to a .xls or .csv file. Just as it reads, the idea Ability to export report in Lightening Experience (6800 pts) was delivered for this feature.
Both Lightning Experience and Salesforce Classic
Contacts: Associate a Contact with Multiple Accounts (Generally Available) - This is a big one, that’s way overdue! I think a lot of Salesforce users from all industries are going to be very happy with this feature. As the title clearly states, this feature allows one contact to now have a relationship with multiple accounts. Most people have handled this in the past with custom objects or installed packages like Affiliations (from the Non Profit Starter Pack). Those will continue to work fine, but for anyone building out a new Salesforce instance it’s there ready to go...very cool. I’m sure there were a lot of ideas merged in this one that gets the credit, Link a Single Contact to Multiple Accounts, however, it has a whopping 64,560 pts...um...can someone say (again)...way overdue?
Use SOQL to Identify Reports Used by Dashboard Components - I think this is a nice to have capability. If someone leaves the company, as an Administrator you want to do a little house cleaning which may include removing reports saved in their private folder. Where this is now possible running a SOQL query, what you may run into is the inability to delete because it’s being used in a dashboard component. Now this is solvable using a SOQL query which will return a list of dashboard components that uses the report as a source. The idea Show what dashboard component is utilizing a report was delivered (3450 pts).
Processes Can Execute Actions on More Than One Criteria - This is a nice new feature of Process Builder. Before this, when a record met your defined criteria, the action was executed on and the process stopped. Now you can select whether to stop or evaluate the next criteria. This makes it nice to build multiple scenarios in one process and move onto the next regardless if the previous criteria was evaluated as true. I built a process recently in a sandbox so that I could have a field update depending on the stages of an opportunity and it was nice to be able to build all criteria in one process. There were a few delivered ideas for this:
- Process Builder: Allow choice to let criteria execute simultaneously (430 pts)
- Process Builder to handle multiple decisions evaluating to true in one process (270 pts)
- Process Builder - next decision box for true (1070 pts)
Change a Record’s Owner - On the go a lot and need to delegate ownership to others? If you have the “change record ownership” permission the new ‘Change Owner’ action will now appear in the action bar on Salesforce1. This works on most standard objects plus custom objects but it’s worth noting the new owner needs to have at least ‘Read’ permission on that object. The idea called Change record owner in Salesforce1 was delivered (8240 pts).
There’s a lot of good suggestions continuing to come out of the IdeaExchange and it’s great Salesforce continues to take them seriously. Do you have other favorite ideas delivered in this latest release I didn’t mention? Please feel free to comment below, on our Facebook page, or directly at me on Twitter @LeiferAshley or in the Success Community.
The release cycle for Salesforce’s flagship marketing tools, Marketing Cloud and Pardot, are not tied to Salesforce’s general thrice yearly release cycle, and with the Summer ‘16 release they have almost entirely disappeared from the release notes. There’s not a single mention of Pardot, and Marketing Cloud gets a nice little blurb about what it is without even a link to its own, separate release page. So does this mean we shouldn’t be talking about the evolution of these systems in the same breath as the overall platform release? Not at all. In fact, the Salesforce release cycle provides us with a structured opportunity to review all of the things we use in conjunction with Salesforce, and marketing applications are high on that list for many customers.
Marketing Cloud has a release schedule that is established on a year to year basis and published in detail in advance. You can also sign up for notifications on these releases, which is a no-brainer if you are dealing intimately with the tool. For the purposes of this article I am going to focus on the May 2016 release.
Marketing Cloud’s May 2016 release was a hefty one, introducing the Marketing Cloud mobile app and an open beta for the new Email Studio and Content Builder features. It also included some major bug extermination, including fixing some issues with deduplication. And of course, what would any Salesforce product release be these days without a mention of Lightning? This is very interesting when it comes to the path for Marketing Cloud, because it indicates moving toward an experience of the product that is more consistent with the rest of Salesforce’s flagship Clouds. Marketing Cloud Connect becoming (“evolving into,” as the release notes put it) Marketing Cloud Lightning means the product we interact with looks and feels more like Salesforce and indicates to me a priority on making the integration more fluid. I’m excited to watch this evolve.
Pardot breaks from the release cycle model entirely, offering rolling improvements published on their New Features page, regularly emailed to customers in a nice narrative message with links to blog entries and help articles, and often displayed prominently upon logging into the system whether you ask for it or not. In the past month Pardot customers received two substantial goodies--Multiple Scoring Categories and a serious beefing up of the Competitor Monitoring feature.
In response to Multiple Scoring Categories: THANK YOU! This enables marketers to set up additional scoring schemes on top of the regular score, adding capacity to track prospects interest in something like different products a business sells or other non-mutually exclusive types of prospect nurturing. I know many nonprofit organizations use Pardot as well as businesses, and this could have a great use case in scoring against things like donations, volunteering and/or specific programs. With this feature Pardot is taking a big step forward in meeting the needs of organizations that fuel multiple business streams with one marketing engine (and one Salesforce org.)
Competitor Monitoring is basically a way to see how well your website is battling it out in the search term arena. While this isn’t a feature that gets a lot of hype against all the other bells and whistles of the platform, that might be changing. Pardot just doubled the set of metrics covered by the report, giving marketers real ammunition for making content and SEO decisions without crunching lots of numbers.
Summer ‘16 Marketing Implications
If you use any other marketing application in conjunction with Salesforce, make sure you are keeping up on releases and improvements to those products as well as the overall Salesforce release notes. This way you can avoid any surprises when new Salesforce features have implications for your marketing integration and you don’t miss out on any opportunities to take advantages of release features that could add power to your marketing activities.
Many marketing applications (including Pardot) leverage Visualforce pages embedded in Salesforce detail pages for Leads, Contacts, Campaigns, and other objects to give non-marketing users insight into the good work you are doing delivering leads and nurturing customers. For some this has been a barrier to entry for Lightning Experience. In the Summer ‘16 release notes Salesforce tells us this may be less of a problem, in some cases. So spin up one of your extra sandboxes and see what this means for you.
Also, the ability to automatically get geocodes for addresses in Salesforce might mean you can leverage this information in your marketing application (depending on the tool you use, how it syncs data, and your use case.) I’m excited to see what all the creative marketers out there find to do with this wealth of information.
It is also a good idea to review the evolving security and identity features to make sure they don’t affect how your marketing applications or marketing users access Salesforce. While I’m not seeing any specific red flags in this release, this is always an important area to assess.
Do you see any other features in Summer ‘16 that are of special importance to marketers, or have comments on the latest goodies from Marketing Cloud and Pardot? Please feel free to comment below, on the Salesforce Success Community, on our Facebook page, or directly at me on Twitter @ifitfloats.
Grab a cold drink because it’s time for hot fun in the summertime with these Summer ‘16 enhancements focused on service. Hopefully you have been following along in our series of posts (Rapid Reaction, Sales, Developers, Financial Services) related to this milestone 50th release and take note, there’s more to come. Here are some highlights selected from over 30 pages of service-related release notes.
Salesforce Console For Service
- Set up Service Cloud Features in a Flash with Launch Pad Templates what? This is a major timesaver and what hopefully indicates an increased focus on templates for other areas of the platform. System admins will be able to rapidly deploy and validate Service Cloud features with a few clicks. This release provides three templates that provide the most popular Service Cloud features, including console configurations with reports and dashboards necessary for a productive service organization.
- Responsive list hovers yes, please. Spring ‘16 introduced tab hovers and now users can display the details of a row in a hover, without having to open the record. Hovers deliver the goods without clicks.
Work Orders, Milestones and Knowledge
- Attach Articles to Work Orders indeed. Work orders and work order line items were introduced in Spring ‘16 and you will now be able to attach Knowledge articles to them to enable users to quickly locate information. “Knowledge has a beginning but no end.” ~Geeta S. Iyengar
- Milestones are now available on work orders as well, allowing you to tie entitlement to work orders and track these important steps within your processes. Entitlement management was previously available just for cases, now you can specify whether an entitlement process can enforce milestones on cases or on work orders through the use of a new Entitlement Process Type field.
- Improve Article Suggestions on Cases will allow you to choose five case fields that will be used to suggest articles when closing cases. The concept here is that a search will suggest articles based on their content and any links between similar cases. The suggested articles are available in the Salesforce Console for Service and your portals when viewing existing cases and creating new ones.
- Management of work order hierarchies was enhanced with a couple of fields that make it easier for you to view and build out hierarchies of work orders and work order line items. The new read-only field Root Work Order lists the top-level work order in a hierarchy of work orders and can be added to work order page layouts to provide users a complete view of work order hierarchies. Similarly, the new Root Work Order Line Item field lists the top-level line item in the work order line item hierarchy allowing user to navigate the hierarchy.
This list is not exhaustive of all the service features in this monumental release and I suggest you peruse the release notes to view them all. Do you have some favorites that we didn’t mention? Please feel free to comment below, on the Salesforce Success Community, on our Facebook page, or directly at me on Twitter @sfdcclicks.
Like clockwork, it is time again to take a look at the new Salesforce release with a set of Financial Services sunglasses on. Sure, this thing is packed with tons of Lightning goodness but those who are true to the core can also rejoice.
Let's start with one of the newer "clouds" to join the sky in Financial Services Cloud.
For those who missed the bus on this one, Salesforce has two new industry specific clouds and in this case the Financial Services cloud gets some love in Summer 16. This new change allows for better visibility into relationships between Accounts, for example an accountant is both in his firm but also has a role on a household as the accountant of record. Reciprocal records to the rescue.
My love for person accounts is not very deep, but when they get some love from Salesforce (pretty rare) it is nice to see and deserves some attention. This enhancement brings back person accounts in search results if both the Account and Contact contain the search term which was not the case before. No more missing person (Accounts).
Two-factor authentication is a great feature bringing another level of security to Salesforce, but with all things Salesforce, sometimes the end user gets the dirty end of the stick. This new Summer 16 feature allows administrators to rescue a locked out end user by generating that one time code if they can't access their secondary device. Being an awesome admin just got easier.
Yes, I know this was already mentioned in Justin's rapid reaction post, but I cannot crow about this new feature enough, so let's do it again. This new feature solves the many to many problem of Contacts and Accounts and once enabled brings a new related listed called Related Contacts addable to the Account page layout. By default your Contacts will already be there, but not your Contact Roles, so those will need to be migrated. It will allow you to have Contacts related to many Accounts with multiple roles and indicated as a direct or indirect relationship. Confusing to start, but will help a lot of people who struggle with the primary account restriction.
What is Pledge 1%
Pledge 1% is an effort spearheaded by Salesforce, Atlassian, Rally for Impact, and Tides to accelerate their shared vision around integrating philanthropy into businesses around the world. Pledge 1% encourages and challenges individuals and companies to pledge 1% of equity, product and employee time for their communities, because pledging a small portion of future success can have a huge impact on tomorrow. Pledge 1% offers companies turnkey tools and best practices, making it accessible for any company to incorporate philanthropy into their business model.
Why We Made the Pledge
We announced that we have joined Pledge 1% because from inception we have always been inspired by the 1-1-1 model spearheaded by Salesforce. We have decided to take the next step and officially leverage the Pledge 1% platform to give back to the community at large. We are pledging 1% of our time and 1% of our product to fulfill our obligation to being a Pledge 1% company.
“We built Arkus to help make a positive impact on society from the beginning, following in the footsteps of leaders such as Salesforce. We believe it is important to make this commitment through Pledge 1% and built it into our organizational DNA” - Jason Atwood, COO & Co-Founder
As a Preferred Partner of Salesforce.org we are consistently working with nonprofits who make such an enormous impact on this world. We wanted to ensure that we continue to give back to these organizations while empowering them to push their missions forward in making a positive impact on society.
How We Made the Pledge
We have made the pledge (for now) on two important fronts:
- Since inception in 2010 we have provided a deep discount for our professional services to all registered nonprofits.
- We are donating 1% of our time to nonprofits in the local area. In 2015 we started holding Arkus Pro Bono days. These one day workshops are meant for any local nonprofits to come to our office for a day of learning, networking, and talking to our Salesforce experts about any technical issues they are having, strategic planning, or general information gathering about usage of Salesforce at their organization. Going forward we plan on doing these two to three times times a year.
We are going to continue our dedication to Pledging 1% via the numerous resources and toolkits that Pledge 1% provides to us as an organization. We are extremely excited about continuing to work with organizations that are helping to make the world a better place. This is only the start for us, we are looking forward to giving back to this thriving community and adding even more value in the future.
To learn more or to take the pledge, please visit www.pledge1percent.org.
Summer ‘16 features an expansion of limits (for a new set of editions). Limit expansions have been on the rise over the past three releases, and most recently we’re seeing a relaxation on sandbox limitations that may hinder environmental setups or scaling for large teams. Read on to learn about the coolest features and limit increases that Summer ‘16 offers developers!
Moarrr Sandboxes 2.0!
With the new “Lightning” editions and a slight price bump, some limits have also gotten a bump. The biggest win for developers is the increase in the number of developer sandboxes available for Professional, Enterprise, and Unlimited Editions. Enterprise Editions benefitted from having 25 developer sandboxes included in the Spring ‘16 release, but that wasn’t enough for developers. In Summer ‘16, developers receive 1 partial copy sandbox for Enterprise Edition orgs! No longer do developers need to maintain a set of Excel spreadsheets or execute Apex to create sample data when creating a new sandbox.
If you love cloning records or cloning users, you now can enjoy cloning sandboxes! This feature allows developers to create a new sandbox in production, but instead of cloning from the current production instance, developers are able to select another sandbox to use as the source of their clone! This can be a huge time saver if you have a large development team, or wish to create a separate environment for users to perform testing on a new feature.
Consolidating Asynchronous Limits
Prior to Summer ‘16, there were different limits based on the asynchronous action type, and there were 4 different ways to accomplish this! The two that I often use are @future methods and Database.executeBatch, and the limits were a bit of a drag, especially for the @future methods. Salesforce has wrapped all of these into a single asynchronous limit of 200 calls, which means that developers leveraging @future methods have a 4x increase to their existing limit!
Increasing Limits Across Namespaces
Salesforce has had a limit that previously allowed for only 10 namespaces of code to be invoked in a single transaction, which in effect means that only 10 managed packages would be allowed to execute during a single transaction. For orgs that have a lot of apps installed or have a robust app with many separate packages installed as features, this can produce a headache or even block the use of app offerings. This limit has now been removed (read: shifted) in favor of a scaling limit based on 11 times the number of per namespace limits. This means you could have more than 10 packages execute in a single transaction.
Do you have a favorite Summer ‘16 feature? Did we include it or miss it from our post? Let’s talk about it below in the comments, via Twitter @RogerMitchell, on our Facebook page, or in the Success Community!