Page 1 of 1

Errors in fee when importing applications

Posted: Thu Jul 07, 2011 5:36 pm
by D. Van Haken
After applying V5SP3, errors can occur when importing applications prepared in other systems when the xml related to the fees is incomplete. The system will not create or override the missing fee information with the values that would appear if one would formfill an application from scratch via the GUI.

A patch is now made available to address this issue. It can be downloaded from our website at
http://docs.epoline.org/epoline/product ... ch5063.exe.

The logic that will be applied for missing or incomplete fees information in the xml is:
For EP1001, EP1038, EP1200, EPOPPO, at the time of import only:

if fee-amounts-unlocked-by-user="no" or this attribute is missing
then
for any fee that is defined in the imported XML:
- keep the value of topay attribute ("yes"/"no")
- <type-of-fee>: set to default type for this fee code, probably standard
- <fee-factor>, <fee-schedule>, <fee-sub-amount> : set to the value for locked fees

for any fee that is NOT defined in the imported XML:
- add the fee element, set the value of topay attribute to "no"
- <type-of-fee>: set to default type for this fee code, probably standard
- <fee-factor>, <fee-schedule>, <fee-sub-amount> : set to the value for locked fees

remark: as a consequence of the above, if not a single fee is present (empty list) --> all the fees will be added with topay "no" and default values

if fee-amounts-unlocked-by-user="yes"
then
for any fee that is defined in the imported XML:
- keep the value of topay attribute ("yes"/"no")
- keep <type-of-fee>, <fee-factor>, <fee-schedule>, <fee-sub-amount> as imported (no modifications whatsoever.

for any fee that is NOT defined in the imported XML:
- add the fee element, set the value of topay attribute to "no"
- <type-of-fee>: set to default type for this fee code, probably standard
- <fee-factor>, <fee-schedule>, <fee-sub-amount> : set to the value for locked fees