I have a rule that really should not stop the saving process, like using the addbrokenrule call would do.  How would you suggest taking care of this type of issue?  How about a warnings collection and an addwarning call?

Just a thought.

Hi,

Any update on this feature? I couldn't find it at 1.6.7 as well.

It is very useful feature for us. Please put it on higher priority if it is not implemented.



Thank you

No, and at the present we are not sure if it will be added in the near term.  We have taken a different approach in our medical software and after a lot of discussion and debate there are no consistent opinions on how this would be implemented on a global scale.  It is not taken off of the table, but the issue comes down to at what point the record will be saved (if it will at all).  For example, errors prevent a save, so this is easy.  But what do warnings do?  Ultimately there would have to be some events that manage this and options to determine how the behaviour would be.  So until we revisit this and come up with an agreed way to manage this, it will not be implemented.  But it is still on the table and will be implemented in some fashion at some point, but at present this is not implemented.