7

In current code we use something like:

<apex:outputLink value="/one/one.app#/alohaRedirect/apex/TestVisualforcePage"

Anyone knows how we can convert this so it works with the new lightning URL format?

I tried for example "/lightning/alohaRedirect/apex/TestVisualforcePage" or "/lightning/apex/TestVisualforcePage" but it does not work.

Thanks for your time!

6

The syntax /one/one.app#/alohaRedirect/apex/TestVisualforcePage is not dead yet and will continue to work. As stated here it's not recommended if there is an alternative, but sometimes there is still no alternative.

In one scenario on a current project, we have a CTI adapter that opens a screen pop in a new window, and we want the new window to pop open to a particular Visualforce page with the Lightning one.app wrapper around it, and pass parameters to the VF page. The CTI adapter does not have access to sforce.one or any Lightning events. In this situation we decided to use the alohaRedirect syntax because we simply could not find an alternative.

0

You can redirect using <apex:outputLink value="/lightning/n/yourVFPageName"/> and i have used like this and it works for me.

4
  • 1
    I am not able to reproduce this in my org with the new URL format enabled. – Charles T Mar 22 '18 at 1:52
  • 1
    I think what you're describing might only work if it's already a Tab. – Charles T Mar 22 '18 at 1:53
  • Yes i had a Visualforce tab earlier, but after removing the tab, i was able to access the page using <apex:outputLink value="/apex/yourVFPageName"/>. – Kumar Mar 22 '18 at 15:28
  • Yes if you're navigating from within a Visualforce context already you can access it that way. However if you visit that URL directly it will load without the one.app wrapper. – Charles T Mar 22 '18 at 16:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.