This table shows the types of activities you can define:

During its life cycle an activity can have these statuses:

• Created – The activity is created in Project Server.
• Opened – The activity is opened, at least once, in the Activity Explorer.
• Cancelled – The activity is cancelled. To re-use the activity, you can open the activity again through the Activity Explorer.
• Closed – The activity is closed through the End Activity command in the Activity Explorer.
• Finalized - The activity is delivered through a PMC solution.

Project Managers can create software projects and activities through the Software Project Explorer.

By default, the components in this VRC are only accessible for the software engineer to which the activity is assigned. Optionally other software engineers can access these components if they put this activity in the activity context of their own activity.

From a development perspective, a Business Object is a collection of tables and functions that manipulate tables implemented simultaneously as one group during the development phase. A Business Object is identified by the combination of a package code, module code, and Business Object code.

For example, it defines the type of graph, thickness of lines, size of bars, and colors. The following default chart types are present in LN:

• Bar
• Layer
• Line
• Pie
• Scatter
• Stacked bar

The important ideas about classes are as follows:

• A class can have subclasses that can inherit all or some of the characteristics of the class.
• In relation to each subclass, the class becomes the superclass.
• Subclasses can also define their own methods and variables that are not part of their superclass.
• The structure of a class and its subclasses is called the class hierarchy.

LN Studio uses these connection points:

• ProjectServer
• Administrator
• Debug
• Development Address
• Runtime Address
• RuntimeRepositoryConnection
• TestServerConnection

These debugging techniques are available:

• Definition of conditions that suspend a running process, so you can inspect it more closely
• Navigation through a suspended process, to discover the flow and identify any problems
• Inspection, to validate the state of the process and identify any problems

The following values indicate the dependency type between solutions.

These dependency types are available:

• Pre-requisites
• Co-requisites
• Post-requisites

You can only install solutions that are dependent on other solutions if the other solutions are already present, or are also installed.

The same dependency types exist between Patches. However, to keep the descriptions readable, only solutions are mentioned, but patches are meant as well. One exception applies: the post-requisite type is not applicable to patches.

A details session can contain a number of tabs to group related fields.

Domains indicate the valid values for an attribute and are used to define the scale division of the axes or to verify data.

The developer does not need to determine exactly where fields must be placed, or what they must look like. Instead, the developer defines the following:

• The form contents.
• The form structure.
• The sequence of the objects on the form.

At runtime, the dynamic form displays only those fields for which the user is authorized.

Depending on settings, a dynamic session can start as one of the following:

• A details session.
• An overview session.

In the dynamic form definition, the developer does not need to determine exactly where fields must be placed, or what they must look like. Instead, the developer specifies this information:

• The form contents.
• The form structure.
• The sequence of the objects on the form.

At runtime, the dynamic form shows fields for which the user is authorized.

Create Eclipse tasks through the Tasks view and the LN Studio script editor.

A form command, as opposed to standard menu commands such as the Exit command, must be especially defined for a session tab.

A function is a self-contained software routine that can perform a task for the program in which the function is written, or for another program.

When you perform an operation, such as copy, delete, check in, or check out, on an integrated session, you also perform the operation on the integrated session's form.

A non-integrated session's form is a separate object.

This table shows how the language code corresponds to the language number:

For example:

• Language code b = Language number 11
• Language code B = Language number 37

A module code consists of three characters. For example, the General Ledger has the code "gld".

When you add or change a record a details session usually starts. Sometimes, you can add and change records directly using the overview session.

A package code consists of two characters. For example, tt is the code of the Tools package.

Each package has a unique VRC version structure.

In the User Data (ttaad2500m000) session, each user is linked to a package combination. This determines which version of the software the user can use.

In the Companies (ttaad1100m000) session, each company is linked to a package combination. This indicates which version of LN is appropriate to handle the data in that company.

A developer can usually only modify software components in a particular package VRC.

The code of a package VRC consists of these components:

• Package code, such as tc
• A version (VRC) code, such as B61O a cus1, built up of these components:
  • Version
  • Release
  • Customer

In LN Studio, these perspectives are used:

• Application
• Debug
• Integration
• Integration Test
• Project Server

PMC uses a version number in the solution dumps to ensure that the PMC software at the recipient side can process these dumps. If the PMC version at the recipient side is too low to process a particular dump, then an error message is displayed. In this error message, a solution number is displayed. You must first install this solution, before you can process the original solution dump.

This mechanism enables you to change the format of the PMC dumps when you must include new functionality.

The PMC version is linked to every update. This guarantees that various formats of PMC solution dumps are handled by the correct version of the PMC software. After installing solution 2177498, the PMC version of the client can be found in the Parameters (ttpmc0100s000) session.

The PMC version to be used at the distributor side depends on these factors:

• The Enterprise Server version (Infor LN Tools version) at the distributor side
• The functionality you want to use in PMC
• The Enterprise Server version of the customers for which you are creating PMC solutions

You can edit the PMC version at the distributor side in the Base VRC Combinations (ttpmc0111m000) session.

Private VRCs are only used if SCM is active for the application to which the activity belongs.

Synonym: UI script

The projects and activities are stored on the Project Server.

The project VRC is the Export VRC linked to the Base VRC of the Application to which the project belongs. This VRC also contains finished software components for other projects defined for the same application.

A reference can have one of the following reference modes:

• Mandatory

  The field must contain a code found in the reference table.

• Mandatory unless empty

  The field can be empty. If not, it must contain a code found in the reference table.

• Not mandatory

  The field can be filled with a code not found in the reference table. The reference speeds up queries.

Example:

• One of the fields of the Items – General table is the Country of Origin (coor) field. This field can contain a country code. (The field can also be left empty.) LN stores country codes in the Countries table. To control this connection, the Country of Origin table field in the Items – General table has a reference to the Countries table.
• Items – General is the referral table and Countries is the reference table.

Example:

• One of the fields of the Items – General table is the Country of Origin (coor) field. This field can contain a country code, but can also be left empty. LN stores country codes in the Countries table. To control this connection, the Country of Origin table field in the Items – General table has a reference to the Countries table.
• Items – General is the referral table and Countries is the reference table.

The rules used by VSC are based on the Infor LN Software Coding Standards (SCS), the Infor LN Software Programming Standards (SPS), and the Infor LN Performance Guide.

These are examples of rules:

• A table code must have the following structure: pp mmm s xx, where pp is the package code, mmm is the module code, s is the submodule code (only when numeric), and xx is the sequence number.
• A message called in a script should not be expired.
• A query that performs an update must have a 'with retry' clause.

Most rules are hardcoded in the VSC software. However, some rules used to analyze scripts are implemented as source analyze codes.

The rule database contains this information:

• Detailed information about the rules implemented in VSC.
• Information about rules that might be added to future VSC versions.

This database is intended for internal use by the LN development department. It is therefore not delivered with the VSC software.

The code of a session consists of a package code, a module code, four digits that indicate the main table number and the session type, an m or an s, and three additional digits, such as Countries (tcmcs0510m000).

• Message
• Report
• Label
• Function
• Business Object
• Chart
• Integrated session
• Additional file
• Question
• Session
• Domain
• Table
• Menu
• Form
• Program script
• Library

During its life cycle a project can have these statuses:

• Created
• Active
• Cancelled
• Closed
• Finalized

Project Managers can create software projects and activities through the Software Project Explorer.

These statuses are only used at the recipient side, and must not be confused with the Solution status distributor at the distributor side.

• Available

  The solution or patch is scanned and available on the system.

• To Install

  The solution or patch is checked and is ready to be installed.

• Saving

  A backup of the components is being saved.

  This status is not applicable for patches.

• Installing

  During the installing process the solution or patch has this status.

• Installed

  The solution or patch is installed.

• To Uninstall

  The solution or patch is checked to be uninstalled.

• Uninstalling

  During the uninstalling process, the solution or patch has this status.

Each source analyze code is linked to an expression text and to a warning message. The expression text contains a search pattern, which is used to find errors.

See "Source Analyze Codes" in the Web Help on the LN server.

A solution supersedes another solution if the following conditions are met:

• The superseding solution contains at least all the components of the other solution.
• The superseding solution contains newer versions of these components.
• The superseded solution is not yet installed. If the superseded solution is already installed, speaking of a superseding solution is illogical.

A table code consists of a package code, module code, and three digits.

Example

Table: tc mcs010 Countries

Updates can be delivered in four different configurations:

• Solutions
• Collections
• Patches
• Service Packs

A verification code is usually linked to one or more verification filters.

A verification code is usually linked to one generic verification filter and one or more specific verification filters.

The generic filter defines the checks executed to verify all software components in all packages. Depending on the filter settings, the checks in the generic filter can generate two types of warnings:

• "Filtered to Handle" warnings. You must solve or accept these filtered warnings immediately.
• "Non-filtered" warnings you do not have to handle immediately.

Specific filters are used to reduce the number of "FiItered to Handle" warnings for a specific package, module or VRC. Each specific filter is derived from the generic filter, and therefore executes exactly the same checks as the generic filter. In a specific filter, indicate for each check whether you want to generate "FiItered to Handle" warnings or "Non-filtered" warnings.

These are typical LN Studio views:

• Activity Explorer
• Software Project Explorer
• Component Explorer

Depending on the verification filter settings, VSC generates the following:

• "Filtered to Handle" warnings. You must solve or accept these filtered warnings immediately.
• "Non-filtered" warnings you do not have to handle immediately.

Use a zoom session to enter the code of an existing record, such as an item, order type, or warehouse in another session.

To start a zoom session, click the browse arrow button behind the field or press CTRL+B.