3 2 3 Steps for Completing Fields in Repository

Visual LANSA

3.2.3 Steps for Completing Fields in Repository

The basic development steps to build your fields in the LANSA Repository will depend upon the approach used to create the initial field definitions.

These approaches have been described:

Manually Define New Fields

Use Modeling Tools

Load Other Files

Manually Define New Fields

You may create a new field in the repository by manually defining the field or by copying an existing field. You may use a Reference Field to create the new field. As you create a new field, you should complete the following steps:

1.  Use proper naming standards when the field is created. These are described in the 3.1.3 Corporate Data Dictionary Concept.

2.  Set all required field characteristics based on your site standards. (Refer to 3.2.7 Field Considerations.)

3.  Define field level help text for the user and the developer. (Refer to 3.4 Repository Help Text Development.)

4.  Create field visualizations if required for component or WAM development. (Refer to 3.6 Field Visualization Development.)

5.  Optional: In special cases, field level rules and triggers can be added. (Refer to 3.6 Field Visualization Development.)

6.  Test your field definitions by using a simple test function. (For example, you can use the FLDTEST application template.)

Use Modeling Tools

If you have used a modeling tool to create the database, the basic field definitions are automatically created for you. Most field definitions will use Reference Field based on attribute data types that are part of the modeling tool. You will complete the following steps to update field definitions:

1.  Open each field created by the modeling tool.

2.  Review and update changeable field characteristics where necessary. (Refer to Field Considerations.)

3.  If help was not added during the modeling phase, define field level help text for the user and the developer. (Refer to Repository Help Text Development.)

4.  Create field visualizations if required for component or WAM development. (Refer to Field Visualization Development.)

5.  Optional: In special cases, field level rules and triggers can be added. (Refer to Field Rules and Triggers Development.)

6.  Test your field definitions by using a simple test function or by using an application prototype.

Load Other Files

If you have loaded other files to use an existing database, all fields in the files are automatically added to the repository. You will complete the following steps to update field definitions:

1.  Review file definitions to identify created fields in the Repository.

2.  Open each field created when the file was loaded. Review and update the field characteristics. (Refer to Field Considerations.)

3.  Define field level help text for the user and the developer. (Refer to Repository Help Text Development.)

4.  Create field visualizations if required for component or WAM development. (Refer to Field Visualization Development.)

5.  Optional: In special cases, field level rules and triggers can be added. (Refer to Field Rules and Triggers Development.)

6.  Test your field definitions by using a simple test function.

Also See

3.2.5 Reference Fields

Ý 3.2 Developing with Fields