<?xml version="1.0" ?>
<workflowDescriptor name="ipdBusinessDayWorkflow">
<!--
Each node is followed by a comment that indicates which Payment Feature Services
component it is associated with. The nodes that are not labeled are provided
as part of Business Rules itself. If all of the components are not being used,
the nodes that are associated with the unused components must be removefrom thed
Workflow, and the 'connection' entries for those nodes must also be updated to
flow around the removed nodes. Sample connection changes with the
Accounting component removed are shown.
-->
<nodes>
<node name="DepositProductLookupNode"/>
<node name="BusinessDayNode"/>
<node name="BusinessDayCategoryNode"/>
<node name="BusDayAvailabilityNode"/> <!-- Accounting -->
<node name="BusDayBillingNode"/> <!-- Billing -->
</nodes>
<connections>
<connection srcName="DepositProductLookupNode" dstName="BusinessDayNode"/>
<connection srcName="BusinessDayNode" dstName="BusinessDayCategoryNode"/>
<connection srcName="BusinessDayCategoryNode" dstName="BusDayAvailabilityNode"/>
<!--
If the Business Rules component of Accounting is not installed, the previous
connection needs to be replaced with
<connection srcName="BusinessDayCategoryNode" dstName="BusDayBillingNode"/>
and the next connection (marked with an 'A') needs to be removed.
-->
<connection srcName="BusDayAvailabilityNode" dstName="BusDayBillingNode"/> <!-- A -->
</connections>
</workflowDescriptor>
Table 1. ipdBusinessDayWorkflow nodes and related components
| Node |
Related component |
| DepositProductLookupNode |
Business Rules |
| BusinessDayNode |
Business Rules |
| BusDayAvailabilityNode |
Accounting |
| BusDayBillingNode |
Billing |