ForceGuru

Sep 14, 2016

Winter 17 is here and we all are excited about it!Here are some new features which I like when I took a glimpse on release notes.->Lightning
navigation Menu is changed from vertical to Horizontal.

-> All
custom apps created in classic view will be supported. But now their
description is also available so we might need to add description in missing
apps so that they look good and this is an optional step.

-> After your users create,
edit, or clone a record in Lightning Experience, they can create another record
using the Save & New button. The Save & New button lets users create
records repeatedly without leaving their spot in the app.

-> Field
Level help is now available in Lex and SF1

-> You can no take ownership
of multiple lead at once. From the queue list view, your reps can select all
the leads (up to 200). When they click Accept, they’re committed
and those leads become theirs.

-> Global picklist now
available in Lightning experience and we can now send them with change set from
Sandbox to production.

-> Now the Open CTI is
available in Lex. In the bottom you can access the CTI.

-> Your code can use merge fields to construct the bodies of Apex
callouts to named credential–defined endpoints. Those merge fields now support
theHTMLENCODEfunction
so you can escape special characters, such as underscore (_) and ampersand
(&), in the merge fields in callout bodies.

When your users expand or
collapse a section in record details in Lightning Experience, the section stays
that way even after visiting other areas in Salesforce. This change helps users
scroll through a record faster, showing only the information they care about.For example, in Lead details, a user collapses
the Address Information section and expands the Additional Information section.
The next time the user views a lead’s details with the same layout, those
sections remain collapsed and expanded, respectively.

-> Confirmation messages that appear after your
users create, edit, delete, or clone a record successfully from a related list
in Lightning Experience and Salesforce1 have changed. The messages include the
record name for more context. Also, after your users create a record from a
related list in Lightning Experience (not Salesforce1), the popup message
includes a link to the record for easy navigation.

-> Navigate from a Lightning
Component to Another (Beta)

To navigate from a Lightning component to another, specify the component
name usingcomponentDef. This example navigates to
a componentc:myComponentand sets a value on thecontactNameattribute.

-> Opportunity owner can edit
the probability of the opportunity without switching in the Salesforce Classic
view.

-> The
time window to quick-deploy your validations has expanded from 4 days to 10
days.

-> Apex test suites are now accessible through the
Metadata API, using the ApexTestSuite type. You no longer need to recreate test
suites in each of your testing orgs. Instead, create an Apex test suite once
and deploy it and its test classes to each of your test environments. Now you
can focus on more important things, like whether to call your new test methodwhatTheHeckIsWrongHere()orpleasePleasePleaseReturnTrue().

If there are any which you like the most, please list them as comment.

Apr 18, 2016

Communities is becoming a necessity to manage customers and partners and why not, it's easy that way isn't it? We (at Briskminds) are currently handling around 10 active projects where we need to implement the communities, but of-course we were also new to it few months back.

We've followed some simple steps to enable and use it, and would like to share that with my fellow community members as well. Let's explore more how we can enable and customize our community.

How to enable communities

Go
to Setup > App Setup > Customize > Communities > Settings

Enable
the checkbox "Enable communities"

Register
For Domain

Once
enabled the communities it will ask for the domain name, show in picture. Once
registered for the domain you can now create your community, by clicking on
“New Community” (Customize | Communities | Manage Communities,
then click New Community) button.

Allowing
profile to login in community

Once
you create new community then click on edit.

It
will show the screen as displayed in picture (please remember this, as we will
refer the same Edit again and again)

Click
on “Members” tab

Once
clicked on “Members” tab, it will show the screen as displayed in picture

Here
you can enable profiles and give permissions to users

If
you are creating a community user then make sure profile assigned to that user
is listed here (in “Selected Profile”) else user will not be able to do
anything with the email which will be received after new user creation.

Allowing
Tabs and Pages

Click
on “Edit” against your community

Now
click on “Tabs and Pages”, it will show the screen displayed in picture

Select
“Use Salesforce.com tabs” (let’s not dive into using site.com as it is a
separate topic)

Then
you can select the tabs which you want to show to the community users

Note
– First tab selected will be the landing tab

Custom
Branding

Click
on “Edit” against your community

Now
click on “Branding”, it will show the screen displayed in picture

From
here you can customize your headers and footers (formats are mentioned in
picture) (which will be displayed on the native screens, and depends if you’ve
applied on custom pages/tabs) and color theme to the community

Customize
Login Page

Click
on “Edit” against your community

Now
click on “Login Page”, it will show the screen displayed in picture

Now
you can give your company logo in login page. Whenever user open your community
link, then you can show your company logo in header and show your content in
footer.

If
you need to completely change the login page to your visualforce page then we
need to follow some more steps mentioned below :

(i)
Create an apex class and visualforce page you want to show as your login page.
Keep it simple for now.

Feb 22, 2016

I think most of you (probably all) are aware
of TRAILHEAD!! An awesome tool design by a great team of Salesforce to help new and experience developers. It helped me a lot to get over lightning concepts and I hope you must have your own favorite list.

Due to this one can easily get better
understanding of Salesforce and will sort out many puzzles which may be running from a long time in mind. As we are all aware that how easy is to use trailhead, so these new modules
just add "Cherry on the Cake". In these modules you will find information related
to every aspect of Salesforce whether it is their Service, Security or their
core values. Now it is easy for me to train newbies who joins my company as fresher. It tool a lot of initial headache and made my life easy. Am pretty sure it will not take much time even if anyone who doesn't know about Salesforce goes through it.

Best part is the security, which is a big concern now a days (even from long). Salesforce has a lot of security protocols which ensures safety of your data. I think if I remember correctly not even Salesforce internal members can see your data until you authorize them to do so. Would like to add one more point here, that there is a link to create free developer account and more details about
different modules including the newly added IOT cloud.

Jan 3, 2016

I saw this on many developer forums and stack exchange and many others are facing the same issue of how we can enable of all IPs in our organization. For developers this a big problem, as every-time you share the credentials with anyone you've to whitelist their IP so they can login without sending any security code to emails.

So here is sweet and short solution to it. You simply need to create a home page component (custom link) and use this code there :

On home page layout you've to use this custom link. Make sure your browser is allowing the pop-ups as once you click on this link just sit back and relax as it will continuously calls the page and add IPs to your org.Also in code I've "https://ap2.salesforce.com", please make sure you change it your base URL of the ORG (rest URL remain as is "/05G/e?IpStartAddress=' + startingPoint + '.0.0.0&IpEndAddress=' + endpoint + '.255.255.255&isdtp=vw',600,600")