Maybe I misunderstood the 'veto' action but as you can see here, I have a veto rule setup if the SSN does not meet the right format then to veto. The rule was met as true and the veto was activated but you can see that it clearly still continues to process and moves on to the mapping policy and then onto the ETP etc.... Shouldn't this event have been stopped at the veto and not gone any further?

08:26:37 4297F940 Drvrs: DRIVER_NAME PT:Applying policy: pub-itp.
08:26:37 4297F940 Drvrs: DRIVER_NAME PT: Applying to add #1.
08:26:37 4297F940 Drvrs: DRIVER_NAME PT: Evaluating selection criteria for rule 'break if status'.
08:26:37 4297F940 Drvrs: DRIVER_NAME PT: (if-operation equal "status") = FALSE.
08:26:37 4297F940 Drvrs: DRIVER_NAME PT: Rule rejected.
08:26:37 4297F940 Drvrs: DRIVER_NAME PT: Evaluating selection criteria for rule 'Veto if SSN not proper format'.
08:26:37 4297F940 Drvrs: DRIVER_NAME PT: (if-op-attr 'SSN' not-match "\d{9}") = TRUE.
08:26:37 4297F940 Drvrs: DRIVER_NAME PT: Rule selected.
08:26:37 4297F940 Drvrs: DRIVER_NAME PT: Applying rule 'Veto if SSN not proper format'.
08:26:37 4297F940 Drvrs: DRIVER_NAME PT: Action: do-veto().
08:26:37 4297F940 Drvrs: DRIVER_NAME PT:Policy returned:
08:26:37 4297F940 Drvrs: DRIVER_NAME PT:
<nds dtdversion="1.1" ndsversion="8.6" xml:space="default">
<input/>
</nds>
08:26:37 4297F940 Drvrs: DRIVER_NAME PT:Applying schema mapping policies to input.
08:26:37 4297F940 Drvrs: DRIVER_NAME PT:Applying policy: smp-MappingRule.
08:26:37 4297F940 Drvrs: DRIVER_NAME PT:Resolving association references.
08:26:37 4297F940 Drvrs: DRIVER_NAME PT:Applying event transformation policies.
08:26:37 4297F940 Drvrs: DRIVER_NAME PT:Applying policy: Pub-ETP.
08:26:37 4297F940 Drvrs: DRIVER_NAME PT:Policy returned:
08:26:37 4297F940 Drvrs: DRIVER_NAME PT:
<nds dtdversion="1.1" ndsversion="8.6" xml:space="default">