Human Interaction Document Loader Service

How the Human Interaction Document Loader Service Works

Use the Human Interaction Document Loader service to retrieve documents from the Sterling B2B Integrator database. The following sections describe a business scenario and a sample solution using the Human Interaction Document Loader service.

Business Scenario

Your company receives purchase orders in XML format from a trading partner. All purchase orders exceeding $1,000.00 need to be approved. You want to view a purchase order requiring approval in the Web browser.

Business Solution Example

Business Solution Example Dependencies

This business solution example focuses only on the Human Interaction Document Loader service functionality.

GPM Example

The following example shows a solution to the business scenario using the GPM.

The Human Interaction Event service (not shown) generated an e-mail notification to the approver after the purchase order was added to the database. The approver uses this URL to display the purchase order requiring approval in the Web browser. For example:

http://siHostName:siport/websuite/xfm/ExamplePurchaseOrderFromHTTPRequest.xfm?documentId=7736bd:fb78c70638:-77df 

The business process run by the Web template uses the Human Interaction Document Loader service to retrieve from the database the purchase order that corresponds to the documentId, and uses the B2B HTTP Server adapter to display the purchase order in the Web browser.

After the Human Interaction Document Loader service completes, the purchase order is returned to the business process as the primary document, along with a document named HumanInteractionEvents, which contains the reference data from the Human Interaction Event service for the purchase order. The returned Human Interaction Events document for this example looks like the following:

The returned primary document (purchase order) for this example looks like the following:

<Order Id="200"> 
	<Order_Item Id="400"> 
 	<Order_Id>200</Order_Id> 
 	<Name>DSL</Name> 
 	<Quantity>1</Quantity> 
 	<Price> $1050.00</Price> 
	</Order_Item> 
	<Order_Item Id="401"> 
 	<Order_Id>200</Order_Id> 
 	<Name>Cable</Name> 
 	<Quantity>1</Quantity> 
 	<Price> $1500.00</Price> 
	</Order_Item> 
</Order>

The primary document is then sent to the B2B HTTP Server adapter for display in the Web browser.

The approver can choose to approve or reject the purchase order.

Business Process Modeling Language (BPML) Example

The following example shows the corresponding business process solution using BPML.

<process name="ExamplePurchaseOrderHIDocLoader"> 
<sequence name="Start"> 
<operation name="Human Interaction Document Loader"> 
<participant name="HumanInteractionDocumentLoader"/> 
<output message="HumanInteractionDocumentLoaderTypeInputMessage"> 
	<assign to="MinedDataId" from="documentId/text()"/> 
	<assign to="." from="*"/> 
	</output> 
<input message="inmsg"> 
	<assign to="." from="*"/> 
</input> 
</operation> 
<operation name="HTTP Respond Service">
      <participant name="HttpRespond"/>
      <output message="HttpRespondServiceInputMessage">
        <assign to="." from="*"></assign>
      </output>
      <input message="inmsg">
        <assign to="." from="*"></assign>
      </input>
    </operation> 
</sequence> 
</process> 

Implementing the Human Interaction Document Loader Service

Human Interaction Document Loader Service Business Process Usage

The following screen shows a graphical view of the GPM parameters for the Human Interaction Document Loader service. There are no fields to be configured on the Message From Service tab.

The following example shows the corresponding BPML parameters for the Human Interaction Document Loader service GPM parameters.

<process name="ExamplePurchaseOrderHIDocLoader"> 
<sequence name="Start"> 
<operation name="Human Interaction Document Loader"> 
<participant name="HumanInteractionDocumentLoader"/> 
<output message="HumanInteractionDocumentLoaderTypeInputMessage"> 
	<assign to="Downloadable">YES</assign> 
	<assign to="MinedDataId" from="documentId/text()"/> 
	<assign to="." from="*"/> 
</output> 
<input message="inmsg"> 
	<assign to="." from="*"/> 
</input> 
</operation> 
</sequence> 
</process> 

The following table describes the fields used to configure the Human Interaction Document Loader service in the GPM. The values specified for these parameters are the input to the Human Interaction Document Loader service from the business process.

Output from Service to Business Process

The following table describes the output from the Human Interaction Document Loader service to the business process: