Welcome to blog series part 8 of 17 on migrating Notes apps to DOCOVA.  In this entry I’m going to go over profile documents.

In Notes apps, profile docs were convenient for, and typically used for, holding application settings type information.  The information on profile docs was easily gotten with @formula commands like @GetProfileField.

The question is: Does DOCOVA support profile documents?

Yes.  If a Notes application used profile documents then they will be supported in the migrated application in DOCOVA.  When migrating, of course the related profile document’s form will get migrated.  DOCOVA knows, based on how the form is edited, that the generated/updated document is to be treated as a profile document and saves it as such, similar to the way Domino handled profile docs.

When the data of a Notes application is migrated, DOCOVA App Importer™ knows when a document is is a profile type document and will handle the conversion on the DOCOVA side.

@Formula methods like @GetProfileField and @SetProfileField are supported in DOCOVAScript™ as $$GetProfileField and $$SetProfileField as well as $$Command([EditProfile]).

If you’ve used profile documents in any of your Notes applications, when they are migrated over to DOCOVA, you can still use them in the same fashion as you did in Notes, and use them in any newly created DOCOVA apps too.

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.

Post comments and questions below!