Workflow Soluiton

 View Only
  • 1.  Landing Page for multiple workflows

    Posted Nov 07, 2014 02:42 PM

    Hello, has anyone created a tab style landing page with some CSS?

     

    I will have multiple workflow projects for my users and would like to create a landing page for them.  Maybe have each workflow load in a frame or something when clicked?  The idea is to have a one stop shop where users will not have to navigate off the page.



  • 2.  RE: Landing Page for multiple workflows

    Posted Nov 07, 2014 02:55 PM

    I have created several with exactly that layout.  Basically you tie URLs to the "catalog items", and feed that into the iframe as a dynamic value.  

    MainPortal.gif

    I guess Connect doesn't do moving pictures.  Here's a link.

    And evidently neither does Dropbox.  Here's another link.

    http://atmaworkflow.files.wordpress.com/2014/11/mainportal.gif



  • 3.  RE: Landing Page for multiple workflows

    Posted Nov 07, 2014 04:59 PM

    so the side bar is basically a listitems component? then a dynamic model in the iframe based on what is selected on the left?



  • 4.  RE: Landing Page for multiple workflows
    Best Answer

    Posted Nov 07, 2014 05:31 PM

    Correct, list select on the left, then outside the form, an evaluation is done to build a URL for the iframe to load.  when the datastream returns to the form, the iframe loads whatever URL was built in the model.

    There are some notes, such as, if your list is tall enough to scroll, you'll want to return to the previous scroll position when you return to the form.  You'll want to load the first item in the list select's array into the iframe on initial load, things like that.



  • 5.  RE: Landing Page for multiple workflows

    Posted Nov 07, 2014 06:45 PM

    Perfect got the concept down!, now to apply a CSS to it



  • 6.  RE: Landing Page for multiple workflows

    Posted Nov 07, 2014 06:47 PM

    Give me a shout if you get stuck.  Also, make use of the "Input" parameters in your secondary web form projects.  You can merge input arguments into the iframe URLs in order to pass information to the secondary flows.

    2014-11-07_16-48-54.png

    for example, you could pass the userID of whoever is logged into your main portal by adding an input variable to the secondary form called "UserID", make it a text variable, and publish.  Then merge into your iframe URL so it looks like this:

    http://servername/projectname/StartDialog.aspx?UserID=[EnsembleSecurityToken.UserID]