Call Us Today! +1 (866) 331-1354|sales@docova.com

Blog

Migrate Notes to DOCOVA Blog Series Part 17: Input translation and input validation formulas

Welcome to blog series part 17 of 17 on migrating Notes apps to DOCOVA.  The subject of this blog is Input translation and input validation formulas (formulae if you prefer).

Right.  So, one day I hear this argument coming from down the hall here at DOCOVA.  The dev team embroiled in some discussion.  Oh the controversy.  Fisticuffs? Naw.  Heated?  Maybe that would be a bit of a stretch.  The debate?  How should input translation and input validation formulas be handled in DOCOVA?

In a Notes developer client, you can click on a field on a form and provide a formula for translating or validating values for that field.

Should DOCOVA do it the same way?  On the one hand, from a migration point of view, it’s one to one, it’s easier to migrate the formulae over to DOCOVA associated with the fields on the forms.  The way Notes did it, it was convenient and pretty easy to find, add, edit, what have you.

On the other hand, it’s a bit disjointed especially on the validation side of things.  The save/submit process stops for each problem encountered rather than summarize the issues and present them to the user so that the user can fix them all and save again.

So, the question becomes, should DOCOVA implement these formulae the way Notes did?

Well, as of the writing of this blog post I can say, when it comes to input translation formulas, we went ahead and added the option to fields in the App Builder.  Kinda makes sense for that.

However, for input validation, again as at the time of my writing this blog, remains outstanding.  I will come back and update this later but for now, there are two trains of thought.  First, just bring the formulas over and have them the same way as Notes does, as an attribute of a field.  With this approach, migration is easier and the simplicity of it remains.  Alternatively, when importing a form, we gather up all validation formulas and combine them into one function that gets executed on submit.  This approach would lend itself to being more easily converted into something it should be. Stay tuned.  The bottom line though, is that input validation formulas can easily be converted over to DOCOVA and implemented with a field or in your own .js, we’re  just looking to make it a bit more automated.

Comments?

You can fast-track and get all the whitepapers on our migration methodology and everything that is being discussed in this series of posts.  Specifically, you can get the DOCOVA Notes/Domino Migration Methodology – MIGRATE whitepaper.

By |May 25th, 2017|Notes Migration, Technical|Comments Off on Migrate Notes to DOCOVA Blog Series Part 17: Input translation and input validation formulas

Migrate Notes to DOCOVA Blog Series Part 16: Form events

Welcome to blog series part 16 of 17 on migrating Notes apps to DOCOVA.  In this entry I’m going to talk about form events.

Okay, so the talk about form events usually starts of with the question:

Does DOCOVA have document events like onLoad, onUnload, QueryOpen, QuerySave and WebQueryOpen?

Yes.  DOCOVA supports both typical browser events like onLoad and onUnload but has also been extended to handle similar events that were found in Notes forms like QueryOpen, QuerySave, PostSave and so forth.  Many Notes applications made heavy use of these events, we couldn’t just leave them out now, could we?

DOCOVA implements these events in a similar fashion because they are useful and it makes migrating Notes application to DOCOVA much easier.  I mean, could you imagine having to try to implement these events in some other target collaboration platform aside from DOCOVA?  Good luck with that.

Comment below.

You can fast-track and get all the whitepapers on our migration methodology and everything that is being discussed in this series of posts.  Specifically, you can get the DOCOVA Notes/Domino Migration Methodology – MIGRATE whitepaper

By |May 23rd, 2017|Notes Migration, Technical|Comments Off on Migrate Notes to DOCOVA Blog Series Part 16: Form events

Migrate Notes to DOCOVA Blog Series Part 15: Private on first use folders

Welcome to blog series part 15 of 17 on migrating Notes apps to DOCOVA..  In this entry I’m going to talk about good ‘ol Private on first use folders.

This is another one of those “interesting” Notes application design constructs.  In my journeys I don’t think I’ve ever come across this same sort of construct in any other application environment.  Anywhere.  Ever.  Sure, a private folder, but “…on first use” is the kicker.  Interestingly, this construct can be implemented with some creativity behind it.

DOCOVA supports “Private on first use folders”, depicted as “Content personal to each user”.  So, when a person accesses a “view” as a folder, it will be treated as though this folder is private to the user.

This is most useful when selecting documents manually.  One way that Notes applications leveraged this design construct in the past was that sometimes a search was performed to gather documents together and then present them to the specific User doing the search via this folder type.

There you go.  Supported.

Comment below.

You can fast-track and get all the whitepapers on our migration methodology and everything that is being discussed in this series of posts.  Specifically, you can get the DOCOVA Notes/Domino Migration Methodology – MIGRATE whitepaper

By |May 18th, 2017|Notes Migration, Technical|Comments Off on Migrate Notes to DOCOVA Blog Series Part 15: Private on first use folders