Escolar Documentos
Profissional Documentos
Cultura Documentos
FAQ
WHAT IS LIGHTNING?
Lightning is:
This document focuses primarily on the Lightning Experience app for the Desktop.
OVERVIEW
II
CUSTOMER ENABLEMENT
III
FEATURES
IV
CUSTOMIZATION
VI
CUSTOMIZATION
VII
PARTNERS
GENERAL FAQ
I OVERVIEW
Overview
II CUSTOMER ENABLEMENT
Enablement 1
Existing customers with sandboxes can access the Lightning Desktop trial in their
sandbox
Existing customers without sandboxes can enable the Lightning Desktop trial to a
specific user(s). It is recommended that admins enable a profile perm for their own
profile and try it before enabling trials for others. Reference the Trailhead (which will
be live end of August) to learn how to enable permissions for their edition.
For prospects who want a trial: After Winter 16 is released, all new trials will be in the
new Desktop experience.
For prospects who just buy without a trial: Lightning Desktop will be enabled by default
Note that Service Cloud trials will not have Lightning Desktop enabled by default but
will be able to enable it in the set up.
Note that Service Cloud trials will not have Lightning Desktop enabled by default but will
be able to enable it in the set up.
III FEATURES
FEATURES
IV CUSTOMIZATION
Customization
TECHNICAL SECTION
V
How will non-sales users (like service) leverage the new UI?
Customers will need to consider the use case before determining whether or not the
Lightning Experience is right for it. While sales reps can run their business in the new
Lightning Desktop in Winter 16 release, Service Cloud users will be able to use the
Lightning Desktop more extensively in future releases and might choose to stay in Classic
(Aloha) UI until then. The good news is that customers can enable the new UI at the
individual user level, allowing everyone to work with the best tools for their needs. Keep
in mind, any sales user who needs to access service objects other than cases (cases are
available in Winter 16) will be able to do so using the switcher functionality and vice versa.
This is recommended if they do this only occasionally. For Sales users who are blended
agents and work in full sales and service objects daily, it may be best to stay in Classic until
all of the service objects are in Lightning.
VI CUSTOMIZATION
Will Lightning Desktop support Visualforce?
Yes, with some detailed caveats. When a VF created in Aloha is viewed in Lightning
Experience, it will still have the old UI. Customers and partners will want to update the UI
to match that of the Lightning UI to be consistent. The Lightning Design System makes this
possible. For this reason, VF is in beta for Winter 16 (198).
Another example: You will no longer have the option to hide the header or sidebar. The
Aloha header and sidebar will always be suppressed in Lightning Experience. The Lightning
Experience header and left nav menu will always show. No code changes are required for
this behavior. Viewing the VF page in Aloha will behave the same as it does today.
VII PARTNERS
Partners
How does this impact our AppExchange apps or partnerbuilt solutions that are already installed?
Our ISV partners will need to rethink how their package works in this new UI. Changes
such as the new navigation pattern will have impacts on how their apps work. For example:
How does the page respond when the left nav is open?
We started a pilot with 100 partners in Mobile1 in June to allow them to test existing apps
and help us identify any major issues. No major issues were found outside of the known
restrictions of the new Lightning Experience. All partners will have access to the Lightning
Experience when GS0 is deployed.
For Dreamforce we aim to have 100 Lightning Ready applications. The requirements
of making your app Lighting Ready are that it just be fully functional in the new Lightning
Experience, must be responsive to the left nav opening/closing, and we have asked
developers to make styling changes to better align the look/feel with the new UI.
Apps do NOT need to be rebuilt in Lightning; partners will make these changes to
their existing Visualforce apps. There will be a qualitative review process by the UX and
product teams to ensure the app functions and aligns with our new UI. Partners who
meet the criteria will have a sash on their listing on the AppExchange that shows they
are Lightning Ready, and customers will be able to filter for these apps.
If a customer uses an app that is not Lighting Ready, they may experience issues in the
new Lightning Experience. In that case, they would need to switch back to Aloha to use
the app as it works today.
To assist in this effort, we are publishing the Salesforce Lightning Design System, which
is formal documentation around all the styles that make up the Lightning Experience
across all form factors. The SLDS is available to all partners when GS0 is deployed and
will be made GA through an open-source project on GitHub for Dreamforce. SLDS can
be used to design apps built on the Salesforce1 Platform as well as on other platforms.
(SLDS FAQ) You will need to log in with username: landmark, password: theramp.
Until there is further feature parity with Aloha, there are some partners whose apps
will not be able to be used in the new Lightning Experience, such as apps that leverage
person accounts or s-controls. These partners will need to decide whether to wait for
the features or they may need to re-architect if features are not planned to move into
the new experience.