Using the Form importer

The Form Importer can be used to import the definition of an LN session into the LN Studio. For details on the Form Importer and its usage, refer to the LN Studio online help.

Some specifics for LN:

• The session code is used as the form’s identifier. In case of synchronized sessions (using a multi-occurrence and a single-occurrence session), the Table.name will contain both session codes, separated by an underscore. For example: ‘ppmmm0501m000_ppmmm0101s000’. This is also the case if a single session is used for both the multi- and the single-occurrence screen. For example: ‘ppmmm0101m000_ppmmm0101m000’.
• Just like a database table, a form must have a key (primary index) defined. This is needed to set the corresponding fields for Read, Change and Delete. In case of synchronized sessions, the index will be taken from the first session (which is the multi-occurrence session).
• For a multi-occurrence session the session’s view fields must be known. These are defined in a special index named ‘view’. In case of synchronized sessions, the view will be taken from the first session (which is the multi-occurrence session).
• Display-only fields are irrelevant in the form definition, because a screen scraping implementation can only be used for the Create, Change and Delete methods.
• Regarding interaction points, the form importer for LN does not make use of interaction points. At runtime, questions in LN will get their default answer.