nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

WDK 6.5 - Import Component

fenil

For all the WDK experts out here ....

I have a TBO which does attribute validation during import. When the validation fails, I throw an exception with my custom message.

Everything on that front works perfectly. Whenever the validation fails, my custom message shows up and does not let the user import the document.

The issue here is that, when an exception is thrown, the custom message is shown in a new window and the only option the user has is to "cancel" the operation and restart by going to File -> Import.

Is there anyway on the WDK side, I can change the behavior of Import Component / Container so that whenever the validation fails, an exception is thrown, and my message still shows up but the user still has the option to correct the mistake and continue import rather than re-starting the whole process.

Thanks a lot in advance !!

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Button

Accepted answers

mszurap

If you do validation in TBO, that will do a "hard" validation, with the side effect that you have wrote.

If you need "nice" validation with proper warning message and without need to restart the whole process, you need to customize WDK. Extend the import component to include an error message label, and extend the importcontainer and override it's onCommitChanges method. There you can validate what you want. If not's everything valid, you simply don't call the super.onCommitChanges() method and show the error label.

Both solution does not exclude each other. The TBO will ensure that there is no other application which breaks the rules. Yes, it's kind of code duplication, but I don't know a better solution.

Mike

All comments

Francois Dauberlieu

Instead of throwing an exception, you could try (not sure though so you'll have to test) to use the ErrorMessageServices (or something like that, I'm not in front of a machine with WDK on it...)

fenil

Thanks for the reply. Since i'm doing the validation at TBO level and not WDK, will I be able to access ErrorMessageServices class from dfc.jar ?

I don't want to do any validation at WDK / Webtop side.

mszurap

If you do validation in TBO, that will do a "hard" validation, with the side effect that you have wrote.

Both solution does not exclude each other. The TBO will ensure that there is no other application which breaks the rules. Yes, it's kind of code duplication, but I don't know a better solution.

Mike

fenil

Mike,

Thanks a lot for the detailed reply. Looks like I'll need to do validation on both ends, unless I can convince the users to restart the process everytime they screw up !!

Francois Dauberlieu

I guess it was one of those days and whilst answering, forgot it was a TBO so indeed, Mike's way seems to be the best one

harjits

you can do this by customizing the importcontainer. your customization should be in onCommit method. Over ride the method. When you over ride. First call your custom code and then call super.onCommit(). Also WDK has some Validation tags which can do validation for you. Take a look at that in the WDK developer guide. Doing validation in TBO is not a good practice. TBO's are used for a different purpose and not for what you are trying to do.

- Harjit

fenil

Thanks and I was able to achieve what I wanted by overriding the onCommitChanges() from Import Content and using ErrorMessageServices.

I still need to TBO validation becasue users can change the properties after importing the document, the tbo also handles the folder location based on the value entered by the user. So i do need the TBO validation but in conjuction with the Import Component validation.

harjits

if you need validation after the content has been imported. Customize the properties component. We did the same. Autolocation of a object on a attribute, you can have that in a TBO or implement a SBO and that can be called in import and properties component. I would avoid TBO if I can, it just complicates things.

- Harjit

fenil

Thanks for the input. I guess for now we are going the TBO route but I'll definitely keep this in mind for any future situations.