Validation scenario as an Action for mapping to a button in the UI

Are you missing a feature? Request it's implementation here.
dcramer
Posts: 158
Joined: Sat Aug 28, 2010 1:23 am

Validation scenario as an Action for mapping to a button in the UI

Post by dcramer » Fri Apr 10, 2020 11:13 pm

Hi there,

We have a validation scenario that can be expensive so we don't have it on by default. We can have users configure their validation scenario to turn it on, but then they have to remember to turn it back off. The process involves a few clicks each time. Users have requested a single button to run this one validation scenario. Am I correct in assuming this will require writing a custom Operation and adding it to the Classpath? It would be nice if validation scenarios were available as Actions out of the box so I could easily add a button for a specific scenario.

Regards,
David

Radu
Posts: 6980
Joined: Fri Jul 09, 2004 5:18 pm

Re: Validation scenario as an Action for mapping to a button in the UI

Post by Radu » Mon Apr 13, 2020 8:00 am

Hi David,

We have a builtin operation for running transformation scenarios "ExecuteTransformationScenariosOperation" but unfortunately we do not have a builting Author operation for running a validation scenario with a specific name. We would first need to add API to invoke one (or mutiple) validation scenarios given their names and then this API could use used from a custom Author operation to validate. I added an internal issue based on your request. You will be notified on this thread when the API is available.

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com

dcramer
Posts: 158
Joined: Sat Aug 28, 2010 1:23 am

Re: Validation scenario as an Action for mapping to a button in the UI

Post by dcramer » Mon Apr 13, 2020 6:23 pm

It would be ideal if this mechanism worked with an id associated with the validation scenario instead of the validation scenario's name. This would avoid the situation where a framework maintainer rename's a validation scenario without realizing there's a dependency elsewhere in the framework on that exact user-visible string. But I realize that would be a much bigger change and is unlikely to happen.

Thanks,
David

Radu
Posts: 6980
Joined: Fri Jul 09, 2004 5:18 pm

Re: Validation scenario as an Action for mapping to a button in the UI

Post by Radu » Tue Apr 14, 2020 8:58 am

Hi David,

Yes, assigning IDs to all our validation and transformation scenarios would be a bigger endeavor. Also people might not want to manually add ids every time they create a scenario so we would need to probably auto assign unique ID values to created scenarios. And then we would need to also handle older scenarios which do not have defined IDs.
So for now we'll stick to using the scenario names for identification.

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com

alex_jitianu
Posts: 763
Joined: Wed Nov 16, 2005 11:11 am

Re: Validation scenario as an Action for mapping to a button in the UI

Post by alex_jitianu » Wed May 20, 2020 4:00 pm

Hello David,

In the newly release Oxygen 22.1, there is a new operation available, ExecuteValidationScenariosOperation, that will execute one or more validation scenarios. I hope it helps!

Best regards,
Alex

Post Reply