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

Notes Migration

Migrate Notes to DOCOVA Blog Series Part 12: Multi-value fields

Welcome to blog series part 12 of 17 on migrating Notes apps to DOCOVA.  In this entry it’s all about multi-value fields.

Notes had the concept of multi-value fields on forms.  All fields were basically treated as arrays of values.  For example when addressing field values in LotusScript, you might write some code like;

Dim myval = doc.myfield(0)  (where doc is a NotesDocument)

Although it’s a bit of an odd duck, DOCOVA supports the same type of addressing when it comes to form fields.  It’s easier to migrate the code over and easy for Notes developers to quickly understand and use. Thus something like doc.myfield(0) is translated into doc.getfield(“myfield”)[0] in JavaScript.

Or, for a list of fields;
Var myfields = doc.getFields(myfieldlist) and get the field with myfields.myfieldname[0]

One additional important note as it relates to multi-value fields is that if a multi-value field is used in a view column, DOCOVA “views” support the “Show multiple values as separate entries” option.  From a techy point of view, in a relational database environment, I should be able to hear people saying “wow” right about now.

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 9th, 2017|Notes Migration, Technical|Comments Off on Migrate Notes to DOCOVA Blog Series Part 12: Multi-value fields

Migrate Notes to DOCOVA Blog Series Part 11: Pass-thru HTML and Generate HTML for all fields

Welcome to blog series part 11 of 17 on migrating Notes apps to DOCOVA. In this entry I’m going to talk about “Pass-thru HTML and Generate HTML for all fields”.

A neat aspect of forms development in Notes was the ability to treat text on a form as pass-thru HTML.  This meant that you could add HTML and inline JavaScript directly onto your forms and mark it as pass-thru so that the Domino server would let the text “pass-thru” as HTML/JavaScript when the form was being rendered via a browser.

DOCOVA’s App Builder allows developers to achieve the same thing so that they can put HTML and inline JavaScript directly onto a form/subform.  Aside from a typical “block” of HTML, DOCOVA allows the developer to surround other elements, like Computed Text as an example.  Hence something like ComputedText can be leveraged in the pass-thru HTML or JavaScript.  For example, a developer can hide or show content based on an @formula placed in Computed Text in the style of an HTML element.

This functionality opens up a huge variety of permutation around mixing HTML/JavaScript and elemental constructs.

When importing Notes applications into DOCOVA, text marked as pass-thru HTML/JavaScript is treated in a similar fashion and supported in DOCOVA.

On Notes forms, when rendered in a browser, if a field was computed, computed for display or computed when composed, there was no “id” or “name” attributes assigned to those fields, meaning, there was no way to address those fields.  So, turn on “Generate HTML for all fields” and voila, now you had a way to address these fields.

Since DOCOVA supports computed, computed for display and computed when composed fields, we felt it was fitting for DOCOVA to always auto-generate the relevant HTML for those types of fields so that they are always accessible in the browser for whatever your functionality needs are.

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 4th, 2017|Notes Migration, Technical|Comments Off on Migrate Notes to DOCOVA Blog Series Part 11: Pass-thru HTML and Generate HTML for all fields

Migrate Notes to DOCOVA Blog Series Part 10: Refresh fields on keyword change

Welcome to blog series part 10 of 17 on migrating Notes apps to DOCOVA.  In this entry it’s all about “Refresh fields on keyword change”.

Ya, let’s take a moment to just love this one.  Have you ever used it in your Notes apps?  Refresh fields on keyword change was a bit of an odd beast, no?  The purpose of this operation was to enable field options (or values) to be recalculated based on the change of a selection field.

For example, if you had one keyword field on a form named [State] and another keyword field on your form named [City] when you open the form you could get all the States as options to choose from in the State field keyword field, however if the City field was based on what State was selected, then you need to have the City field recalculate what list of cities to show to the user.

Notes forms accomplished this by using the “Refresh fields on keyword change” option.  Although maybe you could argue that it worked fine in a Notes client, in a browser, the page reload, aside from super inefficient, would cause the page/form to jump back to the top of the page as due to the refresh.  Traditionally, with JavaScript, you’d typically load up all possible options in some multi-dimensional array…fast…and not too complicated unless you needed to add a third or more selection fields to the mix. Ugh.  A better way is to use an AJAX or JSON call to retrieve the new options.

In DOCOVA, keyword type fields like selection dropdown fields, checkboxes and radio buttons can all be hooked together in the App Builder so that they track each other and can independently get the options lists they need dynamically with no need for a “Refresh fields” option.  DOCOVA leverages AJAX to accomplish this but the real convenience is the ease with which a developer can hook up this common form control functionality.

It’s a super convenient option in DOCOVA that I love.  Chime in with your “Refresh fields on keyword change” encounters in the comments 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 which goes over these technical aspects.

By |May 2nd, 2017|Notes Migration, Technical|Comments Off on Migrate Notes to DOCOVA Blog Series Part 10: Refresh fields on keyword change