Features Specific to HotDocs Server and HotDocs Cloud Services

Every HotDocs Server or HotDocs Cloud Services implementation begins (in some sense) with HotDocs Developer.  HotDocs Developer is the desktop-based software application template developers use to create templates to run on HotDocs Server or HotDocs Cloud Services.

When creating templates for use with HotDocs Server or Cloud Services, template developers can use most of the same features as they can when creating templates for use with the desktop version of HotDocs. For example, Server or Cloud Services templates may contain related variables grouped into separate dialogs, dialog scripts that dynamically gray or hide variables, instructions for specifying the order in which dialogs are asked, and many other features. However, some features are either not supported or work differently in templates running on HotDocs Server or Cloud Services.

The following HotDocs Developer features are designed specifically for creating templates to run on HotDocs Server or Cloud Services:

• Component File Properties: Template developers can enable a template for use with HotDocs Server at the Component File Properties dialog box. Once they enable a template, you can use that template with desktop HotDocs, HotDocs Server, or HotDocs Cloud Services. Also, if they select Enable template for use with HotDocs Server, HotDocs warns them if they later try to use a feature that is not allowed in a HotDocs Server-compatible template.

  Would it be better to link directly to the At a Glance help for the page that has the server options on it?

   

  http://help.hotdocs.com/developer/webhelp/#Managing_Components_and_Templates_1/mcat1_window_reference_component_file_properties.htm

• Test in Browser: This command enables a template developer to view a browser-based (either JavaScript or Silverlight) interview for HotDocs Server-enabled templates. Using this feature is a way to ensure that the interview looks right and works correctly before the developer uploads the template to a web server.
• Publishing features:

  Do you think the points after this should have indented bullets?

• Publish Templates for Use with HotDocs Server: The Publishing Wizard includes an option for publishing templates for use with HotDocs Server. When this option is selected, HotDocs generates a special file used by HotDocs Server to generate browser-based interviews: the Template Manifest file.  (This file will have the same name as your template, but with ".manifest.xml" appended to the file name.)

  This is only for 11 and later. Do you think we need a note saying something like "pre 11 templates generate a .jvc and (that other file I cant recall) file"

  Passive.

• Upload Templates for Use with HotDocs Server: After publishing the templates for use with HotDocs Server, the template files, including manifests, must be uploaded to the Web server running HotDocs Server. You may do this as part of the publishing process by creating a Web page on the server to handle the uploaded files, or you can use your own uploading process to manually upload the template files after they have been published.

  Passive.

  I thought you were using "They" and referring to template developers in the third on this page?

  Passive.

• Cloud Upload Plug-in: A plug-in installed by default as part of HotDocs Developer that enables template developers to select a template or templates to package into template packages and either automatically upload them to a special web page on your integrated web application built to accepts these uploads, or save them to disk locally (from where they can later manually upload them to your web application).

  Consider revising this sentence into a couple smaller ones. I had trouble following it from start to finish.