l4wdplb2_0045

Built-In Functions

3GL User Defined Built-In Functions will automatically find the associated DLL when the package is built if the Visual LANSA naming convention is followed.
RDML User Defined Built-In Functions can be selected to enable the deployment of the internal definition. The associated function must be added manually to the package.
The associated DLLs can be included in your package by selecting Deploy Execution Add-ons in the 8.3 Settings.

Editor Lists

When an Editor List is selected all objects currently included in the Editor List will be included in the package when it is saved.
When the package is saved, the individual objects will be saved but the selected Editor List is not included as an object.  To pick up any changes to the Editor List it must be added to the package again.

Fields

Field definitions only need to be deployed with an application if the application uses the LANSA repository help facilities.

Tables

Tables need to be included if the application accesses a windows database which is to be set up as part of the application installation.
Table data can also be included. Refer to 8.2.4 Table Data Processing.

Messages

Messages are grouped by the Language, Message File, and the first three characters of the message identifier
Use the Search icon on the toolbar, or double click the Non-LANSA objects in the tree, to locate and select the required messages.
Messages should only be deployed into other development systems.

Message Files

Message files only need to be selected when you are deploying to another development system.

Multilingual Variables

When grouped alphanumerically, Multilingual Variables are grouped by the first alphanumeric character after the *MTXT prefix of the Multilingual Variable name.
In Visual LANSA, Multilingual Variables are compiled into the application DLLs. There is no need to deploy Multilingual Variables, other than when you are deploying to another development system or to support web applications where multilingual variables are resolved at runtime.

Non-LANSA Objects

Non-LANSA objects can be any file available on your deployment environment.  They may be required to support 3^rd party software, such as ActiveX controls, or they could be parameter files or images used in your application which are not stored in the LANSA repository.
There is no definitive set of Non-LANSA objects associated with Visual LANSA.  These are objects external to LANSA which are required to run an application.  A single file can be selected or a directory structure .  When a directory structure is selected all sub-folders will be included based on the folder contents when the package is built.
Refer to 8.2.7 Configure the Non-LANSA Object Installation Path to understand how to control where the Non-LANSA object will be installed.

Objects from Task(s)

When a task is selected, all objects that have been modified under the task will be immediately included in the package. Removing the task will remove the objects.
Task with Open, Work or Closed status can be added to a package.
When the package is saved the individual objects will be saved but the selected task is not included as an object.
Tasks will only be available if your LANSA Environment is not configured as a VCS environment.

Processes and Function

Functions are available for selection as child items of Processes. If you select a Process, all Functions will be automatically included. If you select just a Function, the Process will be automatically included.

System Variables

Typically, System Variables only need to be included if you are deploying a web application. Process related Variables should be set up as part of Process and Functions cross referencing so that they are automatically included when the package is built.
System Variables related to List Graphical Variables must be included manually.

Technology Services

The standard Technology Services are defined under Technology Provider LANSA.
Technology Services will only be available if your LANSA Environment is configured to support WAM development.

Application templates

Application templates should only be included in packages for deployment to another LANSA development system. There is no need to include them in the package if you are deploying an execution-only application.

WAMs

When a WAM is selected the default layout Weblet for the WAM will be automatically added to the package.
WAMs will only be available if your LANSA Environment is configured to support WAM development.

Web Components

Web Components will only be available if your LANSA Environment is configured to support Web Event development.

Weblets

Weblets will only be available if your LANSA Environment is configured to support WAM development.