You need to sign in to do that
Don't have an account?
Stefan Fischer
Flow finishLocation behaviour in Salesforce1/Lightning
Hello all,
I try to call a flow via a visualforce page. The flow is started from an Account (button and action), submitting the AccountID and simply creates a new object linked to this Accout.
My goal is to go back to the Account page after the flow completed. It works in Salesforce classic, but not in Lighning and SF1. As soon as I click finish here, I am not redirected to the Account page, but the page just freezes. Only possibility is to click cancel then.
Any suggestions from you?
Stefan
This is how my code looks like:
<apex:page standardController="Account">
<apex:variable var="getAccountId" value="{!Account.Id}"></apex:variable>
<flow:interview name="Assessment" finishLocation="{!URLFOR('/'+getAccountId)}">
<apex:param name="AccountID" value="{!Account.Id}"/>
</flow:interview>
</apex:page>
I try to call a flow via a visualforce page. The flow is started from an Account (button and action), submitting the AccountID and simply creates a new object linked to this Accout.
My goal is to go back to the Account page after the flow completed. It works in Salesforce classic, but not in Lighning and SF1. As soon as I click finish here, I am not redirected to the Account page, but the page just freezes. Only possibility is to click cancel then.
Any suggestions from you?
Stefan
This is how my code looks like:
<apex:page standardController="Account">
<apex:variable var="getAccountId" value="{!Account.Id}"></apex:variable>
<flow:interview name="Assessment" finishLocation="{!URLFOR('/'+getAccountId)}">
<apex:param name="AccountID" value="{!Account.Id}"/>
</flow:interview>
</apex:page>
Did you have any success with this?
I have the same situation, my quick action calls a visualforce page which launches a flow. The actions within the flow are all executed correctly, but the re-direct isn't working, the user is just left with a blank screen with 'Cancel' and 'Save' at the top. If you press 'Cancel' you return to the correct record, but it's not ideal for the users to have to do this.