Tag

updates Archives - 501Partners LLC

Nov 24
0

Upgrading to NPSP 3.0

By | CRM & Salesforce

To upgrade your Salesforce to NPSP 3.0:

1)  Create a new trial and choose “Pre-Configured for Donor Management.” (Note: you will need to create a different login than the current Salesforce, but it does not need to be a real email address.)
2) Call or email your Salesforce representative to request your grant be pointed to the new Salesforce instance. (If you don’t have contact info for your rep, you can email crmdonation@salesforce.com) They will ask you for the Organization ID of both the old instance and the new one. You can find them by going to Setup –> Company Profile –> Company Information –> Salesforce.com Organization ID (see below).
image
If they ask you to upgrade your old instance to NPSP 3.0, 501Partners can do that after we create the customizations without messing up your data.
Nov 17
0

Looking Ahead to Spring ’15: Salesforce Maps Feature & How To Opt Out

By | CRM & Salesforce

Even though Salesforce’s Winter ’15 update has barely begun its roll-out, we’ll be turning our attention to February’s Spring ’15 offering for the purposes of this blog. Yesterday, Salesforce notified administrators that the Spring ’15 version will include a Maps feature. Included in the email were directions for opting out of this service, which might be the preferred way of dealing with this change for some organizations. Here, we will describe the nature of the change and provide you with instructions for turning off the Maps feature:

Read More

Nov 11
0

Salesforce Update: Disabling SSL 3.0 Encryption

By | CRM & Salesforce

Recently, Salesforce announced that it would be disabling SSL (Secure Socket Layer) 3.0 due to a security vulnerability published by Google’s researchers. This is likely not something that will affect your Salesforce instance significantly, but we wanted to keep everyone up to date on the changes. Before we go any further, here is the statement from Salesforce about why this disabling is occurring:

“At Salesforce, trust is our #1 value, and we take the protection of our customers’ data very seriously. On October 15, Google researchers published details on a security vulnerability (CVE-2014-3566) that affects the Secure Socket Layer (SSL) 3.0 encryption protocol, also known as “POODLE,” which may allow a man-in-the-middle attack to extract data from secure HTTP connections. Although the vulnerability is somewhat difficult to exploit, to further protect customers, we will be disabling SSL 3.0 to fully address this issue.”

Here’s what this change means: Once Salesforce disables SSL 3.0 encryption, all channels which connect to Salesforce will need to use TLS 1.0 Encryption (or higher). There are three channels that connect to Salesforce via encryption:

Read More