# Install Extension in Application

After successfully building the Extension **JAR file** from the workspace, the next step is to **install the extension into an application** so that it can be used as a **Custom Activity Node** in Process Designer.

Once installed, the extension becomes available in the Activity Nodes palette and can be reused across workflows within that application.

***

### Accessing the Install Extension Menu

To install an extension:

1. Open **Process Designer**
2. Click the **Extensions** icon ![](https://docs.oneweb.tech/oneweb/~gitbook/image?url=https%3A%2F%2F2015371994-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FMpDjHWFRUtZ5nJcSfVXd%252Fuploads%252F0Zz2aESePJZdzMyBPTxV%252F0%3Falt%3Dmedia\&width=300\&dpr=3\&quality=100\&sign=25f22e82\&sv=2)
3. Select **Install Extension**

The **Install Extension** page will be opened.

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2F3s8pyaT5kotHYFAEUapo%2F1?alt=media" alt=""><figcaption></figcaption></figure>

***

### Selecting the Extension JAR File

On the **Install Extension** page:

1. Browse and select the **JAR file** generated from the workspace build
2. Click the **Get Class Name** button

The system will automatically:

* Retrieve the execution class name
* Load extension metadata
* Populate other configuration details from the JAR file

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FwGEDXyI8qOv2hXNzSszK%2F2?alt=media" alt=""><figcaption></figcaption></figure>

Verify that all retrieved information is correct before proceeding.

***

### Previewing Extension Details

Before installation, users can preview the extension configuration to ensure correctness.

#### View Input & Output Models

* Click the **View** button to inspect:
  * Input Business Object
  * Output Business Object

#### Node Preview

* The **Node Extension** section displays:
  * Custom node icon
  * Node color
  * Look and feel of the activity node in Process Designer

This preview helps validate both **functional** and **visual** aspects of the extension.

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FCybbOFphJ95xFCwi0Pe6%2F3?alt=media" alt=""><figcaption></figcaption></figure>

***

### Installing the Extension

Once all details are verified:

1. Click the **Install Extension** button
2. The system installs the extension into the current application
3. A confirmation message is displayed indicating **successful installation**

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FOuJHIbRiPlesdDva55IY%2F4?alt=media" alt=""><figcaption></figcaption></figure>

***

### After Installation

After installation:

* The custom extension appears as an **Activity Node**
* It can be dragged and dropped into the Process Template Diagram
* The node behaves like a native activity node
* Input and output parameters can be mapped normally
* The extension can be used in multiple workflows within the application

***

### Usage Guidelines

* Install only tested and verified extension JARs
* Reinstall the extension when upgrading to a new version
* Ensure compatibility when updating existing extensions
* Validate workflows after installing or updating extensions
* Use meaningful versioning for extension JAR files

***

### Summary

Installing an extension makes a **Custom Activity Node** available for use in Process Designer.

Key points:

* Extensions are installed via **Extensions → Install Extension**
* Extension logic is loaded from a JAR file
* Class and metadata are retrieved automatically
* Users can preview input/output models and node UI
* Installed extensions are reusable within the application

This step completes the **Custom Extension lifecycle**, enabling developers to integrate reusable, enterprise‑specific functionality directly into ONEWEB process workflows.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.onewebstack.com/designer-reference/process-designer/process-designer-component/custom-extensions/install-extension-in-application.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.