• Post Reply Bookmark Topic Watch Topic
  • New Topic

How to display WW_VERIFY_FUNCTION errors (raise_application_error) to user?  RSS feed

 
Gerben Feenstra
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

I made a (custom) ww_verify_function to attach to a profile of users. It is based on one provided by Oracle and it's only slightly modified here and there. The errorhandling is untouched, so this is all 'vanilla'.
For those who don't know, the code does all kinds of checks on a newly entered password. For instance the minimum length of the password.
If it is not correct it raises:




Now, on the other end inside the application we have a (headstart?) form, QMS0004F that allows the user to change their password. The way this form does this is through a forms_dll call:


(This will trigger the ww_verify_function in the background and verify the entered password. I know the checks work, because I have tested them.)


After that the form does a check on form_success:



However, the user never sees the raise_application_error from the ww_verify_function, only the above messages. Password change either succeeded or it didn't.



How do I show the raise application error to the user, so they know what is wrong in their new password?

I figured the raised application errors would end up on an errorstack, so I searched some and tried getting them from the errorstack:





But nothing returned. Then I examined the cg$errors package some more, and found:





Nothing again. But this gave me the idea to do a little test with:




Now, if I modify my ww_verify_function and push an errormessage on the stack, I can 'pop' them in the form to present them to the user. This seems to work, but I am not at all sure this would be the right way to do it.
Or is it?...


Can anybody explain to me what would be the correct way to show the user the raised_application_error?
 
Gerben Feenstra
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Really, no one?
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!