Extension Type Registry view

Administration System Extension Type Registry Extension Type Registry view

The Extension Type Registry view displays the extension types available in N4. An extension type specifies how and where a code extension may be used. Extension types can be provided as part of the N4 framework, or they may be implemented by third-party application developers. They are loaded into the memory at run time.

When implementing code extensions, you must comply with the Java interface. Externally supported APIs have the com.navis.external interface.

For more information on the mandatory attributes, see Extension Type Registry Columns (on page 1).

You cannot add or edit the extension types in this view.

For more information on the available extension types, see Code extension types (on page 1).

For information on the Java API, see the documentation provided under Help Java API Docs.

In some N4 versions, the link to this resource is not working. As a workaround, you can access the Java API docs directly from the N4 footprint installed on your server. From within the N4 application footprint, manually open the index.html file that is located at the following location (you should only see one of the following directory paths, not both):
Navis/sparcsn4/webapps/apex/argo/api/index.html
Navis/sparcsn4/webapps/apex/model/index.html

Extension Type Registry Columns

Short Label	Long Label	Description	Sorting?
Abstract Base Class	Abstract Base Class	The implemented Java interface that is invoked by a specific invoker along with helper classes (verify this is correct), such as com.navis.external.framework.entity. EEntityLifecycleInterceptor for framework entity interception.	X
Instantiation Mode	Instantiation Mode	The creation mode of the extension type, which can be one of the following: SINGLETON: N4 always uses the same code extension (groovy class) instance for all executions. PROTOTYPE: N4 always creates a new code extension instance at each execution.	X
Interface	Interface	The Java interface methods called by N4.	X
Introduced	Introduced	The framework version that introduced the extension type.	X
Module	Module	The N4 module the extension type is tied to, such as framework, EDI, or inventory. For a list of modules, see Module Versions view.	X
Transaction Mode	Transaction Mode	The transaction context in which the extension type is called, such as: NONE: No transaction has been provided. All transaction handling must be done explicitly. Example code extension types: All UI extensions, such as TABLE_VIEW_COMMAND. NEW: Automatically opens a new transaction for the calling of the extension. Preexisting transactions are not allowed. Errors affect only the code extension. Example code extension types: TRANSACTED_BUSINESS_FUCNTIONS, GENERAL_NOTICES_CODE_EXTENSION. PREEXISTING: Uses whatever transaction was used for the process. Any errors will cause the main transaction to roll back. SECONDARY: Entity lifecycle callbacks in a second inner session. Any errors will cause the main transaction to rollback. Strict limitations apply. UNKNOWN: A mode was specified. The transactional mode is unknown if the code extension type is any of the following: LIBRARY, which can be called in different settings Legacy	X
Trigger Mapping	Trigger Mapping	The entity that uses the extension type.	X
Type Desc	Type Desc	The description of the extension type.	X
Type ID	Type ID	The unique ID for the extension type.	X
Type Name	Type Name	The name of the extension type.	X