# Enabling your applications

This article explains how to copy or update SWING PDF Converter's design elements in a custom Notes application.

The design elements may be copied/updated automatically (using the **Update** action in your SWING PDF Converter database) or by replacing the design elements manually.&#x20;

Once you've copied the required design elements into your application, you can invoke the PDF rendering functions using our [Lotus Script API](/pdf-converter-for-notes/for-developers/lotusscript-api-reference.md).

## **Automated design replacement**

1\. Download SWING PDF Converter (using the download link provided by SWING Software) and extract the **PDFConverter.nsf** file from the ZIP package to an appropriate location.

2\. Open the **PDFConverter.nsf** file and activate the product using your product license key.

3\. Click **For Developers** in the Administration menu  and click **Update**:

![](/files/-MlGB7gd1BEYveaYxsRw)

4\. In the pop-up which appears, locate and select the custom application which is being upgraded and click **OK**.&#x20;

After that, the existing PDF Converter's design elements in the custom application will be replaced wit the new ones:

![Select database](https://sites.google.com/a/swingsoftware.com/lc/_/rsrc/1368104537996/pdf-converter/installation/3/design-update/select-database.png?height=287\&width=400)

5\. Finally, sign your database with Server ID (or other unrestricted ID).

**NOTE:** If your application runs on a server, then after copying the required design elements you will also need to start a conversion job once on the server (in order to extract required .jar files) and restart your server. The server-side conversion job can be executed by creating a scheduled agent on Domino server that runs the SWING PDF Converter API or by running the agent manually from Lotus Notes with the "**agent.RunOnServer"** LotusScript command.

## **Manual design replacement**

1\. Open your custom application in Domino Designer.

2\. If you have previously installed PDF Converter in this application, delete all the design elements that are showing the **"SWING Software"**, **"SWING Software - HIDDEN"**, **"SWING PDF Converter - HIDDEN"** or **"SWING PDF Converter"** comments (see below image). Otherwise skip this step.

![](/files/-MlGBE77bGPvweiG0ZRP)

3\. Open the SWING PDF Converter database in Domino Designer.

4\. Copy all the design elements that are showing the **"SWING Software"**, **"SWING Software - HIDDEN"**, **"SWING PDF Converter - HIDDEN"** or **"SWING PDF Converter"** comments and paste them into your custom application.

5\. Finally, sign your database with Server ID (or other unrestricted ID).

{% hint style="warning" %}
**WARNING:** Some SWING PDF Converter elements are provided in hidden design. It is not recommended to open them in Domino Designer (by double clicking them in order to show their code) since this action can corrupt the hidden code.
{% endhint %}

{% hint style="info" %}
**Note:** If your application runs on a server, then after copying the required design elements you will also need to start a conversion job once on the server (in order to extract required .jar files) and restart your server. The server-side conversion job can be executed by creating a scheduled agent on Domino server that runs the SWING PDF Converter API or by running the agent manually from Lotus Notes with the **"agent.RunOnServer"** LotusScript command.
{% endhint %}


---

# 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.swingsoftware.com/pdf-converter-for-notes/for-developers/enabling-your-applications.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.
