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.

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, the warning functionality did not make it into the 1.5 release.

Did this make it into v1.5? I can't find any reference to Warning Messages in the documentation.

-Larry

Hehe, yes, they are, as a matter of fact.  Might not make the release today or tomorrow, but they will be included with the next version that includes full, role-based security.

Are warning messages still on the "To do" list?

-Larry

Well, I told someone to come up with a good reason to add warnings, and you did, so we're adding it in...

We are now planning on implementing a warning option through the business objects when checking the Broken Rules.  There will be an event that is raised and will contain all of the "Warnings."  We will have an auto-show option or you will be able to manage them yourself.  Instead of using an error provider like the broken rules implement, a window displaying all of the warnings will be presented to the user.  Obviously you will be able to turn this off and display the warnings however you see fit. 

Since there is obviously a need for this type of interaction in the field we will definitely be adding this type of functionality.  Thanks for your input and we will let you know when this new functionality is available.

In fact, we are planning on using this functionality ourselves now when we checking drug indications on our medical application.  Thanks again guys!

I'd like to add my 2 cents to this topic. In the type of applications our organization (Social Services) develops, there is a definite need for warning messages that don't prevent an object from being saved. There are a number of data elements that we would like to capture for reporting purposes, but if the client refuses to provide that information, we are still required by law to provide the service. Using a warning message we can prompt the user to try to obtain the information, even though it's not 'required'. This has been an issue with our current framework, CSLA.

Sounds good to me.  That should be a good learning experience for a .Net novice like myself.