Visualforce page to embed the flow on

This post is part of a series on building a replacement for stay-in-touch using visual workflow

The visualforce page is very simple, no controller required. It is designed to pull the contact ID from the query string (the URL).

This help article shows how to embed a flow in a visualforce page, and it looks like

<apex:page>
  <flow:interview name="MyUniqueFlowName"/>
</apex:page>

This help article shows how to set flow variables from a visualforce page, which then looks like

<apex:page>
    <flow:interview name="flowname">
        <apex:param name="myVariable" value="01010101"/>
    </flow:interview>
</apex:page>

Finally, this article shows how to pull parameters from the query string into a visualforce page, which looks like

$CurrentPage.parameters.parameter_name

So, putting it all together, your visualforce page would look like

<apex:page >
    <flow:interview name="Replacement_for_Request_Update">
      <apex:param name="vaContactID" value="   {!$CurrentPage.parameters.cid}">
      </apex:param>
    </flow:interview>
</apex:page>

No controllers required!

 
7
Kudos
 
7
Kudos

Now read this

checking for record access in visual workflow

the UserRecordAccess object “Represents a user’s access to a set of records”. in apex, you can query this object to determine if a user can view, edit, delete, share, or transfer a record. SELECT RecordId, HasReadAccess,... Continue →