As we know by now with HCL Leap you cannot modify an existing application but must start from scratch by creating a new one.

One situation you may run into is the need to transform an existing application into a Leap : it is entirely possible to recreate an application in HCL Leap with the names and field formats mirroring the existing one but once everything is prepared it becomes necessary to import data from the existing application.

This is also feasible but with some caveats: suppose I create a script in LotusScript that does the job for me: momneto I create a new document in an HCL Leap database I must keep in mind some mandatory steps.

The name of the form must obviously respect the one created in the Leap database which is not at all mnemonic but appears like this : .Form = “6b991a98-65c8-472a-85e4-aabf62a7831b”

Each document has ( or should have) a workflow or stage status and so this must be reported. The default in Leap is ST_Submitted but this can obviously vary depending on what your application looks like. Let’s say that for the default case you should have a .stage statement = “ST_Submitted”

Another important aspect is the UID field in Leap, which is analogous to the well-known UniversalID in Notes but with a different format. In fact, the UID field contains groups of hexadecimal characters separated by the sign – .
You can read it in any record created with leap where the field looks like this: “943a0cd1-485c-e378-c125-8c9f005b6922” So it is 32 characters as for universalID but with die signs – to divide the groups.

At this point the best system I have found to handle the field is to use the universalID as a starting point : this way I don’t have to create code to generate the UID or verify that it is really unique : think of all Notes.
So create my document, save it so that I have the universalID calculated and then from the universalID I create the UID that Leap needs in this way :

Call doc.save(True,False) 
unid = LCase(doc.Universalid) 
uid = Left(unid,8) + "-" + Right(Left(unid,12),4) + "-" + Right(Left(unid,16),4)+ "-" + Right(Left(unid,20),4)+ "-" + Right(unid,12)

Only any author/reader fields remain to be considered at this point, but these we know well how to handle with LotusScript and are not a problem.