Did you know that AppExchange packages are apps customised for Salesforce to extend the existing Salesforce features? They are intended to cover more sales processes, administrative processes and more in different industries.
Where will you stand with the Lightning Experience rollout if you have AppExchange packages installed in your Salesforce instance? What precautions should you have in place to ensure that these AppExchange packages are not affected during the Lightning Experience rollout?
Take a breath and don’t worry!
Salesforce will provide some guidance on “How to Handle This” use case when you run the Lightning Readiness Report. If you haven’t already check out our previous Lightning Readiness Report blog here.
Whilst Salesforce have already quoted that they support AppExchange packages in Lightning Experience, it is entirely up to the publisher (creator of the App) to release a Lightning Experience supported version.
If the package does not support Lightning Experience, all the related buttons, links, and Visualforce pages in the package will NOT:
- Work in Lightning Experience OR
- Be visible to users
- You should ensure that the packages you have installed into your instance are supported in Lightning Experience. You can do this by visiting the AppExchange listing or contacting the publisher. Example of an App that supports Lightning Experience, RIO Inventory.
If one or more of the installed packages in your instance is/are not supported, you will need to check if the buttons, links, and Visualforce pages are working as expected. If NOT:
- Ask for a recommended workaround from the publisher.
- Switch back to Classic view only when you need to use the App (not ideal).