Extensions (ttext1500m000)

Use this session to create or update extensions.

Extensions are additions to the standard software without interfering with changes to the standard software. Extensions are stored in a different package (tx), and are not affected by updates on the standard software.

These extension features, or extension points can be defined:

Table Extension, which can be used for:
- Setting defaults and validation of customer defined fields (CDF’s).
Session Extension, which can be used for:
- Additional validation on form and table fields.
- Additional coding on before and after events of commands.
Report Extension, which can be used for:
- Additional coding on fields from the print session.
- Additional coding to include other fields.
BOD/BDE Extension which can be used to process the UserArea of a BOD/BDE
Menu Extension which can be used to hide standard menu items, or add new menu items.

Extensions are created and modified in the current activity of the user. After the changes are complete, the Commit command makes the extension available for all users. The Extension Modeler is used to define and model the extension in detail.

Actualizing the changes

To actualize the changes to runtime, run the Convert to Runtime Data Dictionary (ttadv5215m000) session. Follow the instructions described in the online help of that session.

Actions/Reference menu

These options are available:

Select Current Activity: Zooms to a session to select the activity, for current project / package combination. You can also create a new activity. This zoom session starts automatically after a change in the session is done and no current activity is available yet.
Check-Out: Check out the extension and extension script to the activity, or private, VRC. If the extension is already checked out, or linked to another activity, you cannot check out the extension.
Check-In: Check in the extension and extension script. If the extension is not checked out, or linked to another activity, you cannot check in the extension. You can check in if the extension script was generated and compiled without errors. The user is asked to fill the revision text. By default, the previous revision text is filled in, or the activity documentation text.
Undo Check-Out: Modifications to the extension since the last check out are undone. If the extension is not checked out, or linked to another activity, you cannot undo check out the extension.
Remove from Activity: Removes the extension and extension script from the activity. All modifications to the extension are undone. If the extension is linked to another activity, you cannot remove the extension.
Commit: Commit the extension and make the modifications to the extension available for all users. If the extension was not committed earlier, it is activated as well. If the extension is checked out or linked to another activity, you cannot commit the extension.
Activate: Activates the extension and makes it available for all users. If the extension was deactivated manually, the commit does not result in an active extension. In that case it must be activated again manually.
Deactivate: Deactivates the extension and makes it unavailable for all users.
Extension Modeler: Starts the Extension Modeler to define and model the selected extension. The Extension Modeler is started in read-only mode if the extension was checked out in another activity.
Start Debugger: Starts the Debugger (ttidedebugger). For details, see the Infor LN Debugger Workbench User Guide.
History: Shows the extension history.

Field Information

Extension Point: Specify BDE, BOD, Report, Session or Table.
Component Name: The specific BDE, BOD, Report, Session, Table for which the extension is created. It consists of the package, module and component specific remainder of the key.
Description: The description of the component from the component table or corresponding label.
Library: The code of the library that will contain the generated code and hooks to be executed at runtime. This library is generated in the dedicated package for extensions (“tx”).
Library Description: The description of the library from the Program Scripts / Libraries Table.
Activity: The development activity in which the extension is being created or modified. This field is blank when the activity is not created or modified.
Activity Description: The description from the activity table. This field is blank if is not created or modified.
Created by: User id of the user who created the extension initially.
Created by Name: Name of the user who created the extension initially, from the User table.
Creation Date: Date the extension was created initially.
Checked out by: User id of the user who checked out the extension. This field is blank if the extension is not checked out.
Checked out Name: Name of the user who checked out the extension, from User table. This field is blank if the extension is not checked out.
Check-Out Date: Date the extension was checked out. This field is blank if the extension is not checked out.
Checked in by: User id of the user who checked in the extension. This field is blank if the extension is not checked in within activity.
Checked In Name: Name of the user from the User table who checked in the extension. This field is blank if the extension is not checked in within activity.
Check-In Date: Date when the extension was checked in. This field is blank if the extension is not checked in within activity.
Active: Indicator whether the extension is activated.
Origin: Commit or Import. Not Applicable if the extension is new.
Activated by: User id of the user who (de)activated the extension. This field is blank if the extension is new.
Activated by Name: Name of the user who (de)activated the extension, from User table. This field is blank if the extension is new.
Date: The date when the extension was (de)activated. This field is blank if the extension is new.
Committed by: User Id of the user who committed the extension. his field is blank if the extension is not committed.
Committed by Name: Name of the user who committed the extension, from User table. This field is blank if the extension is not committed.
Commit Date: Date when the extension was committed. This field is blank if the extension is new.
Imported by: User id of the user who imported the extension. This field is blank if the extension is not imported.
Imported by Name: Name of the user who imported the extension, from User table. This field is blank if the extension is not imported.
Import Date: Date when the extension was imported. This field is blank if the extension is new.