Text EN Version 1.90

Engine Import Script

Description

Example of an Engine Import Script Document:
This is an old method for enabling imports. For compatibility reasons, it is still supported, but it should no longer be used for new imports (deprecated!).
New imports should be implemented using Engine scripts. For this purpose, numerous powerful @Functions are available.

The following is the description of this feature. (deprecated!)
Import-Script !!TEST_IMPORT

Script Administration settings

Script Name:
!!TEST_IMPORT

Category:
DEVELOPMENT
Version:

Distribution:

Toolbox:
No
Application:

CryptInherit:

Import Script

SECTION SYSTEM;

SECTION IMPORT;
A, 20,"",Section;
A, 40,"",SubSection;
A, 5,"",Number;

SECTION REFERENCE;
SECTION INIT;

SECTION PROCESSING;
Form[MAIN]:="How To";
Topic[MAIN]:=@Trim(Topic[MAIN]);
Section[MAIN]:=@Trim(Section[MAIN]);
SubSection[MAIN]:=@Trim(SubSection[MAIN]);
Number[MAIN]:=@Trim(Number[MAIN]);
SECTION EOF;
SECTION END;

Script Comments

Simple import script. LineFeed is used as the record separator. The fields have a fixed length. In the Processing section, the Form field is added to the Notes document. The excess spaces are removed from the remaining fields. The records read in are automatically written to the Notes database (SaveMain=1)

Document History

Author:
23.11.94 15:01:57 – OBDVO01/OBDVO
Modified:

Under Script Name: enter the name under which this document should be found again
(see Control Document Name).
Under Import Script: enter the program to be executed (see SECTION’s).
Under Category: enter the category under which the IDF document should appear.
Under Comments: various information can be stored.
Under Update History: shows who last changed the document and when.

All local variables exist across SECTIONs. (For example, local variables defined in SECTION INIT are still valid in SECTION PROCESSING.)

Tabs may only be used in SECTIONs in which formulas may occur; otherwise malfunctions will definitely occur. The same applies to comments.

The order of the SECTIONs must be strictly observed. No SECTION can be omitted. If it is not needed, the next
SECTION.

Example: SECTION INIT is not needed:

SECTION INIT;
SECTION PROCESSING;

Note : This text was machine-translated and may contain inaccuracies.