As per forum posts on using the HTML widget to display adobe PDF data, allow access to functions like CefBrowserHost::find from within Uniface, this to allow for better integration between Uniface and one of the most popular document distribution formats.

A new switch for lookup
This new \”lookup/exists\” should return
* 0 if there is no row matching the profile
* 1 if there is a least on row matching the profile
The access to the database should
* use (if possible) a \”EXISTS\” clause
* not use a cursor or any other kind of hitlist

What about new UnifAce-functions like

string $occprofile2sql({}}) ; Convert the current profile to a SQL-where clause
string $ucondtion2sql(\”\”{,}) ; Convert a ucondition-string to a SQL-where clause
string $uwhere2sql(\”\”{,}) ; Convert a uwhere string to a SQL-where clause ( superfluous?)

This function should convert the input to the SQL-where-clause on the default database connector or the one give by the term

Some web sites open popup window (via javascript window.open) , then
Uniface open new form with HTML widget inside, but we can do nothing with this except close this.
We can forbidden opening this popup window.

Doing database I/O when getting an error Uniface is providing $dberror to expose real database error captured from db connector, enabling to fine tune application error management.
There should be an equivalent function (or $dberror implementation should be generalized) exposing real error also for other connector types; as an example SOAP connector should expose HTTP transport error (See: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes).
As of U9.7 this fine tuning can only be partially implemented analyzing strings given back from connector into $procerrorcontext; string analysis could be prone to errors because of software evolution or different languages or possible customizations, while an errorcode is a much more simpler and stable information.