Welcome to blog series part 4 of 17 on migrating Notes apps to DOCOVA. In this blog entry I’ll talk about richtext and how it gets migrated over.
So, first off, there is no such thing as a “richtext” field in a browser as compared to what a richtext field is in a Notes client. If you are running DOCOVA on a Domino platform rather than one of the other SQL database platforms, DOCOVA RT remains RT and is rendered to HTML by the server when the page/form is first loaded. From that point on it is treated and stored as HTML content. On non-Domino SQL platforms as part of the migration and we convert the RT content to HTML and store it as HTML.
With DOCOVA, when creating or editing a page/form in DOCOVA, a couple of HTML editor options are used to enable much of the functionality that a richtext field had in the Notes client. One of the HTML editors is the TinyMCE plugin and the other is a custom DOCOVA HTML editor that we’ve built.
One question that gets asked is what happens to the doclinks that were in richtext fields? When migrating data from Notes documents that have richtext fields that contain doclinks, we track which documents have the doclinks and what those links are “hooked” to. As we migrate the data we keep track of what documents have the doclinks and what the doclinks are connected to so that once the data lands in DOCOVA the links are reconnected.
Additionally, DOCOVA’s API has a richtext navigator class that operates similarly to the NotesRichtextNavigator class to support any code that might leverage this class.
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.
Please leave any comments/feedback below!