Rank: Advanced Member
Joined: 9/9/2010
Posts: 51
Location: Pittsburgh, PA, USA
|
It would help if the existing "Exception" function would not have the following restrictions:
• Both parameters of the filter component, on-true and on-false, must be mapped! One of them needs to be mapped to the exception component, and the other, to the target component that receives the filtered source data. If this is not the case, the exception component will never be triggered.
• The exception and target components must be directly connected to the filter component. Functions, or other components, may not be placed between the filter and either the exception, or target components.
We want to throw an exception if specific conditions do not apply (i.e., two tests on same data return a "false") but do not want to forward the "true" output from the filter, as per the ExpenseLimit.mfd example. The actual "true" output is handled elsewhere with additional code, so we violate both bullet items above.
|
