×
Menu
Index

SubProduct tab

 

Description

Description of the SubProduct.
 

Path

Contains a dropdownlist that holds all possible paths (following the ElementTable, that is the XML Schema). The selected Path stands for the standard path for all Tools beneath this SubProduct.
 

Instance

All XML reads done from Child Tools of this SubProduct, are using this Instance of the Element mentioned in Path.
 
Input XML:
<CustomerDocument>
     <Contract />
</CustomerDocument>
 
Product Path:
CustomerDocument/Contract
 
SubProduct Instance:
2
 
After setting ./Policy/PolicyNumber to 845784
 
Output XML
<CustomerDocument>
     <Contract />
     <Contract>
          <Policy>
               <PolicyNumber>845784</PolicyNumber>
          </Policy>
     </Contract>
</CustomerDocument>
 
Attention!
When you use Instance = 0, SoftRules® will loop all Tools and Suppliers (if defined) for each Contract found in the Input XML. In that case the SubProduct will act as a LoopNode.
 

Configuration

It's possible to declare another Configuration of Functions, Tables, Validations and Userinterfaces at SubProduct level. When leaving empty the Configuration of the Parent will be used.
 

Version

You can declare a custom Major and Minor version number to your SubProduct. This is for your own administrative purposes, SoftRules® ignores these.
 

Parallel processing

SubProducts can be executed simultaneously with other SubProducts. Select Parallel Processing to do so. Be careful to design your XML structure so that is is able to be filled in an uncontrolled order. Parallel processing is an advanced technique and is hard to debug. Also you should be careful to process SubProducts that use Execute Tools in parallel. Not every external source is capable of handling multiple requests at the same time. When in doubt use Run isolated or don't use Parallel Processing. But, when mastered, this technique is extremely powerful to create very fast Configurations.
 

Enable exception handling

When checked a node will be placed beneath the SubProduct called Exception handling. This will be the place where the execution will continue after an unhandled exception will occur. See Exception handling.
 

Conditions for Activation

Doubleclick this to enter the Expression that triggers this SubProduct. If no Expression is entered, the SubProduct will always execute.