Sign in
 
HomeOnline20132010Other VersionsRelated ProductsLibraryForumsGallery
TechCenter >
> 
> 
Standard workflows does not work for Extranet zone

שאלה Standard workflows does not work for Extranet zone

  • Thursday, October 14, 2010 12:00 PM
     
     
    Sign In to Vote
    0

    Gentlemen,

    I have got an issues related to the standard SharePoint workflows’ forms (built with InfoPath).

     

    There is a portal leveraging standard review and approve workflows (http://portal). The portal have been published for external users (via extending web application, http://portal.company.com). Everything works fine except for workflows. I can open and view existing tasks but cannot complete them – an error dialog appears saying that the form cannot be submitted. In logs I can see that the forms are trying to submit data by internal URL and not the public one.

     

    Is workflows functionality supported for zones other that the default one? Probably I have missed something?

     

    I am using SharePoint 2010 Enterprise. Microsoft Forefront is used for external users authentication.

     

    Thanks,

    Dmitry Rogozhny.

     

All Replies

  • Thursday, October 14, 2010 4:58 PM
     
     
    Sign In to Vote
    0

    If you customized the forms with InfoPath, then they need to be published to the zone where they're being used.  Forms can't work across zones due to their references.  Did you customize the forms, or was the entire solution completely OOTB without customization?

    Workflows work across zones, but InfoPath forms do not.

    SharePoint Architect || Microsoft MVP || My Blog
    Planet Technologies || SharePoint Task Force
     
  • Thursday, October 14, 2010 6:19 PM
     
     
    Sign In to Vote
    0

    Hi Clayton,

     

    Thanks for your response.

     

    I am using the standard SharePoint 2010 collect feedback workflow. I haven’t done any modifications to it.

    If I have a task created in a workflow I can view it but cannot submit any changes (i.e. complete, reassign, add comments). I assume this is because task forms are InfoPath forms. Because this is a standard SharePoint workflow I am not able to publish forms to another URL.

     

    I was wondering is there anything I can do in order to make it work?

     

     

    Regards,

    Dmitry Rogozhny.

     
  • Thursday, October 14, 2010 11:08 PM
     
     
    Sign In to Vote
    0
    I haven't encountered this, so I don't currently have a solution.  I'm surprised that this becomes an issue when extending the web app.  My suggestion is to try building a test workflow while connected to the site on the extended web app, then see if it works.  If so, then you may just have to build solutions that leverage task forms on the extended side.
    SharePoint Architect || Microsoft MVP || My Blog
    Planet Technologies || SharePoint Task Force
     
  • Monday, October 18, 2010 5:13 PM
     
     
    Sign In to Vote
    0

    Clayton,

    I have tried to associate a new worfkflow with the library using the external address but it didn't work. In order to add a workflow one need to specify parameters presented by an association form which is InfoPath form and it tries to connect by the internal address as well.

    I believe a re-publication using the public URL would work for custom InfoPath forms. It does not work for standard workflows though (which is a really strange behaviour).

    I will try to further investigate, for now it looks like a SharePoint/InfoPath bug though.

     

    Thanks,

    Dmitry Rogozhny.