The Lightning Experience FAQ (last updated October 2016) includes:
Q: Can I still use Salesforce Classic?A: You have the choice of when
you want to move to the new Lightning Experience UI and which users
you want to migrate. You can continue to use Salesforce Classic as
long as you like, and we will continue to support the Classic UI.
The short answer is you will be able to use Einstein with classic but you wont be able to use the lightning components that are provided out of box by einstein package.
You can still access functionality like seeing Lead Score on the record and automatic association of activities but since major of the analytics and the insights prediction UI is lightning ...
In LEX, salesforce uses <a> tags with an href attribute to navigate to records.
Although rather than using href="/<id>", it is href="#/sObject/<id>/view"
I personally can't say for sure whether or not the way the LEX app handles url fragments will be subject to change, or whether developers can safely use this pattern directly for ...
Salesforce has no plans to drop support for classic. It will be around for a long time to come. You'll notice that PDFs are still rendered in classic, that lightning components can be used in classic and that visual force pages can be used in a lightning container in lightning pages. There are far too many orgs that have a lot of money invested in custom ...
For now, the plan is to switch everyone to Lightning by default (except for certain unsupported editions and license types).
The Classic UI will still be available:
After the critical update is activated, all users still have access to Salesforce Classic. Every week, starting the Sunday after Lightning Experience is turned on, Lightning Experience-...
Salesforce.com has not announced any plans to remove Classic at this time. I would expect that salesforce.com is trying to get rid of Classic as soon as possible, but they will not be able to do so until they can convince 100% (or very close) of their major clients to move to LEX entirely. This means that they need to have 100% feature parity with Classic, ...
The Rule of thumb is permission set extend the access of profile and do not restrict.
1.In first scenario since profile already has access which means permission set cannot disable as permission sets are meant to extend the behaviour
2.Second case its obvious .
If you want to restrict the behaviour for a user ,then disable at profile and do not assign ...
So, my question is what is the correct approach to developing an app for Salesforce in team?
In good old days, we used Developer sandboxes for developers, either same or individual and then migrate the changes to upper environments.
But now we have Salesforce DX.
I mean is there a way to have a different versions of environment for everyone and then ...
yes, starting from Summer '19 it is possible to add LWC to VF page via lightning out. Read documentation
Adding a Lightning web component to a Visualforce page is a three-step process.
Create and reference a ...
I did some research on this and I found out the answer for My question. I am sharing all the findings below in case someone need to refer this in future.
1) I got some interesting detailed explanation on this from Link. Click_here
, I am copying some important facts from this as below
Salesforce Classic: It's the platform which we are using from long time ...
For some custom things, like Visualforce pages, you can get away with staying in Lightning; it plays pretty well with Visualforce. However, there's a large laundry list of things not yet available in Lightning Experience (LEX). In those cases, you must switch to Classic in order to see or use the feature. The limitations are outlined here.
You're absolutely ...
In the Lightning now tour, the PMs said this is coming with the Summer17 release, where classic access can be removed w a permission set.
It's now listed on the roadmap doc here
Select which Lightning Experience users can access Salesforce Classic
As the Set Up Users for Lightning Experience documentation explains there is a "Lightning Experience User" permission that you can ensure is unchecked on the profiles (and permission sets) you choose for the newly invited users.
After you enable Lightning for the org, you have to grant permissions to your users in their Profile or in a Permission Set. Make sure the "Lightning Experience user" permission has been granted to your user.
To enable lightning to a profile, go to that profile and search for 'Lightning' and turn on 'Lightning Experience User'. This should help:
With the use of Lightning Out we can definitely build Lightning components that be accessed inside Salesforce (embed in Visualforce, not an iframe) or even outside of Salesforce.
I think most obvious issue with Authentication, as components run outside of Salesforce. So, to use it we may need to setup Connected App with OAuth.
2nd thing, could be the ...
Now with Summer'18 the beautiful pattern of
seems to be broken by Salesforce. So as an answer: it seems you can't use it anymore. However using js-handler for simple things such as an links feels ridiculous.
I think we need a new question searching for alternatives.
No. Lightning component won't work without setting my domain.
There are many reasons that My Domain is required and lightning component will not work unless you set a domain.
Useful link -
Knowledge Article - My Domain Lightning Components
I think Salesforce also have a limit on a max date you entered in date-time / date field.
Maybe it's 4000 year, so you have to create text field to save the date greater than 4000 years.
From documentation: Maximum date and year values accepted by Salesforce:
Salesforce can accept dates between Jan 1, 1700 and December 31, 4000.
No, it's not possible. What you can is:-
Customize the buttons on the list view i.e in your case, you can add a button near the new program button.
Add or remove Custom buttons In Aloha
For standard objects
i. From Setup, click Customize | then click the object you want to modify | click Search Layouts.
For custom objects
i. From Setup, click ...
The limits are always the same. However, many governor limits are flexible. This means that if the server thinks it has the available resources, it can choose to ignore or extend the CPU timeout value to attempt to allow the transaction to finish. In theory, a transaction can get up to about 20,000ms or so before it is definitely terminated (and even higher ...
I would be happy to be wronged here but to the best of my knowledge, your VF pages will work in lightning as well, it is just that their look n feel would be classic-like. The only problem is the navigation url of yours /apex/PriLogin won't work in lightning the same way as that of the classic.
as per the lightning trailhead
This feature is available in Summer 16 release .I just tested in one of the pre-release org on gs0 and this is how it looks
Edit the Home page layout
Kindly note its only in Summer 16 release .So if you have a sandbox you can see this now .
I dont think there is a direct method to do it. With the same requirement I called an APEX @AuraEnabled methoed and used sBoject.Clone and then I used force:createRecord to show the screen. Please see the salesforce documentation for this
The quick action mainly introduced for Lightning Experience and mobile
app. Yes, you are right, in classic you are limited to adding a quick
action to chatter.
In Lightning, You can add a quick action on detail page layout by
adding it to Salesforce Mobile and Lightning experience action.
You can also add a quick action to a list view of Object record. ...
Leave the JS button as is, and it'll only show on the Classic layout. Create a Lightning Component Quick Action which will read the value from the record and either display the appropriate message or redirect.
Unlike in the flexi pages(Lightning app builder pages) when you use components in an app, Your app needs to extend force:slds.
Using the Salesforce Lightning Design System in Apps
The Salesforce Lightning Design System (SLDS) provides a look and feel that’s consistent with Lightning Experience. Use Lightning Design System styles to give your custom stand-...
I don't know if there's any standard way to do so, but you can utilize an approach here in your Extension's constructor to identify if the click was from New or Edit.
When you click on New button, that signifies that you are creating a new record and that it won't have an Id yet, whereas for Edit there will be always one. So checking that in the Extension ...
Doug Ayers has a free, open-source application available called Convert Notes to Enhanced Notes. Its purpose is to do this conversion process from classic Notes (sObject Note) to Enhanced Notes (sObject ContentNote).
You can install the app in the form of a package or source code.
I have no affiliation with this application.