Building an extension

To build an extension:

  1. Start the Extensions (ttext1500m000) session and click New.
  2. Select the Extension Point and specify the Component Name.
    Accept the proposed default in Library or specify your own Library code. Note that the package (tx) and the proposed module (esb, esm, esr, ess, est; see Extension scripts) cannot be changed.
  3. Click Save changes and Exit.
  4. Select the Extension. Click Actions and select Check-Out.
  5. Click Extension Modeler.
  6. In the Extension Modeler specify the Properties on component level, if applicable.
  7. To implement a hook, right-click the hook and select Add Implementation or double-click the hook.
  8. Click Add to add other extension types for the extension and fill the properties and hooks for those levels.
    The extension types, hooks and properties depend on the extension point to build an extension for.

    For some extension types, it is important in what order they are shown in the UI. For example calculated fields in a session, or custom menu items in a menu require a specific order. Use drag-and-drop in the extension types tree to define the desired order.

  9. Click Save to save the extension. The extension script is automatically generated during save.
    Compilation issues can be displayed in the Problems view. Solve those problems and click Save.
    Note:  If a compilation problem must be solved in another component, for example a library which you created with LN Studio, click Generate and Compile after changing that other component.
  10. Test the extension by starting the session(s) that would open the extension functionality. For testing a BOD extension, we recommend that you run the relevant BOD publishing session in simulation mode.
    Go to the Common menu under BOD Messaging > Publish BODs.
  11. Close the Extension Modeler.
  12. Click Actions and select Check-In.
  13. Accept the default revision text or type your own text and click Save changes and exit.
    Before you checked-in the extension, the new extension or the new version of the extension was only available for you. After check-in, the most recent version of the extension is available to all users who set their activity context to your activity.
  14. Click Actions and select Commit.
    The, new version of the, extension is available to all users.