We have problem with showing warnings "Inline with Field"s.

Question

We have problem with showing error messages "Inline with Field"s.
1. We have a package ERROR, that collects all errors/warnings. It has a procedure PUT, that saves errors in the variables of the package.
Package ERROR
procedure put(ptable in varchar2, pcolumn in varchar2, pcode in varchar2, pmsg in varchar2);
end;
2. We have a database table. Its values are validated by a trigger (saving business rules).
If an error occurs, then the trigger calls the procedure PUT ( to save an error message).
For example ...
CREATE TRIGGER ...
--- Rule 21
if substr(:new.ka_kood,1,1) != :new.s_kat then
error.put('TABLE1','COLUMN1', -20167, ' MESSAGE 1 !');
end if;
END;
3. I have a form of HTML DB that updates the table TABLE1
I want to show this error message with the field COLUMN1 (Inline with Field) .
I need same validations before and after updating values.
Before update - to validate same input; after update - to show errors saved in the package ERROR.
I also tried to use the global variables. For example ...
WWV_FLOW.g_validation_ids_in_error(1):= 192645056564169139;
WWV_FLOW.g_item_ids_in_error(1):= 192644674113169137 ;
WWV_FLOW.g_validation_message(1):='MESSAGE1';
And this did not help.
To rise errors in programs - is there same API ?
Or there is some other solutions ?
How can I do this in HTML DB?

Answer 1

Andres,
I'm not sure exactly what you are trying to do. But perhaps this will help some. If your after-submit process runs DML that causes triggers to fire, which result in error messages to be accumulated in package variables, you could create a branch on the page that would be conditional on the existence of error messages in the package variables. The branch could be back to the same page or to a more customized error page. The page you branch to would use the error messages in the package variables to determine how to format the page with the error text. The key to doing this is to run it all in the same database session. The way to do that is to use a "direct" branch, i.e., one that does not do a URL redirect. You create this type of branch with the Create Branch wizard (Branch to Page) and do not check the "Branch to page using redirect" checkbox when you see it.
Be sure to roll back any changes you do not want committed before the branch.
Using HTML DB global package variables for anything like what you described is not supported.
Scott