solutionDefinition Element
The document is archived and information here might be outdated

solutionDefinition Element

Office 2007

Root element for the elements defined in the xsf2 namespace. Specifies new properties and features that have been added to Microsoft Office InfoPath 2007 form templates.

Usage


<solutionDefinition
	runtimeCompatibility="xsf2:runtimeCompatibilityType"
	solutionType="xsf2:solutionType"
	description="xsf2:formDescriptionType"
	allowClientOnlyCode="xsf:xdYesNo"
	runtimeCompatibilityURL="xsd:string"
	verifyOnServer="xsf:xdYesNo"
/>

Element Information

Element type xsd:complexType
Namespace xsf2

Elements and Attributes

Child Elements

ElementDescription
serverSpecifies how a form template is displayed and works when opened in a Web browser.
solutionPropertiesExtensionSpecifies the extended information for the solutionProperties element in the manifest.xsf whose name attribute matches the ref attribute of this element.
mergedPrintViewContains properties of the merged print view.
offlineSpecifies how the form template behaves when working offline.
listPropertiesExtensionSpecifies the extended information for the listProperties element in the manifest.xsf whose name attribute matches the ref attribute of this element.
dataConnectionsContains elements that specify data connections.
sendByMailSpecifies extended information for forms sent by e-mail when using the InfoPath form editor.
warningsContains elements that specify whether a category of message is visible in the Design Checker task pane. The different categories of messages can be made hidden or visible depending on what the user has specified using the Options drop-down list in the Design Checker task pane. By default, all categories of messages are visible.
viewsExtensionSpecifies the extended information for the views element in the manifest.xsf whose name attribute matches the ref attribute of this element.
previewSpecifies properties for previewing the form in InfoPath Design mode.  
autoUpdatePromptSpecifies whether the user will be prompted to choose whether to upgrade to a new version of the form template when one becomes available.
inputScopesContains one or more inputScope elements that specify input scope settings.
managedCodeSpecifies managed code form template project settings for Microsoft Visual Studio and Visual Studio Tools for Applications.
submitSpecifies properties for submitting the form.
featureRestrictionsExtensionSpecifies the extended information for the featureRestrictions element in the manifest.xsf whose name attribute matches the ref attribute of this element.

Attributes

AttributeTypeRequiredDescriptionPossible Values
runtimeCompatibilitycompatibilityModesTypeRequiredSpecifies whether a form based on this form template can be filled out only in InfoPath or in both InfoPath and a Web browser.

Note   This element or attribute must be present and valid in the form definition file (.xsf), before InfoPath Forms Services will allow the form template to be deployed to the server as a browser-compatible form.
  • client
  • server
solutionTypesolutionTypeOptionalSpecifies whether this solution is a template part or a form template.

Note   If this element or attribute is in the form definition file (.xsf), InfoPath Forms Services will ignore this setting when the form template is deployed to the server as a browser-compatible form.
  • templatePart
  • formTemplate
descriptionformDescriptionTypeOptionalSpecifies the description of this form template.

Note   This element or attribute is optional in the form definition file (.xsf) of a form template deployed as a browser-compatible form to a server running InfoPath Forms Services.
String
allowClientOnlyCodexdYesNoOptionalSpecifies whether the form template designer wants to allow the use of InfoPath-only features in business logic written against the Microsoft.Office.InfoPath object model when the runtimeCompatibility attribute is set to "client server".

Note   This element or attribute is optional in the form definition file (.xsf) of a form template deployed as a browser-compatible form to a server running InfoPath Forms Services.
  • yes
  • no
runtimeCompatibilityURLxsd:stringOptionalSpecifies the URL of the server running InfoPath Forms Services that can be used to verify the compatibility of the form template.String
verifyOnServerxdYesNoOptionalSpecifies whether to verify the compatibility of the form template using the URL of the server specified by the runtimeCompatibilityURL attribute.

Note   This element or attribute must be present and valid in the form definition file (.xsf), before InfoPath Forms Services will allow the form template to be deployed to the server as a browser-compatible form.
  • yes
  • no

Definition


<xsd:element name="solutionDefinition">
   <xsd:complexType>
      <xsd:all>
         <xsd:element ref="xsf2:server" minOccurs="0" />
         <xsd:element ref="xsf2:solutionPropertiesExtension" minOccurs="0" />
         <xsd:element ref="xsf2:mergedPrintView" minOccurs="0" />
         <xsd:element ref="xsf2:offline" minOccurs="0" />
         <xsd:element ref="xsf2:listPropertiesExtension" minOccurs="0" />
         <xsd:element ref="xsf2:dataConnections" minOccurs="0" />
         <xsd:element ref="xsf2:sendByMail" minOccurs="0" />
         <xsd:element ref="xsf2:warnings" minOccurs="0" />
         <xsd:element ref="xsf2:viewsExtension" minOccurs="0" />
         <xsd:element ref="xsf2:preview" minOccurs="0" />
         <xsd:element ref="xsf2:autoUpdatePrompt" minOccurs="0" />
         <xsd:element ref="xsf2:inputScopes" minOccurs="0" />
         <xsd:element ref="xsf2:managedCode" minOccurs="0" />
         <xsd:element ref="xsf2:submit" minOccurs="0" />
         <xsd:element ref="xsf2:featureRestrictionsExtension" minOccurs="0" />
      </xsd:all>
      <xsd:attribute name="runtimeCompatibility" use="required">
         <xsd:simpleType>
            <xsd:list itemType="xsf2:compatibilityModesType"/>
         </xsd:simpleType>
      </xsd:attribute>
      <xsd:attribute name="solutionType" type="xsf2:solutionType" use="optional" />
      <xsd:attribute name="description" type="xsf2:formDescriptionType" use="optional" />
      <xsd:attribute name="allowClientOnlyCode" type="xsf:xdYesNo" use="optional" default="no" />
      <xsd:attribute name="runtimeCompatibilityURL" type="xsd:string" use="optional"/>
      <xsd:attribute name="verifyOnServer" type="xsf:xdYesNo" use="optional"/>
      <xsd:anyAttribute processContents="skip" />
   </xsd:complexType>
</xsd:element>

Remarks

Note   This element or attribute must be present and valid in the form definition file (.xsf), before InfoPath Forms Services will allow the form template to be deployed to the server as a browser-compatible form.



Show:
© 2016 Microsoft