Oxygen XML Forum

Hello there,

First I would like to thank Oxygen for the great improvement on table/cell width extensions capability. Really makes tables look great now.

Now, I have a small request: I have a couple of business validation and post-processes I need to implement for users that will not fit into schema or any ontology like framework.( because of the complexity, requires external data....).

I]On load
I have implemented them as Author action which is great but I would like them to be fire up as soon as the page is loaded or switched to author view.

I can do some of it using the entityresolver (only extension fired on load with an AuthorAccess), but:
- the AuthorAccessthere is not completely functional since we are dealing with a copy of the document (table function errors for example, any GET like functions really. Write functions work but throw an error...).
- It is not really the proper place to do it.

So, Would it be possible to:
- make some function fired onLoad/switch user view?

II]Validation of business rules
It would be nice too:
- Be able to extend the validation process with custom errors. Basicaly in:AuthorAcess, out: list<SaxExceptionLikeFields>.
- Or be able to use the custom engine validation with “validate as you type” (same idea as above, be able to extend ovndl.jar's output).


Thanks in advance,

Hello,

Tanking wrote:I]On load
I have implemented them as Author action which is great but I would like them to be fire up as soon as the page is loaded or switched to author view.
. . .
So, Would it be possible to:
- make some function fired onLoad/switch user view?

In version 10.3 the Author API will allow adding a document listener that is fired when Author document loading is completed. Other validations that are necessary later when the document is modified can be done even in the current version (10.2) in a document listener (fired when the document is modified).

Tanking wrote:II]Validation of business rules
It would be nice too:
- Be able to extend the validation process with custom errors. Basicaly in:AuthorAcess, out: list<SaxExceptionLikeFields>.
- Or be able to use the custom engine validation with “validate as you type” (same idea as above, be able to extend ovndl.jar's output).

We will add methods for displaying an error or a list of errors similar with the built-in validation errors. The format of the error message will be imposed by an interface that will allow a severity level (error, warning, info, etc), location of error (system ID of the file with the error, line and column of error), description of error. If we have enough time this can be implemented in version 10.3.

If you have a custom validator engine you can run it with Validate as you type in the current version (10.2). Just create the custom validator in Preferences -> Editor -> Custom Validation and set it as the validator for your document with a validation scenario.


Regards,
Sorin