2.5.9.2 Publish a Browser-Enabled Form Template to the Server

Use Case Diagram

pict8d172562-e339-4aa2-a439-4f464138d6b9

Figure 10: Process for publishing a browser-enabled form template

Preconditions

  • The protocol client can connect to the protocol server that hosts the published Microsoft InfoPath 2013, Microsoft InfoPath 2010, or Microsoft Office InfoPath 2007 form template.

  • The user has permissions to create the InfoPath 2013, InfoPath 2010, or Office InfoPath 2007 form template on the protocol server.

Main Flow

  1. The user opens the InfoPath 2013, InfoPath 2010, or Office InfoPath 2007 client application.

  2. The user creates the form template in the client application.

  3. The user types the URL to the InfoPath 2013, InfoPath 2010, or Office InfoPath 2007 form template in the Publish Form dialog box. In this scenario the following protocols are used:

    • The FrontPage Server Extensions Remote Protocol [MS-FPSE] for getting website metadata, setting file properties, and performing file operations such as renaming.

    • The Windows SharePoint Services Collaborative Application Protocol [MS-WSSCAP] for document library operations.

    • The Webs Web Service Protocol [MS-WEBSS] for getting site URLs and column fields.

    • The Lists Web Service Protocol [MS-LISTSWS] to manage content types.

    • The Forms Services Feature Detection Protocol [MS-FSFDP] to detect the presence of InfoPath Forms Services on the server.

  4. The form template is uploaded to the server. In this scenario the Web Distributed Authoring and Versioning (WebDAV) Protocol: Client Extensions [MS-WDV] is used to upload the file.

  5. The Forms Services Design and Activation Web Service Protocol [MS-FSDAP] is used to browser-enable the form template.

Updating a previously published form template uses the same set of protocols and a very similar process.

List content types are used to publish a form template to a list (1) on servers running Microsoft SharePoint Server 2013 or Microsoft SharePoint Server 2010. For more information, see [MS-LISTSWS].