According to the documentation:
"When this option is selected, it makes the qualification object’s
criteria optional,
which allows you to use AND/OR logic.
For example, you could have three qualification objects, one that
checks that an age
field's data is between 25 – 35, another that checks for a range of 45
– 65, and the last
that checks for a specific heart condition. If the first two
qualification objects have
Optional selected, and the last one does not, then the incoming data
must satisfy
either of the qualification objects that specify the age range and it
must also satisfy
the heart condition qualification object.
If all of the qualification objects for a production object have
Optional selected, the
incoming data must satisfy at least one of the qualification objects
before e-Biz
Impact continues processing."
So, just to test this out, I placed two qualifiers checking the MSH
Header. One checked for a literal of 'BOB' and the next checked for
the literal of 'MARY'.
I would have expected this to throw an error when a standard HL7
message is sent to it with a value of 'MSH' in the MSH Header. It
didn't. Sybase didn't bat an eye and just processed the message.
I've never used this before, and I could code around it, but it would
be more convenient now, and I am just curious.
Thanks