Details
-
Type:
Other
-
Status: Closed
-
Priority:
Default
-
Resolution: Fixed
-
Affects Version/s: 1.4.0
-
Fix Version/s: None
-
Component/s: Documentation
-
Labels:None
Description
The documentation for ValidateFieldsOutOfOrder reads:
"If set to N, fields that are out of order (i.e. body fields in the header, or header fields in the body) will not be rejected. Useful for connecting to systems which do not properly order fields."
Search of the source code reveals that it has to do with mis-ordered repeating group fields. It does nothing about header fields in the body or vice versa. (Verified by experiment.)