<PAYMENTSERVICE>
<inputRules>
<rule triggerUnit="UserIdentifier" >
<selection key="ABC" paymentServiceId="1" articleId="2" tariffPackageId="3" lockArticle="false"/>
<selection key="DEF" articleId="2" lockArticle="true"/>
</rule>
</inputRules>
</PAYMENTSERVICE>
The key/prefix ABC will select Payment service 1 Article 2, and tariffpackage 3. The selection will not be locked (so it is still possible to change PAT afterwards) due to lockArticle attribute.
The key/prefix DEF will select Article 2. The selection will be locked (so it is not possible to change PAT afterwards in the purchase) due to lockArticle parameter.
Asynchronous/Synchronous selection
When a selection of PaymentService is included, the selection will be asynchronous (a thread switch is performed). This means that further actions like OnPurchasePrerequisitesInputDone cannot be executed in the same button that triggered the user identifier select. A solution can be to add the next action in an AutoClick-button in the next panel.
When selecting Article or TariffPackage the selection is performed synchronously, i.e. direct.
In the example above the key/prefix ABC selection will be performed asynchronously and the DEF selection will be synchronously.
Endless loop
When changing PaymentService, the current user identifier will be injected to the new PaymentService and inputRules will be executed again. Be careful and avoid endless loops like this example.
<PAYMENTSERVICE id="1">
<inputRules>
<rule triggerUnit="UserIdentifier" >
<selection key="ABC" paymentServiceId="2" />
</rule>
</inputRules>
</PAYMENTSERVICE>
<PAYMENTSERVICE id="2">
<inputRules>
<rule triggerUnit="UserIdentifier" >
<selection key="ABC" paymentServiceId="1" />
</rule>
</inputRules>
</PAYMENTSERVICE>
