hwsAdapter Element

  • Article

Defines the Microsoft BizTalk 2004 Human Workflow Services (HWS) data adapter, which can be used to start or extend an activity flow and respond to a task.

Type

  xsd:complexType

Child Elements

Element Description
hwsOperation Defines the HWS operation type, such as adding an action to a new activity flow, adding an action to an existing activity flow, and responding to a task.

Attributes

Attribute Type Required Description Possible Values
name 
  xdTitle
Yes Contains the name of the data adapter.

minLength = 1

maxLength = 255

pattern = ([^\p{Z}\p{Cc}\p{Cf}\p{Cn}])(([^\p{Zl}\p{Zp}\p{Cc}])*([^\p{Z}\p{Cc}\p{Cf}\p{Cn}]))?

 
  xdTitle
wsdlUrl 
  xsd:string
Yes Contains the Uniform Resource Locator (URL) of the HWS Web service. string 
  xsd:string
queryAllowed 
  xdYesNo
No Specifies whether the adapter can be used for querying the data source. Can be omitted for the hwsAdapter, corresponding to a default value of "no".
  • yes
  • no
 
  xdYesNo
submitAllowed 
  xdYesNo
No Specifies whether the adapter can be used for submitting to the data source. Always set to "yes" for the hwsAdapter.
  • yes
  • no
 
  xdYesNo

Definition

  <xsd:element name="hwsAdapter">
  <xsd:complexType>
    <xsd:choice>
      <xsd:element ref="xsf:hwsOperation"/>
    </xsd:choice>
    <xsd:attribute name="name" type="xsf:xdTitle" use="required"></xsd:attribute>
    <xsd:attribute name="wsdlUrl" type="xsd:string" use="required"></xsd:attribute>
    <xsd:attribute name="queryAllowed" type="xsf:xdYesNo" use="optional"></xsd:attribute>
    <xsd:attribute name="submitAllowed" type="xsf:xdYesNo" use="optional"></xsd:attribute>
  </xsd:complexType>
</xsd:element>

Remarks

Upon submit, the hwsAdapter automatically creates a globally unique identifier (GUID), as required by the HWS Web service; encodes the XML file; and updates the processing instructions of the XML instance file.

Note   If this element or attribute is in the form definition file (.xsf), InfoPath Forms Services will prevent the form template from being deployed to the server as a browser-compatible form.

Example

The following is an example of the hwsAdapter element:

  <xsf:hwsWorkflow taskpaneVisible="yes">
   <xsf:location url="http://www.contoso.com/hwsservice/hwsservice.asmx"/>
   <xsf:allowedActions>
      <xsf:action  name="approval" actionTypeID="123" 
         canInitiateWorkflow="yes" caption="Get Approval"/>
      <xsf:action  name="delegate" actionTypeID="234"   
         canInitiateWorkflow="no" caption="Delegate"/>
   </xsf:allowedActions>
   <xsf:allowedTasks>
      <xsf:task name="getManagerApproval" taskTypeID="435" 
         caption="Send Response"/>
      <xsf:task name="getVPApproval" taskTypeID="436"  
         caption ="Send   Response"/>
      <xsf:task name="delegateToManager" taskTypeID="420" 
         caption="Respond"/>
   </xsf:allowedTasks>
</xsf:hwsWorkflow>

<xsf:hwsAdapter name="Start Approval"

wsdlUrl="http://www.contoso.com/hwsservice/hwsservice.asmx?WSDL"
submitAllowed="yes">
<xsf:hwsOperation type="addActionToNewActivityFlow" typeID="{guid}"
serviceUrl="http://www.contoso.com/hwsservice/hwsservice.asmx">
<xsf:input source="HWSMessage1.xml">
<xsf:partFragment match="/ns1:HWSMessage/ActionSection/param1"
replaceWith="/my:myFields/my:param1"/>
<xsf:partFragment match="/ns1:HWSMessage/ActionSection/param2"
replaceWith="/a:some/b:thing" dataObject="Aux1"/>
</xsf:input>
</xsf:hwsOperation>
</xsf:hwsAdapter>