Video Screencast Help

Link to a certain part of a web form workflow?

Created: 15 May 2013 • Updated: 19 Jul 2013 | 5 comments


I have a web form workflow. Is there a way to link (I believe it's called a deep link) to a certain page within the application? Or do I have to start at the "Home" page every time?

Update: What if I wanted to link to a specific Model from a URL? For example, I have two models (A and B) and two URLS for my workflow. One URL links to A and the other URL links to B. Is this doable?

Operating Systems:

Comments 5 CommentsJump to latest comment

rhamner's picture

What about HomePage under account info? You'd need to create a new portal page with an iframe webpart to set as your home page.

jbrown's picture

Are you trying to expose a response action/page from the interaction section of a Dialog Workflow? Or force a web form project to start at a particular form builder component?

rhamner's picture

Nevermind, I see what you're asking.

I've done this in the past. What I've done is create a input parameter 'model' in the web forms project. You can either use a dynamic linked model component to route it to the correct model with the forms you want. With a bit more work you can make it so that it also can either go back to the main form or exit process when they exit a particular model.

If you're using 7.5 there's a new project type called web application. It can make 'entry points'  to individual models that each have their own .aspx page.

DannyTW's picture

I've done something similarto rhamner.

I set an input parameter on the project named startPage. Then, in the model, I have a Matches Rule component that checks to see what the value of startPage is. If it's "cal", then I have the "cal" path connected to the Form Builder component for the calendar, if it's "std", I have the "std" path connected to the Form Builder component for the standard form, etc.

The link that I then use looks like this: http://[URL]/[PublishedProjectName]/[EntryPointPageName].aspx?startPage=cal. In other words, the only thing that changes in the URL is that I add a query string to the end that tells the workflow what the value of the startPage input should be, which then directs the viewer to the correct form.

The only caveat here is that you have to make sure you initialize any data that is going to be used in that form before you hit the form. So with mine, I have a calendar that displays planned events, and the event data is all pulled in right after the start component. The next component is the component that tests the startPage variable. If startPage matches any of the recognized variables, the workflow gets redirected to the appropriate page. If it doesn't match (either because there was no query string given, or and incorrect value was entered in the query string), the workflow continues down the default path.