External UserIdentifier CO2 Emission - User Guide
PAYMENTSERVICE element
In the PAYMENT SERVICE
•set the userIdentifier to Code.
•Specify the defaultArticleId to be used if no vehicle data is returned. This can be the same as the one specified for the key values -1 and the highest category.
<PAYMENTSERVICE ... defaultArticleId="30" userIdentifier="Code" ...="">
<inputRules>
<rule triggerUnit="UserIdentifier" userIdentifierDll=" extuis_CO2Emission.dll">
<selection key="=-1" articleId="20" />
<selection key="=0" articleId="10" />
<selection key="<100" articleId="11" tariffPackageId="11"/>
<selection key="<150" articleId="12" />
<selection key="<200" articleId="13" />
<selection key=">199" articleId="20" />
<extendedproperties>
<property name="CO2EmissionCategory1" value="=-1" />
<property name="CO2EmissionCategory2" value="=0" />
<property name="CO2EmissionCategory3" value="<100" />
<property name="CO2EmissionCategory4" value="<150" />
<property name="CO2EmissionCategory5" value="<200" />
<property name="CO2EmissionCategory6" value=">199" />
</extendedproperties>
</rule>
</inputRules>
</PAYMENTSERVICE>
| Important: when describing ranges and you want to use the greater than (>) and less than (<) operators you must write them in XML format as follows: (marked bold in the example above) - write > as > - write < as < |
CO2 value
If the returned data contains a CO2 value, this will be compared to the specified key values in the selection element.
If the license plate is not found a text message like “httpStatusCode404” will be returned. These are most commonly foreign cars. in this case there is no value to compare to the selection keys and the default article will be used. As there is also no matching property, there will be no CO2 emission category available to display. This can be solved by adding a text in the corresponding Tariff Package.
If the license plate can be found but no CO2 value is found for that license plate, a negative value like -1 can be returned.
Verify this with the provider when setting up the service.
rule sub-element
The rule sub element can be found inside the inputRules element
<inputRules>
<rule triggerUnit="UserIdentifier" userIdentifierDll="extuis_CO2Emission.dll">
...
</rule>
</inputRules>
In the rule sub element specify the following attributes:
•Set the triggerUnit to UserIdentifier
triggerUnit="UserIdentifier"
•Set the userIdentifierDll to extuis_CO2Emission.dll
userIdentifierDll="extuis_CO2Emission.dll"
selection sub-element
In the selection elements inside the rule element specify the CO2 ranges to use.
Each selection element points to one CO2 category by defining the range of the return value from WebOffice.
| Note: We Recommend a separate article for each category to be able to display the CO2 fee |
<selection key="=-1" articleId="20" />
<selection key="=0" articleId="10" />
<selection key="<100" articleId="11" tariffPackageId="11"/>
It is possible to link a tariff package to a category as well. E.g. for a normal tariff where most of the cars will end up.
| Important: The selection key values and the corresponding property values MUST have exactly the same value. The selections are validated against the returned data in the order they are specified in the configuration file. If you e.g. set the highest value first all cars will get the highest fee. |
extendedproperties
You can specify the name of the CO2 category in the extended properties of the rule to be printed on the ticket. these can be either digital or physical.
The property works with the same value as the key value in "selection".
<extendedproperties>
<property name="CO2EmissionCategory1" value="=-1" />
<property name="CO2EmissionCategory2" value="=0" />
The maximum fee can be mentioned in the tariff package when no selection can be made.
