SP 2010 Architecture(?) Question Involving Multiple InfoPath Forms and Doc Libraries. - InfoPath Dev
in

InfoPath Dev

SP 2010 Architecture(?) Question Involving Multiple InfoPath Forms and Doc Libraries.

Last post 02-27-2012 09:43 AM by csigler. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 02-23-2012 08:33 AM

    SP 2010 Architecture(?) Question Involving Multiple InfoPath Forms and Doc Libraries.

    I am working on a solution for specific users to submit a short form to request a service. I have the form done and am storing in a doc library. Via workflow the dispatch group is notified that the request is pending. I get how to do that. BUT what I just can’t wrap my head around is I want to retain the original short form request but have that info populate into a Long Form (which I have created and am storing in a different doc library) when the dispatcher opens something (the email, the link for the short form, etc.) then saved. I would also need a view/screen where the dispatcher could see the following:

    (ID#)......(Request)….....................................……..(Long Form)…............................................(task scheduled for)…..........................…(status)……..

    001        (short form id linked to original form)          (long form id linked to original form)...........(date from long form)...............................(status from long form)

     

    Does anyone have any suggestions or alternatives?  The people completing the short form will not have the authority to complete the long form. Also, a long form can be created by dispatch without first having a short form submitted.  I need to show on a screen visually where the request is in the process. 

     I am stumped.

    Corrie

     

  • 02-24-2012 09:16 AM In reply to

    Re: SP 2010 Architecture(?) Question Involving Multiple InfoPath Forms and Doc Libraries.

    I would recommend that you have the info all in one form and you create different views that open depending on who the user is (what group they are in) or what the status is.

    So a user that just submits requests only sees the short form

    then when the dispatch group opens it they see the long version

    you can also expsose various fields that are read only to the end user this way also like a status or comments that they can read but not edit 

  • 02-27-2012 09:43 AM In reply to

    Re: SP 2010 Architecture(?) Question Involving Multiple InfoPath Forms and Doc Libraries.

    *Creating a List, form has multiple views, can attach documents, works great BUT if you print the form it looks awful (and I have to print the form). SP header that cannot be turned off with print settings.

    *Creating a Library, form has multiple views, CANNOT attach documents, prints perfectly.

     Grrrrrr. I wish there was a THIRD container type that allowed for attachments and printed exactly like you had the form laid out.  Sooo aggravating!

Page 1 of 1 (3 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.