Getting started with extensions

Start the Initialize Extensibility (ttext0200m000) session.

If your current package combination already has the Extensions (tx) package, this package VRC is displayed. You cannot change this VRC. If your current package combination does not have the Extensions package, you can use the default VRC (B61O_a_ext). If required, you can change the VRC name. Do not choose an existing VRC that is already used in another package combination. All package combinations require a different VRC for the Extensions (tx) package.

Note: Developing extensions always applies to the current package combination. There is no inheritance through a VRC-derivation structure. It is not supported to have a derivation structure for the tx package.

To use Software Configuration Management (SCM), select Use SCM and specify a Development VRC to be created. The Use SCM option is only available if your LN server is prepared to use SCM.

For more information about Software Configuration Management, see the Infor LN Studio Application Development Guide.

Note: Activating SCM is not required to keep the revisions of your extensions. History of extensions is always available and you can restore old revisions; see Extension history. If you use SCM, you can isolate checked-out changes from other extension developers when you share development activities.

Click Initialize. Close the session.

Select in the menu, to restart your LN environment.

By default, your Extensibility environment is setup with the Extensions Ready for Cloud setting. See Cloud readiness.

If you are not running LN in a cloud environment, you can switch off this setting: Start the Extensibility Parameters (ttext0100m000) session. Clear the Extensions Ready for Cloud check box and click Save.

Start the Extensions (ttext1500m000) session to create extensions. For the procedure to create the extensions, see the Extension development procedure.