# Overview

Product Documentation Overview

### Welcome to the SWING Software product documentation!

This is the place where you can find information about installing, configuring, and using [SWING Software products](https://www.swingsoftware.com). To view content for a specific product, please select from the following list:

{% content-ref url="/spaces/-MkmLDl5OXrWVfn2nv57" %}
[Seascape for Notes](https://docs.swingsoftware.com/seascape-for-notes/)
{% endcontent-ref %}

{% content-ref url="/spaces/-MlCAurE6RSGoCmtmAET" %}
[PDF Converter for Notes](https://docs.swingsoftware.com/pdf-converter-for-notes/)
{% endcontent-ref %}

{% content-ref url="/spaces/-MkpbT4Bt5ort6HdK9SP" %}
[Integrator for Notes](https://docs.swingsoftware.com/integrator-for-notes/)
{% endcontent-ref %}

{% content-ref url="/spaces/-MlByckakJAVY8Rukvr4" %}
[Porter for Outlook](https://docs.swingsoftware.com/porter-for-outlook/)
{% endcontent-ref %}

### Technical Support

You are a customer with a valid Software Subscription or Maintenance Plan, and have a product-related question or issue – let us give you a hand! Our technical support team is standing by to offer friendly, high-quality, responsive technical support. 

{% hint style="info" %}
Before you contact our Technical Support, please consult the FAQ lists and technical articles - someone may have already asked your question. It is also recommended that the latest update has been installed before reporting a problem with your software.
{% endhint %}

If you are unable to find the answer you are looking for, please submit your [Support Request](https://swingsoftware.freshdesk.com/support/tickets).

### Staying Connected <a href="#header-7" id="header-7"></a>

Use the following links to follow SWING Software:

* [LinkedIn](https://www.linkedin.com/company/swing-software/)
* [YouTube](https://www.youtube.com/swingsoftware)


# Seascape for Notes

Lotus Notes Data Migration and Archiving

### Welcome to the Seascape for Notes documentation!

This is the place where you can find information about installing, configuring, and using [SWING Seascape for Notes](https://www.swingsoftware.com/seascape-for-notes). Search this library for technical assistance articles and Frequently Asked Questions. Use the Search Box above to search by word or phrase.

### Technical Support

You are a customer with a valid Software Subscription or Maintenance Plan, and have a product-related question or issue – let us give you a hand! Our technical support team is standing by to offer friendly, high-quality, responsive technical support.

{% hint style="info" %}
Before you contact our Technical Support, please consult the FAQ lists and technical articles - someone may have already asked your question. It is also recommended that the latest update has been installed before reporting a problem with your software.
{% endhint %}

If you are unable to find the answer you are looking for, please submit your [Support Request](https://swingsoftware.freshdesk.com/support/tickets).

### Staying Connected <a href="#header-7" id="header-7"></a>

Use the following links to follow SWING Software:

* [LinkedIn](https://www.linkedin.com/company/swing-software/)
* [YouTube](https://www.youtube.com/swingsoftware)


# Installation


# Installing and activating

1\. Download the Seascape ZIP package and extract the NSF file from the package to your Notes Data directory (typically C:\Program Files (x86)\IBM\Notes\Data).

2\. Open the Seascape NSF file in Lotus Notes, and activate your installation using the license key provided to you by the vendor:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MkmSEtJPSNRdDdYhcGB%2F-MkmXZMNnXmQ3kTKwu4w%2Fimage.png?alt=media\&token=352f872e-8a66-4cb3-8041-a1c30b83f4ae)

If the activation was successful, a confirmation message will be shown:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MkmSEtJPSNRdDdYhcGB%2F-MkmXkbbixtrkyu09Gru%2Fimage.png?alt=media\&token=b6a5c01c-579c-40fe-81d2-6ef0e29128e5)

3\. Click **Next** to start the installation and extraction of the required resources to your system:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBMNBbkOB3IiRCuxuq%2F-MlBMTtcDq8nV1AS459a%2Fimage.png?alt=media\&token=6847c866-e61d-4a2f-9e11-06c3694052f2)

4\. Once the installation is completed a confirmation message appears as shown below. Restart your Notes client once and you are now ready to begin using the product:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBMNBbkOB3IiRCuxuq%2F-MlBMYnj7ypp1L9Nw_CQ%2Fimage.png?alt=media\&token=8d90f28f-e902-46b8-8a98-92b722bd3638)

## Important notes

{% hint style="info" %}

* In order for the Seascape users to be able to use the product correctly they will need to be assigned a **Designer** role in SWING Seascape database (or a higher role).
* The NSF file must be extracted from the ZIP package and save in the Data directory according to instructions above. Opening the NSF directly from the ZIP package will cause errors in product operation.
  {% endhint %}

{% hint style="info" %}
If you encounter **issues with your Notes password** (see below), please take a look at this article: <https://docs.swingsoftware.com/seascape-for-notes/troubleshooting/general-issues/notes-password-issue>
{% endhint %}

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2Fkhep3TfVMLPD3TDc2r8s%2FpassError.png?alt=media&amp;token=a28ca5aa-fe6b-422b-801a-8a675d85eae5" alt=""><figcaption></figcaption></figure>


# Offline license activation

If you are not connected to the Internet while activating your SWING Seascape license, the following procedure needs to be applied in order to activate the license (click on any image for a bigger display):

1\. Open your **Seascape.nsf** database in Notes. When opening the database for the first time you will be prompted to enter your license key. Copy and paste the license key provided to you by SWING Software in the **License Activation** pop-up and hit **OK:**

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FkBCa4BrMWwd9uN2LFS4z%2Foffline-img1.png?alt=media\&token=d581fa55-4373-48a9-9527-48e801b7fa87)

2\. A new **License Activation** pop-up will appear containing a link that you must open in a web browser from a different computer which is connected to the internet. To copy the link, hit **Copy link to clipboard:**

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FvoBVwe7V0ER2RjDGH8jA%2Foffline-img2.png?alt=media\&token=33cb2495-197e-4ae2-ac68-f859a6f8859d)

3\. Paste the link in your browser's address bar, hit Enter, and you will be provided with your activation cod&#x65;**:**

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FONLHkOe6gI9Pg2cYoEsb%2Foffline-img6.png?alt=media\&token=53dc1413-e046-4df7-8e62-56e158cd801b)

4\. Copy and paste the provided activation code in the **License Activation** pop-up and hit **OK**. If a security prompt appears click **Yes** to clear i&#x74;**:**

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FtVzhlIZlBPzbM8gjPKHU%2Foffline-img4.png?alt=media\&token=a1131e95-1088-42dd-a551-af73edc8b74f)

&#x20;5\. Once all of the steps have been completed successfully a message will appear confirming your license activatio&#x6E;**:**

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FuE6c0ebzEflyQw6zvfe3%2Foffline-img5.png?alt=media\&token=a110e07c-5020-4462-ab1e-2878a528a736)

**Note:**

In order to enter a new license or change the existing one, click the **Change license** link in the **about page** of your SWING Seascape databas&#x65;**:**

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FDGurpi18noIVNvCC1RiY%2Foffline-img3.png?alt=media\&token=0b7d2d43-95d3-4b5e-be43-e0a873e4167c)


# Uninstalling

To uninstall Seascape for Notes, simply remove the Seascape database from your Notes data directory.

If you also wish to remove the resources Seascape extracted to your system during the installation process, follow these steps:

1\. Delete the SwPDFC folder from your system (including all sub-folders). The SwPDFC folder is located at `"\Data\SwPDFC\" (typically C:\Program Files\IBM\Lotus\Notes\Data or C:\Lotus\Notes\Data)`.

2\. If you find the swllrend.dll file located in your Lotus Notes or Domino installation folder (typically `C:\Program Files\IBM\Lotus\Notes\ or C:\Lotus\Notes\`), delete it.

3\. Open your notes.ini file (using any text editor), delete the lines listed below, and then save and close the file.

**Important:**

* Please create a backup of **notes.ini** file before making changes.
* Your **notes.ini** file might not contain all entries listed below.
* The notes.ini file is located at "\notes.ini".

List of entries to delete:

a) All entries starting with **SWJ** or **SWJOO**:

`SWJ0`\
`SWJ1`\
`SWJ2`\
`...`\
`SWJOO0`\
`SWJOO1`\
`SWJOO2`\
`...`

b) Entries starting with $Sw:

`$SwPDFJavaDir`\
`$SwPDFJarVer`\
`$SwPDFDoc`\
`$swFileDlgDirectory`\
`$swPDFAutoFileOpen`\
`$SwPDFcLVSO`\
`$SwPDFProgressCount`\
`$swPDFAutoFolderOpen`\
`$SwPDFFileDlg`\
`$SwPDFCreatorServer`\
`$SwPDFCreatorDB`\
`$SwPDFDllVer`\
`$SwPDFDb`\
`$SwPDFServer`\
`$SwPDFForm`\
`$SwPDFViewTitle`\
`$SwPDFContext`

c) Java heap size entries:\
`JavaMaxHeapSize`\
`JavaMinHeapSize`


# Upgrading

## Upgrading Seascape for Notes (NSF)

Below are the instructions to upgrade your Seascape installation to a newer release.

1\. Download the product version you are upgrading to (by using the download link provided by SWING Software) and extract the .nsf file from the ZIP package.

2\. Create a template file using the following steps:

* Rename the extracted .nsf file to **.ntf** file (please make sure to have file name extensions visible in your file explorer).
* Move the .ntf file to your Notes Data folder so it can be easily accessible when replacing the design

3\. Replace the design of the original Seascape database with the database template from step 2 using these steps:

* Right click the Seascape database and select **Application > Replace Design.**

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB-6eLJVi2q9IWsQwD%2F-MlB-ZTvIa-y2UbnQxae%2Fimage.png?alt=media\&token=c9e21e5f-8729-4f2b-b6d2-07db8ee20b00)

* In the **Replace Database Design** window select the Seascape database template **(1)** and hit the **Replace** button (2):

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB-6eLJVi2q9IWsQwD%2F-MlB-iMexWw9UdTbqkgU%2Fimage.png?alt=media\&token=1ecd3384-665a-4388-a8b9-6676f9fa00ef)

4\. After the template has been successfully replaced, open your Seascape database. Seascape will automatically detect that a newer version has been installed and will prompt you to refresh the required resource files saved on disk.

After you confirm the prompt, Seascape will update the resource files on the disk and ask you to restart your Notes client.

After a restart, the upgrade procedure has been completed and you can continue to use the product normally.

5\. Once Seascape is successfully upgraded, we recommend deleting the **.ntf** file (created in step 2) from your Notes Data folder.

{% hint style="info" %}
If you don't wish or need to save your Seascape settings while upgrading, then you can also perform a clean install by simply deleting the old Seascape.nsf file from your system and copying and installing a fresh copy.
{% endhint %}

## Updating Seascape Web Archives

Learn how to update the generated web archives using the Seascape Archive Updater:

{% content-ref url="/pages/-MlAdTTqVgyB0P9o9qr3" %}
[How to update a Seascape archive](/seascape-for-notes/faq/how-to-update-a-seascape-archive)
{% endcontent-ref %}


# System requirements

Microsoft Windows; **IBM Lotus Notes** **R6.5** or higher (IBM Notes, HCL Notes). For best performance, it is recommended that you use IBM Notes 9 or higher.

If you do not have a supported version of Lotus Notes please [contact us ](https://www.swingsoftware.com/form/contact/)to learn about alternative export methods.&#x20;


# Release history

{% hint style="info" %}
For updates in the PDF conversion engine, please refer to the [PDF Converter](https://docs.swingsoftware.com/pdf-converter-for-notes/) Release History
{% endhint %}

## Version 4.4.0 (2026-Aug-07)

* Fixed an issue with embedded views containing umlauts.
* Resolved an issue that prevented Japanese characters from being exported correctly.
* Fixed a problem where document links were not preserved after export.
* Resolved a critical error that occurred when archive names contained apostrophes.
* Fixed a license activation issue on non-UTF-8 JVM locales.
* Resolved errors in the SharePoint Uploader caused by invalid characters in file or folder names.
* Fixed an issue where attachment links did not work correctly when accessed from a web browser.

## Version 4.3.0 (2026-May-19)

* The issue when exporting with "Export inline images as attachments" option enabled has been resolved.

## Version 4.2.0 (2026-Apr-16)

* The issue with metadata when using SharePoint Flat upload is now fixed.
* Issue with empty views in web export, has been resolved.

## Version 4.1.1 (2026-Mar-20)

* The issue with activating the trial license has been resolved.
* It is now not possible to start a new export while the external JVM is running.
* The issue causing blank pages in generated PDF files has been fixed.

## Version 4.0.14 (2026-Mar-05)

* Uploading to SharePoint now correctly maps and populates existing columns.
* The problem with embedded views during export when PDF Conversion was disabled has now been fixed.
* The error that occurred when entering a password in the Refresh User Credentials agent has been resolved.
* It is no longer possible to start an export without selecting a destination folder.
* Issues with uploading data from documents that do not contain form fields have been resolved.
* The error "ERROR java.lang.ArrayIndexOutOfBoundsException: Index 176 out of bounds for length 176" has been fixed.
* The error "NotesException: A required argument has not been provided" has been resolved.
* The issue causing embedded views to display excess documents has been addressed.

## Version 3.36 (2025-Nov-25)

* When uploading to SharePoint, a warning will now show for each field that cannot be uploaded.
* .pzm OLE objects are now exported as .tiff attachments.
* The error *ERROR javax.xml.stream.XMLStreamException*, which occurs when running an Extract to Disk archive with enabled Embedded View metadata file in settings, has now be fixed.
* Issues with the document links not working when uploading to a SharePoint sub-site, have now been resolved.

## Version 3.35 (2025-Oct-29)

* Error message "Extendable File object: invalid read count", has been resolved.
* Added support for Leelawadee UI font.
* Error message "java.lang.NullPointerException: Cannot read the array length because "buf" is null" that occurs when inline images are enabled has been fixed.

## Version 3.34 (2025-Oct-16)

* A newly enhanced SharePoint Uploader is now included, offering a refreshed UI and an improved archive structure in SharePoint.
* The progress bar no longer stalls at 33% during SharePoint uploads.
* RFT field mappings are now being handled correctly.
* The error Cannot invoke "com.swingsoftware.notes.NotesDocument.getFormName()" because "parentDoc" is null, has been resolved.

## Version 3.33 (2025-Sep-05)

* The error "java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0" which occurs when exporting documents without a form, has been resolved.
* The "java.lang.ArrayIndexOutOfBoundsException: Index -138 out of bounds for length 10" error, has been fixed.

## Version 3.32 (2025-Aug-25)

* Minor adjustments made.

## Version 3.31 (2025-Jul-03)

* The issue with the attachment in the email header has been fixed.
* The problem with broken document links in SharePoint due to incorrect encoding of national characters has been fixed.
* The issue with the PDF creation breaking because of a document link to a non existing database has been resolved.
* Correctly managing errors if they occur when creating document links.
* Issue with blank screen appearing when sorting columns is resovled.
* Web archives search result count issue, has been resolved.
* The error "java.lang.ArrayIndexOutOfBoundsException" has been resolved.
* Issue with exporting documents without a form, is now resolved.
* The ability to accept the password by clicking "Enter" is now available.
* Issues when trying to export a database while offline, have been resolved.

## Version 3.30 (2025-Apr-15)

* The issue with the attachment in the email header has been fixed.
* The problem with broken document links in SharePoint due to incorrect encoding of national characters has been fixed.
* The issue with the PDF creation breaking because of a document link to a non existing database has been resolved.

## Version 3.29 (2025-Feb-25)

* The issue with additional columns being unexpectedly added when running an export in R8.5 has been resolved.&#x20;
* The thousands separator is now displayed correctly in the exported views.&#x20;

## Version 3.28 (2025-Feb-19)

* The issue with the thousands separator not visible in exported view, has been resolved.
* The issue with the outline entries being misaligned, has been fixed.
* The problem with Notes 7 Java not being able to verify a signature has been fixed.

## Version 3.27 (2025-Jan-31)

* The issue with the error "Activation error: Signature validation error" occurring has been fixed.

## Version 3.26 (2025-Jan-30)

* The issue with paragraph indentation inside the generated PDF files, has been resolved.
* The error "Object.getClass()" because "dataValue" is null, has been fixed.
* Issues with the documents being exported using a different alphabet has been resolved.
* Font table modifications in settings have now been enabled.

## Version 3.25 (2024-Dec-19)

* The issue with the folder structure being flat, when exporting to SharePoint or Extract to disk archives and selecting view with parent/child structure, has been fixed.
* The error "ERROR \<file\_path>\<file\_naming>-att does not exist", has been resolved.

## Version 3.24 (2024-Nov-20)

* Messages in the log that the attachments are corrupted, even if there not, has been fixed.&#x20;
* The issue with the Nullpointer exception occurring when exporting email documents, has been resolved.
* Problem with the attachments for documents using an alternate form, has been fixed.
* The issue with documents being exported using an empty form, has been resolved.
* Issue where the first column is missing from the view in the web archive, has been fixed.

## Version 3.23 (2024-Oct-31)

* The issue with attachments not being visible in the generated PDF file has been resolved.&#x20;
* A new and improved Sharepoint Uploder had been added. It's now built on the new .NET 6 framework, which has allowed us to use the new Sharepoint PnP library. Improvement have also been made with the functionality of document links in Sharepoint.

## Version 3.22 (2024-Oct-29)

* The issue with the generated PDF file not been moved into the destination folder, because of an invalid PDF file naming has been resolved.
* Issue with the category not opening properly in the web archive and receiving the error message "Failed to 'querySelectorAll' on 'Document'" view has been fixed.
* The issue with the attachments not opening, when the attachments have no extension has been resolved.

## Version 3.21 (2024-Sep-17)

* The issues with the date as a category not been formatted, has been resolved.
* Issue with the category columns being displaced one column to the right, has been resolved.
* When re-exporting documents that have MIME fields, cleaning attachment folders will be skipped if no attachment folder exists, that way no errors will occur during the re-export.

## Version 3.20 (2024-Aug-30)

* The issues with the date/time format showing incorrectly has been issued. A new setting has been added which allows choosing the date/time format.
* An option has been added to include data from embedded views into metadata. An additional xml file will be created inside the archive containing the data.

## Version 3.19 (2024-Aug-09)

* The issues with the error "java.lang.OutOfMemoryError: Java heap space", has been resolved.
* The error "FileNotFoundException" that occurs when using the Extract to Disk option with the setting to disable PDF conversion has been fixed.
* The problem with the error ""swPdfDoc" is null" has been resolved.
* The problem with field weight being determined incorrectly when uploading data into SharePoint using the automatic option, has been resolved.
* Attachment name is where ".1" is added to each attachment name has been resolved.
* Issue with no total/average for categories in the web archive has been fixed.

## Version 3.18 (2024-June-04)

* The problem with the attachment folders being created and named according to the UNID of the document has been fixed.
* The problem that appeared with categories named with two or more points at the end has been fixed.
* The problem that occurred when all documents were selected for export and the PDF conversion was turned off, leading to the error "Java.io.FileNotFoundException" during the extract to disk option, has been resolved.

## Version 3.17 (2024-May-27)

* The Notes JVM export cancellation issue has been fixed.
* The problem that was causing an exception to appear when the Notes form field was left empty has been fixed.
* Fresh install will now set External JVM as the default.
* WARNING "Outline 'Notice - Border Two' does not exist", that occurs when selecting Mail Outline and Calendar Outline for two databases in a single export has been resolved.
* The problem that was causing the export to create two folders when the mail outline option was chosen has been fixed.
* The Exception Cannot invoke "java.util.List.size()" because "children" is null, is resolved.
* A new option has been added to do a complete reinstall from the Actions menu.
* The issue with the exception Exception in thread "Thread-5" has been fixed.

## Version 3.16 (2024-Apr-24)

* The issue with view form formulas not being evaluated has been resolved.
* Issue with the custom metadata being displayed incorrectly, has been resolved.
* Notes error: The full text index needs to be rebuilt, has been resolved.
* The issues with the error message Cannot invoke "java.lang.Integer.intValue()", has been resolved.
* Issue caused by "java.lang.NullPointerException", has been resolved.
* The issue while fetching the databases from the server, using the advanced selection dialog has been resolved.
* Issue when exporting multiple outlines has been resolved.
* The issue with the error message "java.lang.StringIndexOutOfBoundsException: begin 270, end 254, length 254 (Attachments path too long)", has been resolved.
* Issue with the export log not being created when using the log level 3 option, has been resolved.
* Meaningful information has now been added to all logging levels.
* Issue with the twisties not showing up in the web archive, has now been resolved.
* Issue with the DateTime time zones has been resolved.
* The issue with the error message "Index 3 out of bounds for length 3" has been resolved.
* The issue with the Notes error: File object is truncated - file may have been damaged, has been resolved.
* Issues with creating a custom metadata using the @Date function, has been resolved.

## Version 3.15 (2024-Mar-19)

* The issue with the error "Java.lang.IllegalArgumentException: The number of columns in PdfPTable constructor must be greater than zero", has now been resolved.
* Issue with the metadata not being uploaded to SharePoint has been resolved.
* An error received when exporting documents using a generic Notes form has been resolved.
* The Invalid date specification error has been resolved.
* Notes 14 release changed paths within the JVM folder, the necessary changes have been made.
* NotesException: File xxx.log not found error, has been resolved.
* Databases can now be exported on R6 with the external JVM.
* The error messages displayed when opening an empty view have been resolved.

## Version 3.14 (2024-Mar-06)

* The issue with the error Cannot invoke "com.swingsoftware.ssc.ViewColumn.getCellSpan()" because "sscTitleCol" is null appearing in the console has been resolved.
* The issue with the metadata not being uploaded, during the second upload to SharePoint when using the “New Upload” button, has been resolved.
* Every document which has no form defined and no default form, will be exported with an generic form.
* Issue with error "Can't load the XML resource" has been resolved.
* Error "java.io.IOException: Stream closed" has been resolved.

## Version 3.13 (2024-Feb-29)

* Notes error: Insufficient memory, has been resolved.
* Issues with the export failing after running out of memory, has been resolved.
* Notes Exception: Out of memory“ error, has been resolved.
* Index out of range error when uploading to SharePoint, has been resolved.
* Upload to SharePoint issues when site URL is ending with "/", has been resolved.
* Issues with uploaded files to SharePoint, when using folder formula and custom naming formula, has been resolved.
* Issues with the progress dialog behaving strangely has been resolved.
* Issues with the export log, concerning the log level have been resolved.

## Version 3.12 (2024-Feb-20)

* Enabled multiple database selection when uploading data to SharePoint
* New feature added to automatically create a SharePoint document library for each uploaded archive.
* New feature added to automatically create views in SharePoint document library.

## Version 3.11 (2024-Feb-15)

* Issue with the saving the wrong java.console file has been resolved.
* Issue with the special characters causing the document links and attachments to not work in Sharepoint, has been resolved.
* Issue with merging and duplicating log files has been resolved.
* Removed the incorrect "archive limited to 10 documents and 100 entries per level" message, from the log file.
* The Cannot invoke "java.awt.image.BufferedImage.flush()" because "this.image" is null issue has been resolved.
* Two new settings have been added; A setting to save Notes document metadata within the generated PDF files. And a setting to disable the printing of Notes attachment icons in the generated PDF files.
* Additional feature has been added in settings, to put a limit on the document size which will be exported. (**The default is set to 100 MB document size limit**)

## Version 3.10 (2024-Jan-22)

* Issue with the invalid XML character (Unicode: 0xde71), is now resolved
* Issue with the sub tab has been resolved.
* Issue with the exported blank PDF files has been resolved.
* Issue with the export when running on deleted documents has now been resolved.
* Error "Java.lang.NullPointerException" has been resolved.
* The issue with the export crashing and error "java.lang.OutOfMemoryError: Java heap space" being reported has been resolved.
* Error "com.swingsoftware.notes.NotesDocument.getViewEntry()" because "this.currentDocument" is null has been resolved.
* A prompt has been added to notify users of changes being saved in General settings.

## Version 3.09 (2024-Jan-02)

* The issue with zip attachments not downloading when they are exported as .7z attachments, has been resolved.
* Issue with the character reference "\&#11" has been resolved.
* Issue with the dialog incorrectly showing message “Export successfully completed”, has been resolved.
* Issue with Notes error message ".nsf has not been opened yet" appearing in the log file, has been resolved.
* The issue with the error message Cannot invoke "com.swsoftware.pdfc.core.attachments.BinaryAttachment.isConvertedToPDF()" because "attachment" is null and export crashing has been resolved.
* Issue with the outline not being exported properly, has been resolved.
* Issue with the outline being mixed and not being correctly sorted, has been resolved.

## Version 3.08 (2023-Dec-14)

* Issue with the Sharepoint uploader showing incorrect progress percentage has been resolved.
* Issue with the agent "Start Export Background" still running after the export has been completed, is now resolved.
* Issue with the OLE objects being embedded instead of linked and saved in the attachments folder has been resolved.
* Issue with unnecessary folders being created when a category in a view has the character "/" has been resolved.
* The issue with the NAMESPACE\_ERR error has been resolved.
* The error "Cannot convert field - unsupported datatype" has been resolved.
* Issue with the batch export failing to export all databases has been resolved.
* The issue with the attachment links inside the generated PDF file pointing to an incorrect document extension when choosing the options "Save in the Attachments folder > Convert and save as PDF", has been resolved.
* The error Cannot invoke "java.lang.Integer.intValue()" because the return value of "java.util.Map.get(Object)" is null has been resolved.

## Version 3.07 (2023-Nov-28)

* Issue with the Notes exception "Object has been removed or recycled" has been resolved.
* Issue in the web archive with the date in the category not showing correctly, has been resolved.
* Issue with the umlauts not showing correctly in the web archive catalog has been resolved.
* Error "java.lang.OutOfMemoryError: Java heap space" that occurred when exporting using the Extract to disk option has been resolved.
* Issue with export crashing has been resolved.

## Version 3.06 (2023-Nov-22)

* Issue with Word Ole objects not being exported has been resolved.
* The error "Object has been removed or recycled" has been resolved.
* Issue with the export crashing and getting multiple errors (Notes error: Insufficient memory, Notes error: Formula Error) has been resolved.
* Issue with the NAMESPACE\_ERR error has been resolved.

## Version 3.05 (2023-Nov-13)

* Prompt has been removed when destination folder is Flex root folder.
* Date format has been corrected.

## Version 3.04 (2023-Nov-02)

* File duplication has been optimized in the Extract to Disk and SharePoint export methods.&#x20;
* The redundant commas have been removed from the outline category.
* The missing view totals have been added to the view-outline.&#x20;

## Version 3.03 (2023-Oct-17)

* Issue with content missing when column sorting is used, has been resolved.
* Issues with inline images has been resolved.
* Issue with the missing viewer version after the export has been resolved.
* Issue with exporting computed numeric fields has been resolved.
* Issue with the wrong status in the export log has bee resolved.
* Error messages that occur when exporting all views from “Individual views” tab and when selecting outline, have been resolved.

## Version 3.02 (2023-Sep-27)

* Issue with folders missing in the web archive has been resolved.
* Issue with ClosedByInterruptException has been resolved.
* Warning message when using the full trial has been updated.
* Issue with outline having missing folder and views as well as not being sorted properly has been resolved.
* Issue with NullPointerException has been resolved.
* Issue with another export already in progress has been resolved.

## Version 3.01 (2023-Sep-22)

* Issue with folders not being visible in the view list in the web archive has been resolved.
* Issue with java.lang.IllegalStateException showing in the log at the end of the export has been resolved.
* Default folder formulas have been added.
* Issue with XML files not being created when using custom naming formula has been resolved.

## Version 2.78 (2023-Sep-06)

* Search issue in the web archive has been resolved.

## Version 2.77 (2023-Jun-02)

* Issue with unsupported datatype has been resolved.

## Version 2.76 (2023-May-17)

* Issue with merged cells in table in the Notes document has been resolved.
* Issue with unzipping the database in Java and getting a Access is denied error, has been resolved.
* Issues with the export crashing on certain documents have been resolved.

## Version 2.75 (2023-May-02)

* Issue with extracting metadata for a field with RFC822 type has been resolved.
* Issue with returning to the start menu when export is cancelled has been resolved.

## Version 2.74 (2023-Apr-20)

* The System.NullReferenceException when uploading to a SharePoint list has been resolved.
* ArrayIndexOutOfBound exception has been resolved.
* Issue with doclinks for attachments with same name and size has been resolved.
* Additional By template and file path tab added when selecting databases.
* Manual license activation option to Actions has been added.

## Version 2.73 (2023-Mar-29)

* The System.NullReferenceException when uploading to a SharePoint list has been resolved.
* The "No PDF" error has been resolved.
* The "New PDF settings" which throws an error before opening the form, has been resolved.
* Issue with the document form is not defined and there is no default form in the database error has been resolved.

## Version 2.72 (2023-Feb-22)

* Issue with attachments that have same name has been resolved.
* Additional attachment option for generating only the attachments links has been added.

## Version 2.71 (2022-Dec-08)

* Invalid file size exception has been resolved.
* Issue with the embedded view header and columns not being aligned has been resolved.
* Action created to convert archive from aspx to html.
* Ole attachments not being able to open, has been resolved.
* File names that begin with a space(s) are now trimmed (when using SharePoint export method).
* Array index out of range exception has been resolved.

## Version 2.70 (2022-Nov-03)

* The System.NullReferenceException error found when uploading to a SharePoint list has been resolved.
* Error when fetching database views has been resolved.
* Issue with duplicate response documents has been resolved.
* Issues with the response documents not showing after changing view and coming back have been resolved.
* The "not found as file or resource" error caused by Chinese characters has been resolved.
* Issues with RTF fields not properly being displayed in Sharepoint properties have been resolved.

## Version 2.69 (2022-Sep-22)

* The System.NullReferenceException error found when uploading to a SharePoint list has been resolved.

## Version 2.68 (2022-Sep-15)

* Issue with documents count mismatch have been resolved.
* Issue with the attachments not working properly have been resolved.
* Issues with the document list not being refreshed upon category change has been resolved.

## Version 2.67 (2022-Aug-17)

* The System.NullReferenceException error found when uploading to a SharePoint list has been resolved.
* SharePoint "Return to start" link issue has been resolved.
* Embedded OLE object issue resolved.
* Alignment issues resolved when printing PDF.
* Issues with the document count in the export log have been resolved.
* Two new columns added in the database analysis report.

## Version 2.66 (2022-May-19)

* The System.NullReferenceException error found when uploading to a SharePoint list has been resolved.
* Additional reporting has been added to the database analyzer.
* Multivalue table issues have been resolved.

## Version 2.65 (2022-Apr-26)

* The System.NullReferenceException error found when uploading to a SharePoint list has been resolved.
* The overflow error found during export on some documents has been resolved.
* An issue with a the embedded view table being broken in PDF has been resolved.
* The XML metadata file creation is now skipped if the XML already exists.
* An issue with Word doc OLE attachment being extracted as TIFF file has been resolved.

## Version 2.64 (2022-Mar-25)

* An issue with the Metadata Sidebar closing on its own has been resolved.
* The System.NullReferenceException error received when uploading files to a SharePoint list has been resolved.
* An issue with searching through categories in the Seascape Web Viewer has been resolved.
* An issue with missing sub-category structure has been resolved.
* The Nullpointer Exception received when converting a document/corrupted attachment has been resolved.
* The java.lang.StringIndexOutOfBoundsException error received when attempting to export attachments that start with "." has been resolved.

## Version 2.63 (2022-Feb-21)

* Attachment date created and date modified information is now saved in the XML and JSON metadata files.&#x20;
* An issue with category search has been resolved.&#x20;
* The System.NullReferenceException error received when uploading to a SharePoint list has been resolved.
* The web archive metadata sidebar now opens or closes automatically based on the state which is saved in browser's local storage from the previous session.&#x20;

## Version 2.62 (2022-Jan-19)

* A new setting has been added for turning off Form Formula evaluation.
* An issue with the web archives no longer working when hosted in Microsoft SharePoint has been resolved.&#x20;

## Version 2.61 (2021-Dec-14)

* The System.NullReferenceException found when uploading to a SharePoint list has been resolved.&#x20;

## Version 2.60 (2021-Nov-25)

* An issue with exporting stored images has been resolved.
* Document search is now set as the default search in Seascape Flex.

## Version 2.59 (2021-Nov-11)

* An issue with missing view column in the web archive has been resolved.
* An issue with hidden attachment icons has been resolved.

## Version 2.58 (2021-Nov-02)

* JS files are no longer generated if the metadata export is disabled.
* A fidelity issue with single category embedded views has been resolved.
* An issue with the SharePoint uploader crashing during field mapping has been resolved.

## Version 2.57 (2021-Oct-19)

* An issue with PDF attachment links not linking to the correct attachments in the web archive has been resolved.
* Links to external attachments have been disabled in the Extract to Disk archive.

## Version 2.56 (2021-Oct-06)

* New feature: The database analysis tool now provides clients with the ability to generate a report listing all of the databases found on a Domino server including the important information for each database, such as the database size, number of documents, attachments, etc.
* The SharePoint uploader has been updated for better upload performances.
* An issue with web archive infinite scroll has been resolved.
* An issue where a document with an embedded view stalls the export process has been resolved.
* An issue with the embedded view columns being shifted in the PDF has been resolved.

## Version 2.55 (2021-Sep-22)

* Attachment links now work correctly when the file name is too long.
* Reverting to high-level renderer no longer causes documents to be exported with Memo form.
* The Seascape Updater now comes with separate functions for the archive catalog updates and export updates.

## Version 2.54 (2021-Sep-17)

* Unfinished exports will now resume automatically when the application is re-opened in case of a Notes crash.
* The categories outline is now exported correctly when a document filter is applied.
* An issue with long file paths for XML files has been fixed.
* A Type Mismatch error that occurred when clicking on pdfsettings in Settings has been fixed.

## Version 2.53 (2021-Sep-08)

* If no PDF file was created for specific archive documents then clicking on the document will only show the metadata sidebar.
* An issue with selecting Outlines has been fixed.
* If a user tries to open a 100+ document in the trial version of the web archive a warning message will be shown.
* An issue with missing dolinks.xml file has been fixed.

## Version 2.52 (2021-Aug-10)

* Attachment icons in PDF are now linked to the files in the Attachments subfolder of the web archive.
* An issue with users not being able to switch to another view while viewing search results has been fixed.

## Version 2.51 (2021-Jul-09)

* Unfinished exports can now be resumed on application open in case of a Lotus Notes crash.
* An error that appeared when selecting the PDF Settings has been resolved.
* When all the views are selected in the view selection the selection link now changes to "Deselect all".

## Version 2.50 (2021-Jun-14)

* The database selection dialog now comes with improved options for selecting mailfile outlines.
* An issue with missing bullet labels with Chinese characters has been resolved.
* An issue with the SharePoint uploader crashing while uploading files to SharePoint 2010 has been resolved.
* The date are now properly set when there is no time for UTC format.

Version 2.49 (2021-Apr-20)

* The classic database selection dialog now allows for more than 18 databases to be selected.
* It's now possible to select "Export default view only" when multiple databases are selected.
* A new column called "ND.Parent" of type lookup is now created during SharePoint uploads containing a reference to the parent document.

## Version 2.48 (2021-Apr-15)

* An issue with uploading files containing the hash character to MS SharePoint has been resolved.
* The "Export default view only" option can now be selected when exporting multiple databases.
* A few "java.lang" errors have been resolved.

## Version 2.47 (2021-Mar-24)

* An issue with selecting database for export via database templates has been resolved.
* An issue with mail outline selection has been resolved.
* A "Path not found" error found on batch mail export has been resolved.
* An "XML exception on illegal character" error has been resolved.

## Version 2.46 (2021-Feb-23)

* A new feature has been added which enables the optional export of documents that are not shown in any document view.
* The "Export default view only" option can now be selected normally when multiple databases are selected.
* An issue with outline exports creating additional views has been resolved.
* An issue with SharePoint uploader reporting an error when uploading files with "#" has been resolved.

## Version 2.45 (2021-Jan-26)

* The SharePoint upload window now shows the correct library URL.
* Seascape now supports the creation of PDF/A-2U files.
* Seascape now supports import of HTML content into SharePoint fields.
* An issue with generating file paths from document views that contain the slash character "/" has been resolved.

## Version 2.44 (2021-Jan-05)

* Notes crash issue when running exports on R8 or earlier has been resolved .

## Version 2.43 (2020-Dec-23)

* Offline license activations are now cached locally to avoid showing activation prompts unnecessarily.

## Version 2.42 (2020-Nov-28)

* Field too large error (32K) has been fixed.
* A few column sorting issues in the web archive have been resolved.
* SharePoint export settings have been updated by removing a few unused settings.

## Version 2.41 (2020-Nov-02)

* An error that occurred when archiving a database with a Japanese title has been resolved.
* The DB selection dialog no longer splits the database name when there is a comma in the name.
* The license usage information on the About now includes the date of last refresh.
* The "Type mismatch" error found on Notes R7 client has been resolved.

## Version 2.40 (2020-Oct-21)

* Attachments with Chinese characters are now extracted normally.
* A Notes crash issue has been resolved.
* The ability to switch between low level and high-level renderer when attachments have Chinese characters has been added.
* Attachment folders are now saved with the same names as the PDF files when using the "Extract to disk" option.
* An issue with metadata not being set when the Title column is named differently has been resolved.
* The main PDF files are now attached along with the other attachments in the in SharePoint List
* Empty categories are no longer visible in the Web viewer.
* An issue with older versions of Notes crashing has been resolved.
* An issue with Seascape Updater using an incorrect archive path if root folder is a disk drive has been resolved.

## Version 2.39 (2020-Sep-11)

* An issue with missing and deformed content in PDF files has been resolved.
* Outline selection is now enabled when multiple databases are based on the same template.
* When exporting via outlines, the outlines labels are now used instead of the view names.
* The Notes outline structure is now replicated fully in the web archive, including "group" entries
* The System Monospaced font has been replaced with a scalable font.
* An issue with the "detachNotesAttachment error - must supply bulk decryption key" error has been resolved.
* An issue with missing or incomplete content has been resolved.
* An issue with invalid characters appearing the XML files used for SharePoint uploads has been resolved.
* An issue where an embedded view is torn apart in the PDF output has been resolved.

Version 2.38 (2020-Aug-17)

* Users can now select up to 100 databases to export in one go.
* Quotations marks are now stripped from the file names.
* An issue with data formats in the web archives has been resolved.
* An issue with the view creation breaking on document rendering error has been resolved.

## Version 2.37 (2020-Aug-10)

* A new agent has been added to automatically sign the Seascape database with the current user ID during installation.
* An issue with empty view columns in web archive has been resolved.
* An issue with stack overflow has been resolved.

## Version 2.36 (2020-Jul-27)

* An issue with invalid JSON files being generated has been resolved.
* The web archive now works on HTTP also.

## Version 2.35 (2020-Jul-10)

* An error caused when creating a database shortcut which contains illegal file name characters has been resolved.
* Attachments upload to SharePoint now works correctly when the PDF files are named using a custom naming formula.
* PDF files are now generated correctly with the Extract to Disk option when the database is on local.

## Version 2.34 (2020-Jun-23)

* The getMetadata function now works correctly when the web archive is deployed from a server.
* The ND.AttachedTo UNID property is now added for each attachment in SharePoint.
* An issue with broken string on export in view entries has been fixed.
* The AnonymousBlockBox incompatible with org.xhtmlrenderer.newtable.TableRowBox error has been resolved.
* The Response column content is now properly aligned.
* Chinese characters in attachment names are no longer exported as question marks inside the view-entries.js files.
* The folder names in Export to disk are now trimmed.

## Version 2.33 (2020-May-27)

* The Database Clear action now clears the view selection too.
* The 'db' subfolder is now exported to the correct location in structured export.
* An error found while creating JSON for Notes metadata has been fixed.
* The three primary export methods have been renamed.
* A new option has been added for exporting mail databases to disk.
* The ND.AttachedTo UNID metadata is now generated for each attachment uploaded to SharePoint.

## Version 2.32 (2020-May-11)

* An issue with connecting to SharePoint On-Premise has been resolved.
* A FileNotFoundException error when exporting folder names ending with dots has been resolved.
* Completed exports now show a link to the Export Log.

## Version 2.31 (2020-May-07)

* The SharePoint upload progress bar is now displayed based on the actual number of files in the folder.
* The ND.Attachments property is no longer imported to SharePoint lists.
* If the Title list item is not defined in SharePoint then the file name will be used instead.
* The database selection dialog has been updated with several new improvements.
* Attachments are no longer duplicated when exporting documents from view based on a form formula.
* Metadata is now applied correctly to documents created with a View Form Formula.
* An issue with Notes crashing during export has been fixed.
* The Plain Archive now saves the view structures.
* Settings for multiple views export in the Plain Archive have been moved to the Export Settings tab.
* The ND.UNID, ND.Parent UNID ($Ref), ND.Created Date, and Form properties have been added to indexed columns in SharePoint.
* The documents and view entry counters in the application now show the correct values.
* OLE objects are now exported correctly.

## Version 2.30 (2020-Apr-06)

* New settings have been added for selecting views in the plain archive.
* Sharepoint uploader now correctly uploads files that are not named using the Notes UNID.
* SharePoint uploader now manages the document upload speed automatically based on SharePoint's throttling policy.
* An issue with the plain archiving showing an incorrect number of exported documents has been fixed.

## Version 2.29 (2020-Mar-23)

* The Full Archive created from a mailfile's outline now includes all folders.
* Non hierarchical view with response column not shows documents correctly.
* Plain archives can now be created by selecting specific document views.
* The Full Archive is no longer broken because of invalid views-list.js

## Version 2.28 (2020-Feb-07)

* A new option for exporting mail databases as plain archives has been added.
* A new option has been added to disable the XML metadata file creation in the plain archive.
* Rich text fields can now be exported as metadata in the plain (SharePoint) archive.
* An IE11 compatibility issue has been resolved.
* Documents with same file name as already exported documents will be skipped in plain archive export.
* Line breaks are now preserved when uploading rich text metadata to the SharePoint.
* The "User xx cannot open database" error on refresh database list has been fixed.
* The Web viewer updater no longer throws an error when reading zip file.
* A user defined error when selecting database in the new alternate form setting has been fixed.
* The "Variable not set error" has been resolved.
* An issue with LocalStorage when 3rd party cookies are disabled has been fixed.
* An overflow error when exporting with plain archive has been fixed.

## Version 2.27 (2020-Jan-15)

* The "32k error" which appeared in some cases when fetching database views has been fixed.
* The Notes metadata is now displayed correctly in the full archive hosted in a MS SharePoint library.

## Version 2.26 (2019-Dec-20)

* The modern authentication method is now supported in SharePoint
* A quick tour feature is enabled in the full archives to help users find their way around the archive easily
* RTF text field can now be mapped to SharePoint fields
* An issue with the wrong date format has been fixed
* A "32k" error that occurs when too many workstations are registered has been fixed
* An issue with the PDF files not opening with double-click has been fixed
* The error handling in cases when the database list from server can't be fetched has been improved
* Very long attachments names in the Full Archive are now automatically shortened

## Version 2.25 (2019-Nov-07)

* The plain archive attachment subfolders are now saved with the same names as the parent PDF files.
* An issue with filter selection showing "All folders in views in selected database" when only a single view is selected has been fixed.
* An issue with an Invalid Formula error has been resolved.

## Version 2.24 (2019-Nov-04)

* The mail outline is now the default outline when exporting mailboxes.

## Version 2.23 (2019-Sep-27)

* New options have been added for processing embedded views.
* New options have been added for OLE attachment extraction.
* An overflow error which occurred on full archive export has been fixed.
* As issue where the progress bar freezes with an "input past end of file" error has been fixed.

## Version 2.22 (2019-Sep-06)

* An issue with SharePoint upload connection has been resolved.
* A few UI issues found when the Full Archive is viewed in Microsoft Edge have been resolved.

## Version 2.21 (2019-Aug-07)

* The "Field is too large (32K)" or "View's column & selection formulas are too large" errors have been fixed.

## Version 2.20 (2019-Jul-29)

* An OEM version of the product is now available
* JSON files are now loaded using JavaScript without a web server

## Version 2.19 (2019-Jul-12)

* A category view search issue which occurs when there are no results in the search has been fixed
* Searching in a view category with multiple levels now works correctly
* An issue with the SharePoint field mapping has been fixed
* Subcategories are now correctly recognized

## Version 2.18 (2019-Jun-21)

* Fixed a stability issue

## Version 2.17 (2019-Jun-05)

* Fixed an issue with the license activation

## Version 2.16 (2019-May-31)

* Send multiple replicas for activation when performing batch exports
* Improved the license activation procedure
* An option to send email when export is completed has been added
* The current license usage is now shown after successful activation
* An issue with empty date fields showing the value of "00:00:00" has been fixed
* An issue with column duplication in categorized views has been fixed

## Version 2.15 (2019-Apr-15)

* The mail database outline is now recreated in Full Archive
* UI formulas are now evaluated during export
* An issue with plain archiving getting stuck on a specific document has been resolved
* A missing icon in the web viewer has been restored
* The custom-root.css file is now exported to root css folder and custom-db.css files to css folders of each database
* The metadata is now sorted alphabetically
* An issue where nothing happens when fetching views of encrypted databases has been resolved
* When modifying a document selection the hidden views will not be unselected
* Long attachment names will be trimmed if the path is too long
* The "No RESUME" error on fetching views from a database with private views has been resolved
* Column sorting should is now case insensitive
* Full Archives can now be set up with custom colors and logo in the root css file
* The log now shows the information on alternate forms if they are used during the export
* Created and modified time is now displayed in 24h or AM/PM format

## Version 2.14 (2019-Mar-13)

* The last used destination folder will now be set as default until changed
* Date only fields with "0Z" suffix are now correctly transferred to SharePoint
* An issue with big decimal numbers rounding has been fixed
* The Plain Archive export now allows user to choose if the database root folder should be created
* Support is added for text-only representation of RTF in metadata
* "The server does not allow messages larger than 2097152 bytes" error in SharePoint uploader has been resolved
* An issue with invalid time range and date time range values in JSON has been fixed
* Mime mail "Received" property is now handled correctly when generating metadata
* Progress bar during metadata processing now works for the plain archive too
* Text fields over 255 characters are now trimmed

## Version 2.13 (2019-Feb-25)

* Comma separated decimal numbers are now transferred correctly
* SharePoint field type change is now saved correctly

## Version 2.12 (2019-Jan-19)

* The metadata formula is now validated correctly.

## Version 2.11 (2018-Dec-19)

* An issue with date-only fields getting a "0Z" suffix in the XML metadata has been resolved.
* "Object variable not set" error has been resolved.

## Version 2.10 (2018-Dec-10)

* The SharePoint library tree is now loaded faster using dynamic loading
* The SharePoint connections are now listed alphabetically
* Refreshing a view list now also automatically refreshes the outlines list
* An option has been added to refresh the outline list
* An issues with converting databases with trailing space in the title has been resolved
* Fetch views now works correctly on specific databases
* An option to disable rendering of doclinks has been added
* An issue with matadata containing invalid characters has been resolved
* A warning message will now be shown if the version of Notes client used is less then R8
* An issue with no documents being displayed in a view has been resolved

## Version 2.09 (2018-Nov-26)

* An issue with specific documents not being displayed in the web view has been resolved

## Version 2.08 (2018-Nov-21)

* Existing JSON files are no longer overwritten with new exports
* The Full Archive can now be hosted from a SharePoint library

## Version 2.07 (2018-Nov-12)

* Response doc titles are no longer duplicated
* View entries columns are now displayed correctly (not empty)
* Added an alternative way to select databases when batch select doesn't work
* The "Add a database" button has been removed from the batch select dialog

## Version 2.06 (2018-Nov-06)

* The views are now presented in the same order as in the database outline
* The export log now includes information on document counts
* Seascape export now works correctly when there is a comma in database name
* An issue with a view now being exported correctly has been resolved
* "Created By" field is now correctly transferred to SharePoint
* The license key is now shown in the About dialog
* Fixed an issue where the error log shows just "Document conversion failed, no additional data available"
* Existing PDF documents will now be overwritten when the export to the same folder is repeated
* Support has been added for Delegated / Claims

## Version 2.05 (2018-Oct-18)

* Invalid characters are now removed when file names are created using a formula
* The SharePoint uploader now provides the ability to upload attachments and link to corresponding documents
* The parent document (PDF) can now be added to a generic SharePoint list as an attachment
* The Full and Plain archives now provide the ability to define custom metadata
* Documents already uploaded to SharePoint will now be skipped if a new upload is started with the same documents
* If a Form Formula is defined in a view, multiple document instances will be created based on the formula
* A new option has been added which enables the export of only the default view in a each selected database
* Users can now switch to the default Notes dialog when selecting a single database if needed
* The default PDF settings are now saved correctly after being edited
* Documents to be exported can now be selected using a Notes formula
* The Full Archive now opens the default database view, same as in the original Notes application

## Version 2.04 (2018-Sep-19)

* Documents are now listed in a view correctly when a string value is shown in the "display as icon" column
* When attachments are extracted to disk the created and modified dates will be saved unchanged
* Upload metadata and attachments to SharePoint lists when there is no main document

## Version 2.03 (2018-Aug-07)

* File attachment options
* Hash license key for display
* Add SharePoint field name validation (typed field names can not be blank or duplicates)
* Before starting conversion check if PDF Converter is already running
* Manual database activation fix
* PDF Settings dialog improvement
* PDF/A fixed

## Version 2.02 (2018-Jul-30)

* Restricting export to one server still allows local databases to be exported
* Document export based on date does not work
* Time zone in exported JSON
* PDF Setting dialog improvement
* Version number updated in main.js file
* SharePoint upload UI in the Seascape Notes application
* SharePoint Uploader WPF UI design
* Exported views and documents count in Seascape Web Viewer and Updater

## Version 2.01 (2018-Jul-23)

* Fix: Overflow error on large databases (>2GB)

## Version 2.00 (2018-Jul-20)

* New: Plain Export (PDF+XML)
* New: SharePoint Uploader
* New: Full Export - Database Catalog
* New: Export of multiple databases in a single batch
* New: Updater for Web Viewer
* New: Other improvements

## Version 1.61 (2018-Feb-07)

* Fix: Attachments with long files names are not exported
* Fix: View indentified as hidden if name starts with underscore
* Fix: Error when fetching views: Could not create field %1
* Fix: Object variable not set error

## Version 1.60 (2017-Dec-10)

* Fix: User can export data from any accessible server

## Version 1.59 (2017-Nov-14)

* Fix: Fetch database views not working when database is not saved in the Notes Data directory
* New: Updated the PDF Converter libraries

## Version 1.58 (2017-Oct-20)

* Fix: Crash when exporting large emails
* New: Updated the PDF Converter libraries

## Version 1.57 (2017-Sep-29)

* Fix: Disabled console logging when exporting documents

## Version 1.56 (2017-Sep-21)

* Fix: Improved memory handling

## Version 1.55 (2017-Sep-14)

* New: Updated the PDF Converter libraries

## Version 1.54 (2017-Aug-18)

* Fix: Notes crash when converting MIME documents

## Version 1.53 (2017-Aug-09)

* Fix: Exported view contains no values
* Fix: Bullets shown instead of numbers in numbered list
* Fix: Unknown HTML symbol
* Fix: Hotspot processing error
* Fix: Content displayed outside of table in RTF
* Fix: Space inserted between sections
* Fix: Section indentation issue

## Version 1.52 (2017-Jul-12)

* Fix: Database activation throws error

## Version 1.51 (2017-May-24)

* Fix: Watermark issue

## Version 1.50 (2017-Apr-21)

* New: Attachment options
* New: Add progress counter when creating view structures
* New: Automatic web viewer updates
* New: Folder shortcuts
* New: Major performance improvements
* Fix: Process failed documents again automatically
* Fix: Handle "not categorized" view category
* Fix: Export job cancellation not working as expected
* Fix: Columns empty when exporting with Notes 7
* Fix: Field with $ref value should be rendered as doclink

## Version 1.07 (2017-Mar-13)

* Fix: PDF Settings not applied
* Fix: Horizontal scrollbar not shown in IE

## Version 1.06 (2017-Feb-01)

* Fix: Define hidden columns
* Fix: PDF Settings not working

## Version 1.05 (2017-Jan-26)

* New: Attachment options
* New: Embedded view doclinks
* New: Horizontal scrollbar for views with many columns
* New: Option to select all views for export
* New: Alternate forms functionality redesign
* New: Structured view selection menu

## Version 1.04 (2016-Dec-22)

* Fix: Display issue in General settings
* Fix: Don't add views that failed to export to JSON
* Fix: Error when one view has no documents
* Fix: Export stuck on Calculating view entries total
* Fix: Run application code on Server only on server
* Fix: Subcategories with totals: subcategory captions are missing
* Fix: Totals - column missing
* Fix: \[PDFC] Embedded view should be empty
* Fix: Notes UI improvement
* New: Exception logging
* New: Trial: 100+ documents

## Version 1.03 (2016-Nov-18)

* Fix: Alternate form settings - use only on mail databases
* Fix: Child documents columns empty
* Fix: Clean hash from attachment filename
* Fix: Document conversion failed, no additional data available (code 14)
* Fix: Margins settings disregarded
* Fix: PDF Settings always in inch
* Fix: processColumnEntry NullPointerException
* Fix: Variant does not contain a container
* Fix: ViewToJson Type mismatch
* Fix: Warning message
* Fix: "Conversion finished" on Notes 7
* Fix: \[PDFC] Embedded view not displayed correctly

## Version 1.02 (2016-Oct-26)

* Fix: Column positions moved
* Fix: Dialog: Select views
* Fix: Object variable not set
* Fix: Overflow error when exporting view
* Fix: Response documents misplaced
* New: Add version number in log

## Version 1.01 (2016-Oct-13)

* Fix: Better error handling
* Fix: Duplicated view names on conversion re-run
* Fix: Invalid data types in view columns
* New: Metadata is missing explanation

## Version 1.00 (2016-Oct-04)

* Initial version


# Flex

## Version 2.0.14 (2026-June-11)

* You can now customise the Web Viewer by modifying its CSS files.
* Archive indexing has been simplified to support indexing a single archive at a time.
* When a View Entries index is created, the first view request is cached and reused for a configurable period, improving performance.
* Memory management has been improved for better stability and efficiency.
* You can now stop an indexing operation while it is in progress.
* A *Created By* field has been added to search results, providing additional context for indexed content.

## Version 1.24.0 (2025-July-18)

* Issues with manually updating the license has  be fixed.
* Added ability to disable fuzzy search.
* A sidebar has been added when clicking on an audit entry.
* Issue with doing the clean installation has be resolved.
* Error message that appears when the authentication is disabled, has been resolved.

## Version 1.23.1 (2025-July-02)

* Issues with the control panel have been fixed

## Version 1.22.0 (2025-Feb-03)

* Switched from SHA1 to SHA256 for signature evaulation

## Version 1.21.0 (2025-Jan-29)

* &#x20;It is not possible to create new Flex users without a password assigned.
* The ability to sort the audit log by timestamp has been disabled.
* Users last login column and Audit timestamp column in the Audit log is now in 24h format.

## Version 1.20.0 (2025-Jan-20)

* Issues with searching by UNID have been resolved.
* The ability to disable the Audit log is now available.
* The columns in the Audit log are now sortable.

## Version 1.19.0 (2024-Nov-12)

* The issue with child document has been resolved.

## Version 1.18.0 (2024-Oct-05)

* The issue with the date columns not properly being indexed has been resolved.
* Searching view columns by UNID now works properly.
* Issue with the child documents result limited to 10 docs has been fixed.
* Issue with saving the user with no name and email fields populated has been resolved.
* Issue with logging in when the URL is saved in favorites has been fixed.

## Version 1.17.0 (2024-Sep-06)

* Issue with searching view columns by UNID, has been resolved
* For the issue with indexing large attachments, an option has been added to adjust the attachment size limit.

## Version 1.16.0 (2024-July-31)

* UNID of the document is now searchable in Flex.
* Issue when sorting catalog with multiple pages, has been resolved.
* The issue with searching catalog columns with multiple catalog pages, has been fixed.

## Version 1.15.0 (2024-July-11)

* The issues that occurs when there is an Active directory user and Seascape user with the same name, has now been resolved.
* Issue with adding Active directory user to Seascape groups has been fixed.

## Version 1.14.0 (2024-May-22)

* The problem with updating the license has now been resolved.
* Issue with indexing the archive has been resolved.

## Version 1.13.0 (2024-Mar-27)

* The problem with searching inside attachments is now fixed.
* Issue with updating the license, has now been resolved.
* Issue with the search when a backslash is inside the query has been resolved.
* The Issue with default search has been fixed.
* Not being able to sort the results list has been fixed.
* Seascape Flex will not start until Elastic Search is up and running.
* Issue with the catalog not opening correctly, has been resolved.
* In case of the service failing, service start/stop actions are now updated correctly.

## Version 1.12.1 (2024-Jan-26)

* The issues with Indefinitely search when using AND or OR operators with missing parameters,has been resolved.
* Issues with searching view columns values has been resolved.
* The issue with user conflict when authentication is disabled, has been resolved.
* Checkbox is disabled in users list for AD user.
* Option added to remove groups from the archive.
* Issue with indexing large views has been resolved.

## Version 1.9.2 (2023-Jun-19)

* Option has been added to be able to remove groups form a specific archive.
* Issues with the names and date field in the search results, has been resolved.
* Custom column naming capability has been added.
* Issue with opening the default view for the first time, has been resolved.
* User list checkbox for active directory users has been disabled.

## Version 1.9.0 (2023-Mar-01)

* Improved index progress reporting
* Option to disable authentication has been added

## Version 1.8.0 (2023-Jan-13)

* Database search results as list view are enabled

## Version 1.7.0 (2022-Sep-27)

* Issue with the unique ID not being recognized in the archive folder has been resolved
* Issue when searching for two strings using "and" in between has been resolved.

## Version 1.6.0 (2022-Sep-12)

* Concurrent sessions with the same username have been disabled
* Issues when the search contains "-", have been resolved
* Issues with categorized entries showing documents that should not be there have been resolved

## Version 1.5.0 (2022-Aug-03)

* Issues with the license activation dialog appearing has been resolved
* Ability to completely remove an archive has been added
* Reporting feature for Flex usage added
* Issues with the admin password being too long have been resolved
* Issues with database indexing have been resolved

## Version 1.4.0 (2022-Jul-05)

* Added minor improvements and fixes.

## Version 1.3.0 (2022-May-11)

* Highlighting error on large attachments
* Reports progress while indexing databases in Seascape Flex

## Version 1.2.0 (2022-Jan-26)

* Nest Plugin updated
* .DWG attachment issue resolved

## Version 1.1.0 (2021-Dec-06)

* Added minor improvements and fixes.

## Version 1.0.0 (2021-Nov-24)

* Added minor improvements and fixes.


# Database archiving with Seascape


# Archiving methods (Videos)

SWING Seascape allows you to export Notes data to a standalone **Web Archive**, a **Microsoft SharePoint library or list**, or a **designated folder** on your disk. The quick videos below demonstrate how each of these three archiving methods works.

## Web Archive

This video demonstrates how to export Notes databases to a Web Archive. For more details, please refer to our [Web Archive Overview](/seascape-for-notes/archiving-with-seascape/creating-a-web-archive) guide.

{% embed url="<https://www.youtube.com/watch?v=wAm2p11ntIA>" %}

## SharePoint Archive

This video demonstrates how to export Notes databases to a SharePoint site with automated creation of SharePoint library and lists. For more details, please refer to our [SharePoint Archive Overview](/seascape-for-notes/archiving-with-seascape/sharepoint-archive-overview) guide.

{% embed url="<https://www.youtube.com/watch?v=k2rPtNPane0>" %}

## Extract to Disk

This video demonstrates how to export Notes databases to a local folder. For more details, please refer to our [Extract to Disk](/seascape-for-notes/archiving-with-seascape/creating-a-disk-archive) guide.

{% embed url="<https://www.youtube.com/watch?v=wokmoXqh47M>" %}


# Web Archive - Overview

The Web Archive is a standalone web application which you can open in any web browser. It consists of the the following elements:

* The PDF documents generated from the Notes documents
* JSON files which store the Notes metadata
* Notes attachments (Word, Excel, and similar files)
* HTML, CSS, and other UI files

For a complete overview of the files that are generated with the Web Archive please see our article on the [Web Archive Structure](/seascape-for-notes/archiving-with-seascape/creating-a-web-archive/web-archive-structure).

The archive's browser interface is described in the [Web Archive Interface](/seascape-for-notes/archiving-with-seascape/creating-a-web-archive/web-archive-interface) article.

The Web Archive is launched by opening the **index.html** file found in the archive's root folder.

The archive’s interface features all of the application views that you chose to export. This views are fully searchable and sortable. Additionally, the links between documents are preserved and remain functional.

If you have multiple databases then you can export them to a single Web Archive in a batch process. In this case Seascape creates a separate folder for each database and also a [Database Catalog](/seascape-for-notes/archiving-with-seascape/creating-a-web-archive/database-catalog) page, which shows all of the databases that have been added to the Web Archive.

You can host your Web Archive locally, in a shared network folder, or any web server (eg. IIS, Apache, or other).

{% hint style="info" %}
The Web Archives do not require Lotus Notes or Domino to run, since they are built entirely on open standard formats such as HTML, PDF, and JS. All that is needed to open a Web Archive is a web browser.
{% endhint %}

For advanced capabilities such as full-text search, user access management, and unlimited scalability, you can install the Seascape Flex server and link it to your web archive. For more information see our [Introduction to the Flex Server](/seascape-for-notes/seascape-flex/what-is-seascape-flex).&#x20;


# Export databases to a web archive

### Starting The Web Archive Export

To create a **Web Archive** click on the Web Archive option in the main menu:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB4RUc7MR9m_9n0X9z%2F-MlB4kwnCdg6IU5n1POp%2Fimage.png?alt=media\&token=c8c8982e-4efd-40b8-b49f-afd7616d99fc)

Next, select **one or more databases** to be exported (using the "Plus" icon), select the **export settings**, select the **destination folder**, and click **Next**:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB4RUc7MR9m_9n0X9z%2F-MlB4plNPzMij0egnPlY%2Fimage.png?alt=media\&token=73c5d032-a932-4eb3-a0bd-d5e323e410cf)

{% hint style="info" %}
The **export settings** can be configured on the **Settings page** and allow you to configure the export options such as **attachment export**, **PDF rendering settings**, and more
{% endhint %}

You can now review the export summary info. When you're ready to continue, click **Start export now:**

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB4RUc7MR9m_9n0X9z%2F-MlB4u9fvjtUCP5MtJz4%2Fimage.png?alt=media\&token=453dd959-2fed-451d-a211-450a08b759db)

A new window will pop up, containing the progress bar showing the progress of your export:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FFRCFmZCycujUYyN3JZZG%2FwebProgress.png?alt=media&amp;token=d2db73fb-a155-4981-8752-6b33834bcfce" alt=""><figcaption></figcaption></figure>

After the export is completed, click **Open in browser** to open your archive in a web browser:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2Fw6PNhj89K9BwxzIbsXg1%2FwebFinish.png?alt=media&amp;token=a29e97c7-ce69-4421-af20-0be6f93e34a3" alt=""><figcaption></figcaption></figure>

### Database Selection Dialog

The **Database selection dialog** opens up when you click on the **Plus icon** in the database selection menu:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB4RUc7MR9m_9n0X9z%2F-MlB54g_pObt6o1qzrzI%2Fimage.png?alt=media\&token=4c1fb76e-3871-4811-a6ce-b98a46d53d5b)

The dialog allows you to select the databases from your **Notes workstation** or a **Domino server:**

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB4RUc7MR9m_9n0X9z%2F-MlB58aD9CfTS05pfxPY%2Fimage.png?alt=media\&token=1fe0ed4e-1a96-4abd-befa-983a5eec9d48)

Note that the selection dialog has two modes, the **advanced** and **classic** mode.

The **advanced mode** is shown in the above screenshot and opens by default. It allows you to select multiple databases all at once, by simply selecting them in the view.

The advanced dialog sometimes loads slowly, as it needs to analyze the databases and create a view for database selection.

If the advanced dialog is taking too much time to load, you can switch to the **classic mode** using the link shown in screenshot below:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB4RUc7MR9m_9n0X9z%2F-MlB5IRdqBasXFctQgW5%2Fimage.png?alt=media\&token=3ac08438-913a-45c3-b77b-da52f51d7a7d)

The classic selection dialog opens immediately each time. Click the **Add Database** link to select databases one at a time and add them to the dialog:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB4RUc7MR9m_9n0X9z%2F-MlB5MIN5IHOrpj1Er-2%2Fimage.png?alt=media\&token=4a39ce39-29a1-4887-8507-17ab79c5b826)

After you've selected your databases click OK, and you will be returned to the main export page.

### View Selection Dialog

After selecting a database to export, you can also click on the Views option to select specific views to export from the database:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB4RUc7MR9m_9n0X9z%2F-MlB5Q407Wv3K9Ye7KHJ%2Fimage.png?alt=media\&token=b9846df6-052a-40dc-b37a-3a8d08c73414)

The view selection popup now appears where you can select the views to export:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB4RUc7MR9m_9n0X9z%2F-MlB5UYX8izbUqYpjMXh%2Fimage.png?alt=media\&token=767061bc-59d8-4421-8d34-bcc0806fa907)

If the popup doesn't list all of your views then click **"Refresh views list".**

To show hidden or private views click the **"Show hidden and private views"** link on the right.

If you select all views, then an additional option will appear that also allows you to export unreferenced documents (documents that are not associated with any one view):

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FflTnARcHqOjGiQYI4hga%2Fimage.png?alt=media\&token=b0da9a8f-f475-4569-9eaa-aca35e68de84)

If you are exporting multiple databases, then you'll have the option of exporting either the **default view** from each database, or **all views** from all the databases:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB4RUc7MR9m_9n0X9z%2F-MlB5_cfsjELe80KQiCs%2Fimage.png?alt=media\&token=a62f694b-b65e-4923-b923-e7204a612c92)

### Document Selection Dialog

If needed, click the **Documents pencil icon** to add an additional filter and export only the documents meeting a specific criteria:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB4RUc7MR9m_9n0X9z%2F-MlB5cWJ2wxXmX7O6Yxx%2Fimage.png?alt=media\&token=7ba403cc-3870-472c-ab5a-5c8df6562187)

The document selection popup now appears where you can select documents created or modified in a specific date range.

Additionally, you can also define a Notes formula to set up a custom document selection criteria:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB4RUc7MR9m_9n0X9z%2F-MlB5fyTXa6D35-UhXhV%2Fimage.png?alt=media\&token=0f6dc196-87f4-43eb-82d3-be16e95becde)

### Custom Metadata

To add custom metadata to your export, click on the **Custom Metadata** link and configure your metadata creation settings using Notes formulas:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB4RUc7MR9m_9n0X9z%2F-MlB5jDDEYwk_2rLDOAF%2Fimage.png?alt=media\&token=2301d022-a606-4e50-9a45-21c8569b9a89)

The custom metadata is saved in JSON files in the Web Archive along with the regular metadata extracted from Notes.

### Doclinks

The Notes doclinks are converted to special PDF hotspots that you can click on in order to open another linked PDF document in the archive.


# Web archive file structure

The below screenshot show the file structure of the Web Archive on your disk:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB2Cq8TKQmxJr-EpMT%2F-MlB2akk5DO4mD13VS8m%2Fimage.png?alt=media\&token=ae40f65e-6670-4742-86f6-a84141940054)


# Web Archive interface

Below is a screenshot of the Seascape web archive opened in a web browser (click on the image for a bigger display).

The archive interface consists of several elements as indicated by the numbers 1-5 on the screenshot.

Here is a description of each design element:

* **(1) Toggle button** — enables switching between different views (in case more than one document view was exported from Notes)
* **(2) View frame** — displays all of the document categories in the currently selected view. Clicking on any of the categories here brings all the documents associated to that category in the document frame.
* **(3) Document frame** — displays the archive's PDF documents which can be opened by double-clicking. Documents can be sorted by clicking on column headers.
* **(4) Search box** — used to quickly locate a document in the current view.
* **(5) Metadata sidebar** — displays the Notes document properties and document attachments

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB2eMAafzXv6iqObxy%2F-MlB2kkM2j7EL7L80Id4%2Fimage.png?alt=media\&token=7c1890bb-2d27-440c-ae4e-cfdabf018009)

### Document Links

The documents that you export into Seascape archives will remain linked via file links in the same way as the Notes documents were linked via doclinks.

When you click on a link in a PDF record then the linked PDF record will be automatically opened (assuming that the linked PDF has also been exported and saved in the archive).

The Web Archive also supports cross-database links, so long as both of the databases have been exported to the same archive.


# Database catalog

When you export multiple databases to a **Web Archive**, Seascape automatically generates a **Database Catalog** which is used as a starting point for users who wish to browse the archived applications.

Here is a screenshot of a sample database catalog:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FSIs0jkCO6R6BSHwNcYXs%2F2022-06-02_11h22_20.png?alt=media\&token=b9606e47-ddc6-44ff-af27-fdb60981eb4c)

You can use the icon in the top-right corner to switch between the table and tile views.

The database catalog can be searched and sorted using any of the available database properties such as the title, template, server, etc.

This screenshot shows the structure of the Database Catalog and how to launch the catalog in a web browser from your disk:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB2qtp-JZEijLYve_F%2F-MlB32mPxb_xNJ8naxVq%2Fimage.png?alt=media\&token=0b4c8af8-cd3c-4647-a8cd-bc460f144e72)

You can also save the entire archive on any web server, and provide your users with the URL to the catalog's **index.html** file.


# Option: Seascape Flex server

For advanced scalability, full text search, advanced search across multiple databases, and user access permissions, learn more about [Seascape Flex server](/seascape-for-notes/seascape-flex).


# SharePoint Archive - Overview

SWING Seascape provides a structured and user-friendly way to move Lotus Notes content and data into Microsoft SharePoint. The archiving process ensures that Lotus Notes documents, attachments, and metadata are preserved, while providing end users with intuitive access through SharePoint lists and libraries.

## SharePoint version support

* **Microsoft SharePoint Online** is supported.
* **SharePoint On-Premise** is not supported; however options may be available through SWING Software Export Services Program. [Contact us](http://www.swingsoftware.com/pdf-converter/notes-export-services) for more information.

## Data migration methods

Seascape SharePoint Uploader supports two methods for migrating databases to SharePoint:

1. **Structured Upload** (recommended) – Automatically creates lists, libraries, pages, views, and cross-links: Seascape Uploader creates one or more SharePoint lists to store Notes field data, generating a separate list for each Notes form found in the database. It also creates a SharePoint library for Notes documents (as PDFs) and cross-links list items to their corresponding documents, attachments, and related items, preserving the complete parent/child document structure.
2. **Flat Upload** – Uploads all Notes documents into a single existing SharePoint list or library: You must first create the SharePoint list or library, including all fields/columns you want to populate with Notes data. During the upload process, you will need to map the Lotus Notes fields to the corresponding SharePoint fields/columns you created.

Below is a side-by-side comparison of the Structured Upload and Flat Upload data migration methods:

|                                                                                           | STRUCTURED UPLOAD                                                                                                                                                                                                                                                                                                                                            | FLAT UPLOAD                                                                                                                                                                                                                                                                                                                                                                         |
| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Creates SharePoint lists and libraries automatically?                                     | Yes                                                                                                                                                                                                                                                                                                                                                          | No                                                                                                                                                                                                                                                                                                                                                                                  |
| Option to show/hide additional view columns (Notes fields) after the export is completed? | Yes. In each list view, a few primary columns are displayed by default, while the rest are hidden (and can be enabled as needed).                                                                                                                                                                                                                            | No. In the list or library, you can only have the columns that you created before starting the data migration.                                                                                                                                                                                                                                                                      |
| Creates a database catalog page in SharePoint (Home Page)?                                | Yes                                                                                                                                                                                                                                                                                                                                                          | No                                                                                                                                                                                                                                                                                                                                                                                  |
| Supports upload of multiple databases?                                                    | Yes                                                                                                                                                                                                                                                                                                                                                          | No, only one database at a time can be uploaded.                                                                                                                                                                                                                                                                                                                                    |
| Requires manual field mapping?                                                            | No                                                                                                                                                                                                                                                                                                                                                           | Yes                                                                                                                                                                                                                                                                                                                                                                                 |
| Supports automated indexing of SharePoint columns?                                        | Yes                                                                                                                                                                                                                                                                                                                                                          | No, columns need to be indexed manually.                                                                                                                                                                                                                                                                                                                                            |
| Is there a limit to the number of SharePoint columns?                                     | Yes, each list is subject to standard [SharePoint column limits](https://learn.microsoft.com/en-us/sharepoint/install/software-boundaries-limits-2019?utm_source=chatgpt.com#list-and-library-limits). However, because each Notes form becomes a separate list in SharePoint, each list typically accommodates ALL fields found on the original Notes form. | Yes, each list and library is subject to standard [SharePoint column limits](https://learn.microsoft.com/en-us/sharepoint/install/software-boundaries-limits-2019?utm_source=chatgpt.com#list-and-library-limits). When you create your list or library, you must carefully consider which fields/columns to create, as it is not possible to add additional columns in the future. |
| Supports SharePoint view filters, group-by, and other view operations?                    | Yes                                                                                                                                                                                                                                                                                                                                                          | Yes (only in SharePoint lists)                                                                                                                                                                                                                                                                                                                                                      |
| Supports creation of folder structure in SharePoint, including custom naming rules?       | No, documents are organized in a way that doesn't require folders or custom file names to navigate the content.                                                                                                                                                                                                                                              | Yes.                                                                                                                                                                                                                                                                                                                                                                                |

## Export process overview

The export process in Seascape consists of two distinct parts:

1. **Exporting from Lotus Notes to a local folder**
   * Selected Lotus Notes databases are exported locally.
   * During export:
     * Notes documents are converted into **PDF files**.
     * File attachments are exported in their **native file formats**.
     * Metadata from Lotus Notes is preserved in **XML files**.
2. **Uploading to SharePoint**
   * The exported content is uploaded to SharePoint using Seascape’s built-in SharePoint upload utility using either the Structured Upload (previously auto-config) or Flat Upload (previously manual-config) mode.
     * **Structured Upload** (previously auto-config)
       * When the upload begins, a **Database Catalog** page is created, serving as the entry point to the database archive.
       * For each Lotus Notes database a **separate SharePoint library** is created automatically which stores the PDF files and file attachments.&#x20;
       * Additional **SharePoint lists** are created for each Lotus Notes form found in the database. Each list’s **columns** are generated based on the fields defined on the Notes form.
     * **Flat Upload** (previously manual-config)
       * The the SharePoint upload tool is launched, you'll need to switch to the Flat Upload (manual config), and map your Lotus Notes fields to the corresponding SharePoint fields/columns (the SharePoint list or library already needs to be in place at this point).

## Key benefits

* **Preservation of context**: Documents, attachments, and metadata remain accessible in a structured format.
* **Familiar navigation**: End users can interact with document links and attachments in ways similar to Lotus Notes.
* **Automated mapping**: SharePoint lists, libraries, and columns are automatically created based on the structure of the source Lotus Notes databases.

***


# Structured Upload (recommended)

Automatically creates SharePoint lists, libraries, pages, views, and cross-links

## Database export and upload to Sharepoint

Follow the steps below to export your Notes databases from Seascape to Microsoft SharePoint using the auto-mode method.

1. From the **Seascape home page**, click **SharePoint**.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2Fbm81mEPwu2xjNS9i7UEj%2F01.png?alt=media&amp;token=bbe71631-438e-44f5-bb01-95d753d8c82e" alt=""><figcaption></figcaption></figure>

2. Select your database(s), configure the export settings, and choose a **staging folder** (this is where the exported data will be temporarily saved).

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FjpF5V3diMl8W1EPK4Ii1%2Fexport.png?alt=media&amp;token=248d9678-e9e7-408a-a268-1ba36eeda5c1" alt=""><figcaption></figcaption></figure>

3. Click **Start export now**.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FBgPTtfynZLlA4LFdpE0M%2FexpRev.png?alt=media&amp;token=c39e362e-294a-4571-9670-466ab257e703" alt=""><figcaption></figcaption></figure>

4. When the export finishes, click **Upload to SharePoint**.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FTJHzALR5fWo1vJJYuY58%2FexpCompl.png?alt=media&amp;token=21e69560-ebc9-4ca6-b790-6b302bc23634" alt=""><figcaption></figcaption></figure>

5. The **SharePoint upload utility** will open. Select your database(s) and click **Next**.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FKbx9HCtA3yAGtfU8sWQP%2FarchSelection.png?alt=media&amp;token=3c3f6074-0bd7-4dd6-85fe-52a1a32a4913" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
To select multiple databases, hold the **Ctrl** key and click each database you want to upload.
{% endhint %}

6. Click **Add a site**, then enter a **connection name,** choose an **authentication type** and enter the **site address**. Click **Test Connection**.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F6pWhMuAfrglOy5Rvcs6B%2FarchSelection2.png?alt=media&amp;token=62a785e9-aedb-4a24-bde2-afa02ad30577" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
Make sure you are logged into your SharePoint site in your browser before creating the connection.
{% endhint %}

7. When the connection is confirmed, click **Save settings** to save it.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FB1VwgDuaO8jH7zy7kOsE%2FsaveSiteConn.png?alt=media&amp;token=a0c7742b-ead1-4ce6-951c-69465859bbd0" alt=""><figcaption></figcaption></figure>

8. Select the saved connection in the connection dropdown and click **Connect**.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FkmtzIH8MLjeFKLDWcqlr%2Fconnecting.png?alt=media&amp;token=c58ff1a9-d48a-4f5d-8275-27b3a1487a3d" alt=""><figcaption></figcaption></figure>

9. Click **Next** to move to the final step.
10. Review the upload configuration. If needed, adjust the optional settings, then click **Start upload**.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F9mn0KR06gPENaeLjoy0f%2FstUpload.png?alt=media&amp;token=c12d07e7-5140-4679-ac80-17b3ecf2df8a" alt=""><figcaption></figcaption></figure>

11. The upload will begin. You can monitor progress in the **runtime log**.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FaKqgFg2tLXbE7K77NikM%2FupProcess.png?alt=media&amp;token=6e330071-3673-47ad-be3a-a8724203a660" alt=""><figcaption></figcaption></figure>

12. Once complete, the uploaded databases will appear with direct **links to the SharePoint archives.**

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FLU3uRh23UX4oLvdQPKZo%2FupComplete.png?alt=media&amp;token=8594277e-500e-4b0b-9b07-8e666c8f2a3b" alt=""><figcaption></figcaption></figure>

## Navigating database archives SharePoint

### Example: Multiple databases

Here is a SharePoint site where three Lotus Notes databases have been migrated:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F10aNtS22PmJE5chFnUol%2Fimage.png?alt=media&amp;token=aefe98c1-72fb-415a-8e03-9a9e08c7ede5" alt=""><figcaption></figcaption></figure>

### Example: Opening a database

When we open one of the databases, we see the lists associated with that database. In the following example, the demo NFL database shows two lists, **Team** and **Player**, since the NFL database included two form types with those names:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FfGjrpX3GsrDc9Bo92HXT%2Fimage.png?alt=media&amp;token=eaf605d8-420e-4953-aa39-f76fee31f1b0" alt=""><figcaption></figcaption></figure>

### Example: Viewing a list

Clicking on a list displays its items (previously Notes records). For instance, opening the **Team** list shows all teams and their properties:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FNjcgm75KUVk9EwPhUB4K%2Fimage.png?alt=media&amp;token=910f2675-4f90-4397-8728-dd9997a311b0" alt=""><figcaption></figcaption></figure>

* The **ND column** opens the main PDF document (a copy of the original Notes record).
* Additional columns provide access to **related items** (child records) and **file attachments**.

In the example below, the *Dallas Cowboys* list item includes several related items (players) and two attachments, which are accessible through the provided columns:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2Fa2YDdGqx9Yqpu5YlOx6m%2Fimage.png?alt=media&amp;token=d9f87e5b-5663-4b82-8cc6-e4ab46493eda" alt=""><figcaption></figcaption></figure>

### Example: Viewing related items (child records)

Clicking on the **Player** icon from the Dallas Cowboys list item, shows the Player list filtered to display only the related items for the selected parent. Users can also return to the parent by using the shortcut in the **PDoc column**.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F4nWW9mMJWAXHW4vJoxLx%2Fimage.png?alt=media&amp;token=bd628ded-1a84-476b-ad3f-9b07346df991" alt=""><figcaption></figcaption></figure>

### Example: Viewing attachments

Clicking on the **Attachments** shortcut opens another view where users can access files associated with the parent list item:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FRMhOtOm5Cm9nPg70KW9G%2Fimage.png?alt=media&amp;token=6c42f028-92e6-46f6-8d10-f9801029beca" alt=""><figcaption></figcaption></figure>

### Example: Opening a PDF record

The following screenshot shows a PDF generated from the *Dallas Cowboys* Notes document. Within the PDF:

* **Doclinks** remain active, allowing users to navigate to related records.
* **Attachment icons** provide direct access to the original files.

This mirrors the user experience in Lotus Notes.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F4hNhIivt292Ye34e8kx1%2Fimage.png?alt=media&amp;token=91da478c-9a7a-49b3-b079-fbb236991212" alt=""><figcaption></figcaption></figure>

## Completing the Migration

The Lotus Notes database archive has been successfully migrated to your SharePoint site without requiring manual intervention.&#x20;

You can now use SharePoint features such as creating additional views, grouping, filtering, sorting, and applying advanced formatting to list views.&#x20;

Integration with Power Apps, Power BI, and Power Automate enables the creation of custom forms, advanced analytics, and automated workflows.


# Flat Upload

Uploads all Notes documents into a single existing SharePoint list or library

&#x20;With Flat Upload (or manual mode) to SharePoint, you will need to:

* Create the SharePoint Library or List in advance.
* Map the Notes fields to SharePoint fields during the upload stage.

## Database export

To begin the export process click on the **SharePoint** icon on the Seascape home page:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB6BNvUlF5Yz8pNPIc%2F-MlB6KUi9xXW9fUszAxs%2Fimage.png?alt=media\&token=539086fa-141c-4347-89b5-fdfe14642c22)

Next, select a **database** to be exported, the **export settings**, and the **staging folder**, and click **Next** to being your export:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F90pRwVHRw2p0jUq8vfFN%2F1.png?alt=media&amp;token=482d6676-dd6f-4ae5-9a12-39359ace7b78" alt=""><figcaption></figcaption></figure>

A window with an overview will appear.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FQqmycdcTZfkBtkR6t0AV%2F11.png?alt=media&amp;token=cc5e1846-2d37-4047-b05f-a7b10385379f" alt=""><figcaption></figcaption></figure>

Once you click on **Start export now** button a new window will appear showing the progress of your export.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FcC9HRKziiXdtvfAGCDEZ%2FspProgress.png?alt=media&amp;token=ee8a7d33-504b-4f62-b809-fbdea0901f72" alt=""><figcaption></figcaption></figure>

Once the database is exported to the **staging folder**, click on the **Upload to SharePoint** button to open the **SharePoint Upload Utility** in a new window:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FoqAEcmLkfexqEH9fjENA%2F3.png?alt=media&amp;token=3bbe16f4-5f14-435b-87ba-9c1c9120f03a" alt=""><figcaption></figcaption></figure>

This is how the folder structure of the staging folder should like like:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FtaQwoGGJVFNmE1xghvjS%2FspStructure1.png?alt=media&amp;token=802bf723-0b56-409c-8fef-289616a8f7e6" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FTZ5TQEgPf4eHrjAiFHbU%2FspStructure2.png?alt=media&amp;token=df724f18-cbf1-46e1-a3ff-0d2d36e77a21" alt=""><figcaption></figcaption></figure>

You can now upload your archive either to a **SharePoint library** or a **SharePoint list**.

{% hint style="info" %}
The PDF files generated during the export will be named using the document ID string by default. To have the files named using a different naming convention simply configure your PDF naming formula in the export settings. More info: [Export Settings](/seascape-for-notes/seascape-settings/export-settings)

You can also have Seascape generate a custom folder structure during the export, which will then be replicated in your SharePoint library too. For more information please see our article on [Folder Formulas](/seascape-for-notes/seascape-settings/folder-formulas).
{% endhint %}

## Upload to SharePoint

The **SharePoint upload utility** allows you to upload exported Notes data from a staging folder to a **SharePoint library** or a **SharePoint list**.

The utility launches automatically after a database export is completed from the SharePoint archiving page. You can also launch it manually by using the **Upload existing archive** link on the SharePoint archiving page:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB7RgWLReCo6PBezt-%2F-MlB7_H02nNc-tJgu4Z1%2Fimage.png?alt=media\&token=7013d61b-e34e-49ba-adf7-67050a77f140)

{% hint style="info" %}
The SharePoint Library or List which you are uploading to must be created prior to uploading.
{% endhint %}

Below are the instructions for uploading the Notes data from a staging folder into a **SharePoint Library** or a **SharePoint list**.

### **Step 1: Selecting the database**

* When the SharePoint upload utility launches, click on the **Browse** button to select the **staging folder** that contains your exported Notes data.
* After the **staging folder** is selected, the utility will automatically display all archive folders within it.
* Select **one** archive folder you wish to upload to SharePoint and click **Next**:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FQxu7kKCddd3FPsVw1Hy8%2F4.png?alt=media&amp;token=2addcbef-5bc6-4ff6-a6bc-856d2f4304a1" alt=""><figcaption></figcaption></figure>

### Step 2: Connecting to SharePoint

* In **Step 2**, click **Add a site** to create a new SharePoint site connection or select an already existing one using the drop-down menu and connect, then click **Next**.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FHM3a4NwPbUAYBCKNB4DC%2F5.png?alt=media&amp;token=312718b2-db49-4e4b-b3b0-d056ee887cd4" alt=""><figcaption></figcaption></figure>

* When clicking on the **Add a site** button, the connection settings popup now appears where you can enter choose the authentication type and your SharePoint site URL. Then test the connection.

{% hint style="info" %}
The Site URL should be in the following format (without the .aspx part or any additional folders in the URL): [https://yourdomain.sharepoint.com/sites/yoursitename](https://swingsoftware365.sharepoint.com/sites/LotusNotesData)
{% endhint %}

* If the connection is established successfully, click **Save Settings** so you can re-use the settings for your future uploads:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FDiEeVqJFtVvGAW6IDg6Y%2FsavingConn.png?alt=media&amp;token=e5479145-ec68-4012-ae77-1c8a6148ac83" alt=""><figcaption></figcaption></figure>

**Note:** Use the Authentication type to change the authentication method if needed:

**Interactive:** Log in to SharePoint Online using your Tenant ID.

**Web login:** Log in to SharePoint Online or on-premises using web browser. Requires claims based authentications with FedAuth cookie. If you are previously logged in to SharePoint in the web browser on the machine where you are trying to do the upload, then it is enough to enter the "Name" and "Site URL". You can leave "Log-in URL" empty.

* Once you have connected to your SharePoint site, choose List or Library, and find your desired destination:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FOntUiuDgNUXtrgGuylk3%2F7.png?alt=media&amp;token=ee5e5228-a68f-48c9-a22b-ffc052f74490" alt=""><figcaption></figcaption></figure>

### **Step 3: Review and upload**

* In **Step 3**, after clicking on Next, you can review and update the SharePoint field [mappings](broken://pages/-MkmS6nL9_hwk-_FK-fL), and select the upload settings:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2Fk17UE36CZ0p1lwXcPxWT%2F8.png?alt=media&amp;token=73a9bbfd-5f11-459b-b8ab-d165611b05cd" alt=""><figcaption></figcaption></figure>

* Here is a description of the upload settings:
  * **Shorten Notes canonical name to common name:** "CN=Mary Tsen/OU=Illustration/O=Acme" becomes "Mary Tsen"
  * **Publish documents after upload (Check-In):** Documents will be published after upload (if unchecked, the uploaded documents will be saved as drafts)
  * **Overwrite existing documents:** Documents with the same PDF file name will be overwritten
* When you're finished, click **Start upload.**

During the upload, the upload progress information will be shown in real time:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FAP1EEwFue5oftto3wR4e%2F9.png?alt=media&amp;token=e7b4e0ef-86ad-4219-920f-6c65b6411b4c" alt=""><figcaption></figcaption></figure>

After the upload is completed, a summary of the uploaded data will be shown, and you can now open your SharePoint library (or list) and verify that all the data has been imported successfully:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FcSKf892wMwmBkRIR9use%2F10.png?alt=media&amp;token=6a8c111f-49ca-4fe4-b66b-2b8744e51796" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
In order to keep the Notes document links working on SharePoint a web part must be installed and added to the SharePoint site, more information can be found here: <https://docs.swingsoftware.com/seascape-for-notes/faq/how-to-enable-notes-doclinks-in-sharepoint>
{% endhint %}


# Extract to Disk - Overview

The **"Extract to Disk"** option enables you to export your Notes content to a folder on your disk.

This type of archive includes:

* **PDF files**, which store the content of the Notes forms
* **XML files**, which store the Notes metadata
* **Document attachments**

When creating your archive, you can choose to [**name the PDF files using configurable rules**](/seascape-for-notes/faq/how-to-configure-pdf-file-naming-rules) and [**generate a custom folder structure**](/seascape-for-notes/seascape-settings/folder-formulas) for storing the files.

The disk archive also **retains links between PDF documents**, preserving the same relationships that existed in Lotus Notes via doclinks.

For additional convenience, a CSV Creator tool is provided which enables you to merge the XML metadata into a single or multple CSV files (one CSV per Notes form). More info: [Save Notes metadata in CSV format](/seascape-for-notes/archiving-with-seascape/metadata-into-csv-format)


# Export databases to disk

To extract your Notes documents or email to disk, click on the **Extract to Disk** option in the main menu:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlB8wfdK7IwH3QoiX0W%2Fimage.png?alt=media\&token=c0596e01-7329-4bac-a41f-57b721e68dbd)

On the export page select **one or more databases** to be exported (using the "Plus" icon), select the **export settings**, select the **destination folder**, and click **Next**:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlB96JrR8Ielgu_7Qlt%2Fimage.png?alt=media\&token=3e73d021-3ecd-474c-bb08-29888e5c84e1)

{% hint style="info" %}
The **export settings** can be configured on the **Settings page** in Seascape. You to configure the export options such as **attachment export**, **PDF file naming rules**, **PDF rendering settings**, and more.
{% endhint %}

{% hint style="info" %}
For more information on how to select databases, views, and documents please see instructions further below in this article.
{% endhint %}

You can now review the export summary info. When you're ready to continue, click **Start export now**:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlB9AVLeUhL7LF_h8FK%2Fimage.png?alt=media\&token=841bc12b-927f-41ed-97ea-3ef6a19f6c1b)

A new window will appear containing the progress bar showing the progress of your export.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FCsL06juU6Q1jDSugsskr%2FextToDiskProgress.png?alt=media&amp;token=634a4cd0-e967-4de7-b640-bb72351d71e3" alt=""><figcaption></figcaption></figure>

After the export is completed, click **Open Archive** to open the destination folder containing the generated PDF files, attachments, and metadata.

You can also view the export log by using the **"See the Export Log"** link:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F3SbLGHbshhr7Jq4Uq5NK%2FextFinish.png?alt=media&amp;token=45c245cf-61bc-4e6f-9904-517d00aa4e4d" alt=""><figcaption></figcaption></figure>

## Database Selection Dialog

The **Database selection dialog** opens up when you click on the **Plus icon** in the database selection menu:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlB9PiD_uiKVMbJKZGP%2Fimage.png?alt=media\&token=8879b363-a630-4b72-9c77-a06692b8d1ec)

The dialog allows you to select the databases from your **Local workstation** or a **Domino server:**

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlB9Vah91jIBBUPSVeV%2Fimage.png?alt=media\&token=7665885e-a061-459a-84d0-605db21d5dfd)

Note that the selection dialog has two modes, the **advanced** and **classic**.

The **advanced mode** is shown in the above screenshot and opens by default. It allows you to select multiple databases all at once, by simply selecting them in the view.

The advanced dialog can sometimes load slowly, as it needs to analyse the databases and create a view for database selection.

If needed, you can also switch to the **classic mode**, using the link shown in screenshot below\*\*:\*\*

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlB9YmBzY-uyNqodwOI%2Fimage.png?alt=media\&token=b726bb2f-f6d7-4a8a-b935-4387c227921e)

The classic selection dialog opens immediately each time, and you can now click the **Add Database** link to select databases one at a time:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlB9b24DaM6-XB53GgN%2Fimage.png?alt=media\&token=45bffafc-9a1b-4416-8a19-1b03685b0930)

After you've selected your databases click OK, and you will be returned to the main export page.

You can choose to export **All documents in database** or **All documents in selected view(s):**

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlB9f2mz8tNMXEAlJ9m%2Fimage.png?alt=media\&token=0c4bfab6-6dc4-4e13-8545-3bcb6d9ce18d)

If you choose the **All documents in database** option, then in the export settings you can also choose whether to export the documents to a **single folder per database**, or to a **custom folder structure** which will be generated in the destination folder:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlB9iud1zrffRzvAEya%2Fimage.png?alt=media\&token=181c4cf4-afd3-454d-8264-b5865210996f)

If you select the **No Structure (single folder per database)** option, Seascape will create a folder for each selected database, and save the documents there.

If you select the **Custom Structure** option, Seascape will create a custom folder structure in the destination folder, and save the documents in the appropriate folders.

The folder structure is created using pre-defined **folder creation formulas** that you can select (for example **by author**, **by form name**, etc.)

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlB9nh8izJirZPMS7A2%2Fimage.png?alt=media\&token=138f9e48-0f40-4a44-9d00-ede4bb183120)

If needed you can also define your own custom folder formulas on the **Folder Formulas** tab on the **Settings** page:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlB9rLGJSh4_iw4jvig%2Fimage.png?alt=media\&token=666b0393-15b0-4124-9ce8-9bbd2c5ee093)

After you add a new folder creation formula it will be shown in the **Custom Structure dropdown list** on the export page where you can select it.

If needed, you can also add an additional rules for exporting only the documents that meet a specific criteria, by clicking on the **pencil icon**:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlB9twLzeE-GOAYjhm4%2Fimage.png?alt=media\&token=bbbae951-8f01-4133-9eec-02f2a58548ba)

A popup window is now shown where you can select your **document selection criteria** (for example documents created in a specific date range), or even define a **custom selection rule** using a **Notes formula:**

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlB9wv4dwAEeWzSklFV%2Fimage.png?alt=media\&token=d6698119-3d92-455b-a855-ddf55b9fbb5f)

To export specific document views select the **All documents in selected view(s)** option and then click on the pencil icon to select the views:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlBA-qTWe7CNebtc0LW%2Fimage.png?alt=media\&token=a61de289-6e95-428d-90be-67887b544efc)

A popup window now appears where you can select the required views. To select an outline instead, click **Views in outline**:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlBA3uEaPd8vafNF3CL%2Fimage.png?alt=media\&token=9f70291d-b12a-47e4-ba04-33b11878e70d)

Note that the view selection popup only appears when exporting a single database.

If you're exporting multiple databases, then a different popup is displayed, which allows you to export either the **default view in each database** or **all views:**

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlBABgmOd46HSCXsBaG%2Fimage.png?alt=media\&token=80397681-f856-4949-b1b7-17b2588b478d)

**Important:** When you're exporting document views to disk some duplication may occur (in the event a document is displayed in more than one document view).

## Custom Metadata

To add custom metadata to your export, click on the **Custom Metadata** link and configure your metadata creation settings using Notes formulas:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB8rnTwj38FS8zYmmt%2F-MlBAGhZz0rXKs24uXIv%2Fimage.png?alt=media\&token=be4b5b09-69a0-4c5e-bf57-27da45a67f46)

The custom metadata is saved in sidecar XML files in the disk archive along with the regular metadata extracted from Notes.

## Doclinks

The Notes doclinks are converted to special PDF hotspots that you can click on in order to open another linked PDF document in the archive.


# Export log

The **Export Log** provides a detailed overview of the database exports run by users:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBAJTq50YIyGB9XBWn%2F-MlBAO2TYHlps5gmMln4%2Fimage.png?alt=media\&token=d739bcfa-a719-484d-a09a-01e95baee2ad)

Click on any document in the history log in order to view more detail for that specific job.

Each log document consists of two parts, the **Job Summary** and the **Process Log**.

### Job Summary

The **Job Summary** provides basic information on a job such as the job status, last run time, the selected destination folder, databases/views/documents exported, and the export settings used for the job:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBAJTq50YIyGB9XBWn%2F-MlBAReMaBlyv0-L9okJ%2Fimage.png?alt=media\&token=d96c4996-97e6-4fd4-9389-d92f3e9e98c4)

If needed, you can repeat the job right from the log by clicking the **New export** button.

### Process Log

The **Process Log** contains process-level information which may be used for troubleshooting or debugging:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBAJTq50YIyGB9XBWn%2F-MlBAVpOQvN99SaX5WGR%2Fimage.png?alt=media\&token=755988d4-59d2-467e-80eb-bfb49f34ff09)

Click on the **View log file** link in order to open a log file which contains the run-time console output.

Additionally, if any errors occurred during the export, the information will be logged and you will be provided with the links to the documents that could not be exported, so that they may be inspected further.


# Database analysis tool

The **Database analysis tool** enables you to easily generate a report on Notes databases that are located on any Domino server or local workstation.

The report is intended to help you plan for your database archiving project by providing the most important information on each database including:

* Database size
* Number of documents
* Number of forms
* Number of views
* Average document size
* Number of attachments
* Average attachment size
* Number of MIME documents
* Number of encrypted documents
* Number of documents containing doclinks
* Number of documents with reader fields

To open the tool click the **Database analysis** link in the Seascape database and click **New Analysis**:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2Fhvpi6u8csEcd5bPPjcTP%2Fimage.png?alt=media\&token=483a6998-352c-490c-91cd-1abf099cb982)

Next, select the Domino server or specific databases to analyze, select the analysis level (deep or basic), and hit **Start analysis now** button:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F8QxwKbEU407yPkGHEKD9%2Fimage.png?alt=media\&token=2966777a-7fef-47db-9abf-251cd81ca70d)

The analysis tool will now begin to generate the report. Once the report is generated, click **View Analysis results** to open it:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F8TRqibIk2JPojTDu23EX%2Fimage.png?alt=media\&token=e780362d-1dd8-4457-a7f8-ae9d8829364b)

The report is now shown in a document view as shown in this example screenshot:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FdIEqCMLO6dmTFv4qMKSa%2Fimage.png?alt=media\&token=9d798a6d-df88-4820-af46-e01af3b8b473)

If needed, you can also export the report to a CSV file for easier analysis.

To export the report to a CSV file click **File > Export** in the Notes menu:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FR3b1dTWkNWQp8YvgKESi%2Fimage.png?alt=media\&token=f210d24d-72b7-4665-ac6e-2cf1a4cf38bd)

Next, select a folder where the CSV file will be saved, enter the desired file name (with the .csv file extension) and select **Comma Separated Value** as the file type.

When you're done, click the **Export** button:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FckmdoDun2FcgyAC79DUY%2Fimage.png?alt=media\&token=f1cecfe1-19b2-49bc-8f31-29464eb250fc)

A popup window now appears where you can select additional CSV export options.

Select the **Include View titles** checkbox in order to show the column headings in the first row in the CSV file:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2Fe40yssa6PcxAGW1UZ0HC%2Fimage.png?alt=media\&token=a96240c0-856a-49bf-92f1-6dba80e69e97)

When you're done, click OK and the CSV file will be generated.


# Save Notes metadata in CSV format

The CSV tool is used to merge the XML or JSON metadata generated by Seascape into a single or multiple CSV files.

To use the tool, download the zip package provided to you by SWING Software, unzip the package, and open the CSVTool.exe file:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FoQs4ce2R2DtpcSiVUzQE%2Ftool.png?alt=media&amp;token=e1663d75-d1f8-4153-992d-0fabfb544fce" alt=""><figcaption></figcaption></figure>

Once the tool is open, select the folder (the database archive) that contains the exported metadata, as source folder:

{% hint style="info" %}
If you are running the CSV tool on a disk archive, then the source folder must be the root folder containing the disk archive.
{% endhint %}

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FruADVzF2jTc6EXgHSZdD%2FSltSource.png?alt=media&amp;token=fee0393a-fdbb-4c63-817d-7f09d134a65d" alt=""><figcaption></figcaption></figure>

Next, select the destination folder where you would like the CSV file will be saved, or leave it as it and the CSV file will be saved in the source folder:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FMGL0SuZQ7y2l8lSGI6Nb%2FSltDest.png?alt=media&amp;token=c25228ee-235d-49fc-bfdd-c6b48dfd6ec4" alt=""><figcaption></figcaption></figure>

Finally select the CSV delimiter character you would like to use in the CSV file (typically a comma or a semi-colon) and select the **Create CSV** option, then click on **Next** button:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FXNxWFaxB96MNnJqvXPRt%2Fdelim.png?alt=media&amp;token=ff3830ed-d9e6-4ccf-a819-9ff84bc702c5" alt=""><figcaption></figcaption></figure>

To start the conversion process, select the database archive (could be multiple in source folder) and click on **Run**.&#x20;

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FA6mEL9rbPL1iRo630YxO%2Frun.png?alt=media&amp;token=2b153820-e3ad-4b28-b8f9-0c27fd34f9bf" alt=""><figcaption></figcaption></figure>

Once the process is completed you will receive a confirmation message. Clicking on the "OK" button will end the current process.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FJBbJ5hGuditUKP8n5MZa%2Fok.png?alt=media&amp;token=4ffabf75-ecdb-4f14-a2b0-dba96e7fcb3d" alt=""><figcaption></figcaption></figure>

The generated CSV file is now saved in the selected destination folder:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FbArjvFT8tDy8Nr1k0uSO%2FcsvFile.png?alt=media&amp;token=7cd37132-406d-4f21-8b77-ca69f0282264" alt=""><figcaption></figcaption></figure>

Options:

* **Create CSV for each form:** By selecting this option, a CSV file will be created for each form.
* **Create CSV for each individual view:** By selecting this option, a CSV file will be created for each individual view.
* **Create CSV with all file paths:** Selecting this option will create a CSV file capturing the relative and full path to all documents and metadata files contained in the archive.
* **Create CSV for embedded views:** Selecting this option will create a CSV file capturing the relative and full path for embedded views.
* **Create CSV for attachments:** Selecting this option will create a CSV file capturing the relative and full path for attachments.

{% hint style="info" %}
in case you need to use either of these two options (create CSV for each form/for each individual view) then the source folder should point to a specific database archive, not root folder.
{% endhint %}

{% hint style="info" %}
If any issues are encountered during the data merge process an error message is displayed and the error is logged in the log file.
{% endhint %}

{% hint style="info" %}
If there are multiple databases in the archive and you would like to get the metadata only for one specific database, then you would need to select the root folder of that database (not the root folder of the archive) as the source folder.
{% endhint %}


# Seascape Flex


# What is Seascape Flex?

## Get to know Seascape Flex

Seascape Flex is a lightweight server that automatically extends the capabilities of standalone Web Archives. It provides additional features including full-text search, advanced search across multiple databases, user management and access permissions, advanced performance and scalability.

Seascape Flex can be installed on a Windows **server** or a **workstation**. Once it is installed and linked to an existing Web Archive, it will automatically index the Web Archive’s PDF files, attachments, and metadata, and make them available for full-text searches via the advanced search dialog.

User management is handled either by connecting Seascape Flex to the organization's Active Directory or by creating internal users and groups in the Flex database. Once the user accounts have been set up, administrators can assign access permissions by simply selecting users or groups in each database.

Seascape Flex is built around the industry standard Elasticsearch engine, which provides organizations with uncompromising fast document searches and flexible options for scaling their archives.

Below is a quick comparison of the features supported by a standalone Web Archive and the advanced features that are enabled by deploying both a Web Archive and Seascape Flex on a server.

|                                           | Web Archive                                                                                                       | Web Archive with Seascape Flex                                                                                                                                  |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Deployment method                         | Copy the archive to a web server, shared network folder, SharePoint library, or a local folder on a PC or laptop. | Copy the archive to a server (or PC) on which Seascape Flex has been installed.                                                                                 |
| View column search                        | Yes                                                                                                               | Yes                                                                                                                                                             |
| Any field (metadata) search               | No                                                                                                                | Yes                                                                                                                                                             |
| Full-text search                          | No                                                                                                                | Yes                                                                                                                                                             |
| Search across multiple archived databases | No                                                                                                                | Yes                                                                                                                                                             |
| Access permissions                        | Not available. Access can be managed by configuring folder permissions.                                           | Access permissions are assigned in Seascape Flex. Users are authenticated by Active Directory. Alternatively, users and groups can be created in Seascape Flex. |
| Scalability                               | For best performance, it is recommended to keep the exported document views to under 500K view entries.           | There are no limitations on view sizes.                                                                                                                         |
| Audit log                                 | No                                                                                                                | Yes                                                                                                                                                             |


# Installing Seascape Flex

Here are the steps to install Seascape Flex.

1\. Download the **SeascapeFlexInstaller.msi** installation file and open it to start the **Setup Wizard**:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB37Ujd3HBpWLalSeC%2F-MlB3Fp_VPQhcDUwJfLj%2Fimage.png?alt=media\&token=675f4baa-369f-4983-b979-7ae6812d3c6e)

2\. Follow the wizard steps to complete the installation. Once the installation is completed, click **Finish** to launch the **Seascape Flex Control Panel**:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB37Ujd3HBpWLalSeC%2F-MlB3JK_qz23e1FZ4tHO%2Fimage.png?alt=media\&token=d0d80e48-b5e5-467d-b9a7-87a20c24f34e)

3\. In the Control Panel enter your IP address (use localhost if installing on a local workstation), enter a desired port number, and select the root folder of your existing Web Archive:

You will also need to enter a password for the initial Administrator user (the username is admin). When finished, click the **Start** button:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FfQ8a9jnAerCcnI5CsMxG%2Finstall1.png?alt=media&amp;token=71030cd7-daf2-40b8-b08e-3b98a505a550" alt=""><figcaption></figcaption></figure>

4\. The Seascape Flex services are now running and will begin to index your web archive records. Depending on the size of your archive the file indexing may take a while to complete.

You can use the links in the Control Panel to restart the services if needed, change the Seascape Flex settings, and check for product updates.

To open your archive click on the **Open Catalog** link:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FZitGLoK6f81pErWammGQ%2Finsall2.png?alt=media&amp;token=12070422-db88-4ac0-aff7-bb2d94a768e9" alt=""><figcaption></figcaption></figure>

5\. You can now enter your username and password and log in:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB37Ujd3HBpWLalSeC%2F-MlB3X835uKuGaJ21td_%2Fimage.png?alt=media\&token=60d0e1eb-c3f6-45cd-afcd-0bff9309416e)

6\. When you open Seascape Flex for the first time you will need to enter your license key to activate the product.

Copy the license key into the provided field and click **Activate License**:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB37Ujd3HBpWLalSeC%2F-MlB3_pd4Z_RCw0tVedn%2Fimage.png?alt=media\&token=011d1170-8514-43ea-b348-bdaa26ff340a)

7\. Your Seascape Flex catalog is now open.&#x20;

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FdPUcLGFx8TTUCBZ5B5X5%2Fcatalog1.png?alt=media&amp;token=b0cea6d6-85c7-4d2d-b103-7645764be19b" alt=""><figcaption></figcaption></figure>

8. Now start the indexing for all archives, by clicking on Reindex button.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FG4yuyjF2eJ8Bgs4QirD5%2Findexing.png?alt=media&amp;token=73d75332-e6b0-4c67-9fa2-2b07681c1afc" alt=""><figcaption></figcaption></figure>

9. Once the indexing is complete, you can begin to use the archives.


# Flex search

## Search on the catalog

You can now use the search box on the catalog to search **across all databases** in the catalog or you can click on the search options icon to open the dialog which allows you to search only through databases in the selected **category**, selected **design template**, from the selected **country**, **server** or **organizational unit**.

You can also narrow down your search using form and metadata filters, and select a date range for when the documents were created or modified by specific users.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2Fmn5AJwyY5aLB73u6VM4n%2FsearchCatalog1.png?alt=media&amp;token=71e52725-daaa-490d-9b91-0b24857da125" alt=""><figcaption></figcaption></figure>

The search will go through all of your **PDF records, attachments,** and **metadata**.

Seascape Flex will search your archive and display the matching results as shown in the below example.

To view the attachments and metadata for any record in the search results, simply expand the sidebar on the right of your screen, and select one of the documents in the search results.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2Fq37GOKBVXN7wvhBEl18z%2Fsearch2.png?alt=media&amp;token=06733462-8e50-4846-8709-bcc30732ef54" alt=""><figcaption></figcaption></figure>

If you wish to filter the catalog view and not search the archive's records, simply click on the dropdown in front of the search box and select **Search catalog columns.**

![Change search mode from full-text to catalog columns](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FWafUrUtwVMlDPT1l9TPW%2Fimage.png?alt=media\&token=6756bab4-d24b-4c1f-9d7e-9b2cbfb1b917)

The Search box now switches to the mode which allows you to quickly locate specific databases in the catalog.

## Search in the database

You can use the search box in the specific database to perform a full-text search on that database. It works the same as the full-text search on the catalog just without the option to filter databases.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FD07p2d3Ep4DLKVtN7ZJ1%2Fseach1.png?alt=media&amp;token=2e727e40-1f09-494a-ba8e-faa6ec6c7c39" alt=""><figcaption></figcaption></figure>

If you wish to filter the view documents and not search the archive's records, simply click on the dropdown in front of the search box and select **Search view columns**.

![Change search mode from full-text search to view columns](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FC2fEKdQi5xgTFrHR93TE%2Fimage.png?alt=media\&token=c997fa19-f877-426b-b6f6-4516e5e64022)

It is also possible to use **AND and OR operators** for search in the database (make sure to write the operators using uppercase).&#x20;

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FvtkIANheNI9chdWmFZLK%2FOR.png?alt=media&amp;token=177c1a54-aa16-461f-bed7-ee6bc575438e" alt=""><figcaption><p>Search example using OR operator</p></figcaption></figure>

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FQCwbA1mi52BukRJjKoVP%2FAND.png?alt=media&amp;token=131e24fc-a5f4-4c21-a149-cd4bf98bfca9" alt=""><figcaption><p>Search example using AND operator</p></figcaption></figure>


# Flex administration

To open the Seascape Flex administration page click on the gear icon in the top right corner.

The administration page allows you to create groups and users, or import existing groups and users from the Active Directory:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB3rc_NlBYMHdFgGJN%2F-MlB44I5uI-QGhG55pFw%2Fimage.png?alt=media\&token=bee1dac8-93dd-4f16-9a35-2892aa83b941)

To create a new group, click on the **Create Group** button.

You can always edit the settings for groups or delete groups you no longer need using the action icons shown to the right of the groups:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB3rc_NlBYMHdFgGJN%2F-MlB491vvM6KdK910i6d%2Fimage.png?alt=media\&token=2ece78e3-5644-4e6e-ae66-edda25f814d6)

Here is the Create group popup where you can enter the name and the description of the group, and assign a **user role** for all of the group's members.

There are three user roles with corresponding application permissions sets (not to be confused with Notes application roles):

* Administrator - for managing users and groups
* Archive Manager - for managing database access
* User - default permission automatically assigned to every group

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB3rc_NlBYMHdFgGJN%2F-MlB4BvsNfF4C5aepbFw%2Fimage.png?alt=media\&token=5ffda2f1-751d-4224-916a-b2a7309f532f)

To create a new user, switch to the **Users** tab and click on the **Create user** button:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlB3rc_NlBYMHdFgGJN%2F-MlB4FEc3TsKRjqloJKW%2Fimage.png?alt=media\&token=8e42bfaa-7985-4b79-8d43-9dc3a87f38f0)

To import an AD group or user, click on the **Import AD group** or **Import AD user** button and log in with your AD credentials.

After you log in, you will be provided with options for importing groups and users into Seascape Flex.

### Related content

{% content-ref url="/pages/cebnp3XRyoEnz5dPM7Tf" %}
[Connecting Flex to Active Directory](/seascape-for-notes/seascape-flex/connecting-flex-to-active-directory)
{% endcontent-ref %}


# Flex database permissions

To set access permissions for specific databases, navigate to the Home Page and click on the **Permissions** icon on any database:

The **Permissions** popup now appears where you can add user groups to the database and select the access level for each group.

You can also remove groups using the Delete icons shown next to each enabled group:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FIJFNubIYxwLEA1Up8J5U%2FPermission1.png?alt=media&amp;token=77491add-094e-4768-be71-4d1218cd9a3e" alt=""><figcaption></figcaption></figure>


# Connecting Flex to Active Directory

To connect Seascape Flex to your Active directory follow these steps:

1\. Log into Seascape Flex as an Administrator and click the gear icon in the top-right corner:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F0sHB53Pa6AxP2IZjVBcM%2Fimage.png?alt=media\&token=20591238-27a6-43d3-9334-3d2cf59ac821)

2\. Click **Import AD Group** and log in with your AD administrator credentials:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FxZVNb2keFUQY9BLUtiYo%2Fimage.png?alt=media\&token=004d12cd-d1c3-425b-ada4-a06c1a2fd10f)

3\. Next, search for the appropriate AD group and select it:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FOe8CFkFCK3fgG6dBiQLJ%2Fimage.png?alt=media\&token=ae2a780a-e164-474c-b8f7-63d36a93f4bb)

4\. Select the appropriate role for the selected group and click OK:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FLj3OefC5ay2Sq9qZIfsS%2Fimage.png?alt=media\&token=118c9721-9ad3-437f-a1ed-23001e1c1706)

5\. Your AD group has now been added to the systems and the user from the selected group can begin to log into Seascape Flex using their AD credentials:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2Fpe8x6HIxvfPVRUHn0CN1%2Fimage.png?alt=media\&token=b7723810-19fd-464d-91e6-caeacc1cd0d6)

{% hint style="info" %}
When you import an AD group into Seascape Flex no user licenses will be consumed. It is only when a user belonging to an imported group logs into Seascape Flex for the first time that one user license will be consumed.
{% endhint %}


# Enabling HTTPS on Seascape Flex server

The Seascape Flex server is hosted using Kestrel, and the recommended way to make Kestrel work with HTTPS is by configuring the IIS to work as a reverse proxy.

To enable your IIS server to work as a reverse proxy for Seascape Flex follow these instructions:

1\. Install the [Application Request Routing module](https://www.iis.net/downloads/microsoft/application-request-routing) in IIS:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FhbvnW9FUnEbZCyl3EDLN%2Fimage.png?alt=media\&token=4fbfd619-2492-4097-a0c4-a2741b776267)

2\. Once the module installed, right-click **Sites**, and click **Add Website**:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FMRCSn0N4WDBaV1R7xeZV%2Fimage.png?alt=media\&token=8ad01645-4b6c-4000-9b12-86f028f42ff9)

3\. In the Add Website popup select HTTPS in the Binding section and assign a port (e.g. port 445).

You must also select an **SSL certificate** to use, and select a **Physical path** folder (it can be an empty folder).

When you're done click OK to save your changes:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FS1DP4cF4BXULlcGWG3A5%2Fimage.png?alt=media\&token=469cb6a8-3873-46e5-9dc4-ec07bafbff10)

4\. Select the new site you created and double-click the **URL Rewrite** icon:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FX3XF9SNW8TxzvjaT7IQC%2Fimage.png?alt=media\&token=5f1b28fb-6461-4b30-a95e-91981fcdd287)

5\. In the URL Rewrite window click **Add rule**:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FsA0zWYzWoTJi8H14aTe7%2Fimage.png?alt=media\&token=a88e82a6-b85c-46f9-855c-94fc29756622)

6\. A popup will appear as shown in the below example. Click the **Reverse Proxy** icon in the popup:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FVGjXfYbQMIYJDcTwzLkM%2Fimage.png?alt=media\&token=68ae00df-f7ea-479e-9819-0bc696c048fb)

7\. A new popup now appears as shown in the below example.

Now enter your server name or the IP address where Seascape Flex is hosted (by default that will be **localhost:7500**):

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FU51D0X0WbEEYbcSaPPj8%2Fimage.png?alt=media\&token=7a33473c-49ae-48ce-a03e-a01d84c50915)

8\. Click OK to exit all popups and save your changes.

Your IIS server is now ready to start accepting HTTPS requests.

IIS will handle the HTTPS requests normally and then forward them to Kestrel in the background.


# Security

## Summary

We are aware of the [Apache Log4j 2](https://logging.apache.org/log4j/2.x/) vulnerability, referred to as "Log4Shell".

Seascape Flex uses Elasticsearch OSS version 7.16.3 (or newer), which is **NOT affected** by the Apache Log4j vulnerability ([CVE-2021-44228 and CVE-2021-45046](https://logging.apache.org/log4j/2.x/security.html)).

## More information

A high severity vulnerability ([CVE-2021-44228](https://logging.apache.org/log4j/2.x/security.html)) impacting multiple versions of the Apache Log4j 2 utility was disclosed publicly via the project’s GitHub on December 9, 2021. The vulnerability impacts Apache Log4j 2 versions 2.0 to 2.14.1.

> Elasticsearch, Logstash 7.16.3 and 6.8.23 are released, which upgrade log4j to 2.17.1. By default, Elasticsearch and Logstash have no known vulnerabilities to CVE-2021-44832.

[Apache Log4j2 Remote Code Execution (RCE) Vulnerability - CVE-2021-44228 - ESA-2021-31](https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476)


# Adding new databases to Flex

To add a new database to your Flex server, copy the database folder from your new web archive into the Seascape Flex archive.

In the below example, we show three database folders on the Seascape Flex server. Each folder is named using the Replica ID of the source Notes database:

&#x20;

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2Fgb8OmVpkNUdCOusEVhMZ%2Fimage.png?alt=media\&token=9a49584f-45d2-4889-afb9-315f483a68c1)

To add an additional database, simply copy the Replica ID folder from the new web archive you created and paste it in the Seascape Flex archive:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FuSmWGhZuejzimUasESqW%2Fimage.png?alt=media\&token=54b5e657-74fd-4818-9148-9de86d7aaf70)

After the new folder has been added, open the Seascape Flex control panel and click **Update archives**.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F2ahDUlk4FftW4sfzGcwo%2FupdArchives.png?alt=media&amp;token=cbede25b-db1f-4e55-82f1-165c13ccc443" alt=""><figcaption></figcaption></figure>

Next, a new window will appear showing our Seascape viewer Updater tool.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FSd5zWFnKpSgccHt33lps%2FsscViwerUpdater.png?alt=media&amp;token=15ddb413-e6b2-458e-a207-ecea042cce32" alt=""><figcaption></figcaption></figure>

Choose the root folder of your archives, and click on **Update** button.

Once the update is completed, and the new archive is indexed, it will be connected with the Flex design elements such as the advanced search dialog and others.&#x20;

{% hint style="info" %}
you will need to restart the Elastic search and Flex services, for the indexing to commence.
{% endhint %}


# Audit log

The audit log shows details about who accessed what and when in the Seascape Flex server.

By default, the audit is disabled. To enable it, you must open the "appsettings.json" file in your Seascape Flex directory and change the "EnableAudit" variable to true.

Once you have made the necessary changes, you will need to **restart the Seascape Flex server**.

{% hint style="info" %}
Only the admin user role has access to the audit log.
{% endhint %}

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F3xKdrPnVeuall9Sf9M5D%2Fa1.png?alt=media&amp;token=7f17afc1-6fad-454c-a1ed-0ebf321f245c" alt=""><figcaption></figcaption></figure>

Once logged in as admin, navigate to the settings in the top right corner of Flex:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FWeGExNw60a19wDQ1yCR6%2Fa2.png?alt=media&amp;token=65aaf177-d20c-40a6-a953-0f55a8c70de6" alt=""><figcaption></figcaption></figure>

Next click on the 3rd tab in the view, "Audit".&#x20;

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FDs9qSb7IlVrdcoCpNFOz%2Fa3.png?alt=media&amp;token=4a3c22bc-6768-4da5-910b-51cf41275d79" alt=""><figcaption></figcaption></figure>

There is an option to **export the audit log** by clicking on the "Export" button.&#x20;

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FCLXB5pQQJODde0z3y8jL%2Fa5.png?alt=media&amp;token=2b249d19-92ca-4628-ba71-c0688608e0f4" alt=""><figcaption></figcaption></figure>

The audit log is exported into a **csv** file:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2Fg9AbTAniBFA09ZivHXgK%2Fa4.png?alt=media&amp;token=cc1a2f02-9d42-41ac-b272-5c2a711ddc6f" alt=""><figcaption></figcaption></figure>

To **delete** and clear the audit log, click on the rubbish bin icon on the right hand side:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FG3T5FiMGm84d5PrprRNd%2Fa6.png?alt=media&amp;token=f1cfec49-9ab1-491c-9961-8d4f9b255a03" alt=""><figcaption></figcaption></figure>


# Updating existing archives

Updating Seascape web viewer version for all existing archives

Open the Seascape Flex control panel and click **Update archives**.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F2ahDUlk4FftW4sfzGcwo%2FupdArchives.png?alt=media&amp;token=cbede25b-db1f-4e55-82f1-165c13ccc443" alt=""><figcaption></figcaption></figure>

Next, a new window will appear showing our Seascape viewer Updater tool.

Choose the root folder of your archives, and click on **Update** button.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FgjFmS8zXcVmgGuspT9l4%2FupdatingArch.png?alt=media&amp;token=857d28dd-94c8-4a9f-871c-502f747d05ed" alt=""><figcaption></figcaption></figure>

Once the update is complete, all existing archives will be updated to include the latest versions of the Flex design elements and the Seascape viewer.

{% hint style="info" %}
For the changes to take affect, you will need to restart the Elastic search and Flex services
{% endhint %}

Description of the different options:

* **Update catalog only** - If you select the "Update catalog only" option, only the catalog page will be updated. Otherwise the Archive Updater will update both the catalog page and every database in the archive.
* **Force update** - It will force an update for the catalog page and every database in the archive.


# Flex FAQ


# Re-indexing archives

Re-indexing specific archives

If you need to re-index certain archives, you can do so by navigating to the Flex **catalog** page.

Next, click on the **reindex icon** for the specific archive. The status "**Indexing documents**" will indicate it's in progress.

Once indexing is complete the status will change to "**Ready**"

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FHiJBLU1Aqi1EKTAworee%2FreindexArch.png?alt=media&amp;token=4986f0ba-6a88-4bdd-9886-431f7bb1bf3e" alt=""><figcaption></figcaption></figure>


# Seascape settings


# General settings

The **General Settings** allow you to configure the general application settings and functions. These settings are applied to all application exports that you run.

You can find the **General Settings** tab on the **Settings** page in the Seascape database:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBDZGFJ5JnhmIMdGVK%2F-MlBEUpoXcd9MSd6Yjew%2Fimage.png?alt=media\&token=d074e4e0-5fc5-4319-99c2-2806e00cc319)

Here are the descriptions of the available settings.

### Restrict users to export only specific databases

If Seascape is being deployed from a server, you may optionally restrict selected users so that they are only allowed to export specific databases.

When the restriction is enabled, you can select the servers that Seascape will be able to access, and for each database listed on the selected server(s) you may select specific users who are allowed to export them.

In order to set up the database export restrictions, use the **Click Here** link to open the restrictions settings.

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBDZGFJ5JnhmIMdGVK%2F-MlBEciyuvz5J5WIar0a%2Fimage.png?alt=media\&token=f05ac91e-2a81-47fd-804a-ecf509419ffd)

You will now see a list of all the databases found on the selected server(s), as shown in this screenshot:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBDZGFJ5JnhmIMdGVK%2F-MlBEfL3LCFp3ezYHMgv%2Fimage.png?alt=media\&token=2d8c33d9-7b4c-4522-812b-00ece1046cf2)

Simply select one or more databases, and then select the users who are allowed to export the database(s):

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBDZGFJ5JnhmIMdGVK%2F-MlBEkLog5VTEf_j8Z4G%2Fimage.png?alt=media\&token=6cd7c942-0ba9-4a73-9a86-d6a810b1f057)

If no users are selected for a given database, then all users with access to Seascape will be able to export such a database.

To enable the users to export databases stored on their local workstations, select the **"Additionally, allow exporting local databases"** option.

### Log level

Select the level of information that will be logged in the history log for all of your exports.

A description of each selected log level is shown below the **Log level** menu:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBDZGFJ5JnhmIMdGVK%2F-MlBEtW6876twxLlWh4Q%2Fimage.png?alt=media\&token=1d9bb5f0-a251-4612-bf35-5afab939b9ae)

### Enable console logging

Use this option to enable or disable the console logging:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBDZGFJ5JnhmIMdGVK%2F-MlBF-Pl9Hz7Z0JgzmGG%2Fimage.png?alt=media\&token=c04c0484-cac0-4c4a-91c8-8ea3613efbcc)

Console logging is primarily use to troubleshoot any potential issues and it should be disabled in normal operation to enable better performances.

### Enable built-in progress bar

Use this option to enable or disable the progress bar.

If you are using an older version of Lotus Notes (R6.5 or R7) it is recommended to disable the progress bar and use the unresponsive progress bar instead.


# Export settings

The **Export Settings** enable you to configure the ways in which the different types of archives will be created.

You can find the export settings tab on the **Settings page** in your Seascape database.

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBFEJbuVnKzfeSA5cK%2F-MlBFMTeOfvYU3q6jo3h%2Fimage.png?alt=media\&token=32e9df3e-289f-4835-ae9d-caefaad5ba1a)

You can create and save multiple different export configurations. The configurations can then be selected in the **export settings dropdown list** when you run your exports:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBFEJbuVnKzfeSA5cK%2F-MlBGcQbhu6mUpfvIiYS%2Fimage.png?alt=media\&token=14da6cdd-b46a-4f54-b8d0-6e77507ff110)

To create a new export configuration lick **New export settings**:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBFEJbuVnKzfeSA5cK%2F-MlBGi9_isXJF9RoTsk5%2Fimage.png?alt=media\&token=3b82b277-f21b-4e65-8bd8-0a543a2792d8)

Next, select the archive type (Web Archive, SharePoint, or Extract to Disk), configure your export settings, and save the changes.

Here is an example of the **Web Archive** export settings page:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FEjvfHfS9yX7fvzHZG7Bx%2Fimage.png?alt=media\&token=223e65c8-7fd6-41fc-81d6-29f288dc5355)

The **SharePoint** and the **Export to Disk** export settings also come with an additional option that allows you to configure the PDF file naming rules, using Notes formulas:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FlGYhmhO2GBdDpEx7cDO8%2Fexport33.png?alt=media\&token=bc4627d9-c357-4570-b104-929cacd693a9)

**Note:** If you choose to convert attachments to PDF, then you must also have MS Office installed on the same workstation on which Seascape is running.

The **Advanced settings** provide additional options for creation of PDF or metadata files:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBFEJbuVnKzfeSA5cK%2F-MlBGycIczbm9V_bvBpW%2Fimage.png?alt=media\&token=8197a66d-e9bc-41a1-893a-8a2c3755d6f4)

* **Completely disable PDF conversion** - The PDF files will not be created, but the metadata and attachments will be exported normally
* **Do not export document metadata file** - The XML files will not be generated
* **Force PDF conversion even if PDF document already exists** - PDF files will be generated for every Notes document, regardless of if the same document already exists in the destination folder. If left unchecked, Seascape will only overwrite the existing PDF files with a new version in cases the date/time of when the Notes document was last modified is newer than the date/time of the PDF file creation.


# PDF settings

The **PDF Settings** are used to control how the PDF files will be generated.

You can create one or more configuration documents as per your needs. In the below example, there are four configuration documents called eBook, Press, Print and Screen.

To create a new configuration document click on the **New PDF Settings** link and then edit and save the configuration document.

To edit an existing configuration document, open the document from the provided list, edit the settings, and save the changes.

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FEzB9PTlk7etl8QKWIKD4%2FpdfSettings1.PNG?alt=media\&token=33c68b7e-8906-4a3c-9c17-8405531a25eb)

The **PDF Settings** configuration document consists of several tabs which contain settings that can be edited:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBH-vj1p910CIp_u4W%2F-MlBHEFybv54Y5IyO5Fs%2Fimage.png?alt=media\&token=7c0860d8-37c9-4298-b333-5fd496c8c6fb)

Here is a description of each setting tab:

* **General**: Provides settings for managing image compression and generating PDF/A compliant files.
* **Page Setup**: Provides settings for managing PDF page size, orientation and margins.
* **Fonts**: Provides settings for managing font embedding, path to system font directory and web safe fonts.
* **Header/Footer**: Provides settings for managing PDF headers and footers.
* **Watermark**: Provides a setting to enable/disable PDF watermark printing.
* **Attachments:** Provides settings to enable/disable the export of inline images and zip attachments
* **Security**: Provides settings for managing PDF security (including PDF password protection, encryption level and PDF editing/copying/printing permissions)


# PDF/A format description

PDF/A is an [ISO](https://en.wikipedia.org/wiki/International_Organization_for_Standardization)-standardized version of the Portable Document Format (PDF) specialized for the digital preservation of electronic documents.

PDF/A differs from PDF by prohibiting features ill-suited to long-term archiving, such as [font](https://en.wikipedia.org/wiki/Font) linking (as opposed to [font embedding](https://en.wikipedia.org/wiki/Font_embedding)).

## Description <a href="#description" id="description"></a>

The PDF/A standard identifies a "profile" for electronic documents that ensures the documents can be reproduced exactly the same way using various software in years to come.

A key element to this reproducibility is the requirement for PDF/A documents to be 100% self-contained. All of the information necessary for displaying the document in the same manner is embedded in the file.

This includes, but is not limited to, all content (text, raster images and vector graphics), fonts, and color information.

A PDF/A document is not permitted to be reliant on information from external sources (e.g. font programs and data streams), but may include annotations (e.g. hypertext links) that link to external documents. Other key elements to PDF/A conformance include:

* Audio and video content is forbidden.
* ​[JavaScript](https://en.wikipedia.org/wiki/JavaScript) and executable file launches are forbidden. All fonts must be embedded and also must be legally embeddable for unlimited, universal rendering. This also applies to the so-called [PostScript](https://en.wikipedia.org/wiki/PostScript) standard fonts such as [Times](https://en.wikipedia.org/wiki/Times_Roman) or [Helvetica](https://en.wikipedia.org/wiki/Helvetica).
* Colorspaces specified in a device-independent manner.
* Encryption is forbidden.
* Use of standards-based metadata is required.
* External content references are forbidden.
* ​[LZW](https://en.wikipedia.org/wiki/Lempel%E2%80%93Ziv%E2%80%93Welch) is forbidden due to intellectual property constraints. [JPEG2000](https://en.wikipedia.org/wiki/JPEG2000) image compression models is not allowed in PDF/A-1 (based on PDF 1.4), as it was first introduced in PDF 1.5. JPEG 2000 compression is allowed in PDF/A-2 and PDF/A-3.
* Transparent objects and layers (Optional Content Groups) are forbidden in PDF/A-1, but are allowed in PDF/A-2.
* Provisions for digital signatures in accordance with the [PAdES](https://en.wikipedia.org/wiki/PAdES) (PDF Advanced Electronic Signatures) standard are supported in PDF/A-2.
* Embedded files are forbidden in PDF/A-1, but PDF/A-2 allows embedding of PDF/A files, facilitating the archiving of sets of PDF/A documents in a single file. PDF/A-3 allows embedding of any file format such as XML, CAD and others into PDF/A documents.
* The use of XML-based [XML Forms Architecture](https://en.wikipedia.org/wiki/XML_Forms_Architecture) (XFA) forms is forbidden in PDF/A. (XFA form data may be preserved in a PDF/A-2 file by moving from XFA key to the Names tree that itself is the value of the XFAResources key of the Names dictionary of the document catalog dictionary.)
* Interactive PDF forms - Form fields must have an appearance dictionary associated with the field's data. The appearance dictionary shall be used when rendering the field.

## PDF/A support in Seascape <a href="#support" id="support"></a>

SWING Seascape supports multiple PDF/A output formats, those include:

* PDF/A-1b
* PDF/A-2b
* PDF/A-3b

{% hint style="info" %}
Notes document links remain functional in all three supported PDF/A formats, however the attachment embedding feature works only with PDF/A-3b format.
{% endhint %}

## **PDF/A-1b** <a href="#pdf-a-1-b" id="pdf-a-1-b"></a>

A-1b conformance is the minimum requirement for PDF/A compliance. The focus here is on reliable rendered visual appearance. PDF/A-1b files must include:

* Embedded fonts
* Device-independent color
* Extensible Metadata Platform (XMP) metadata

PDF/A-1b files can not include:

* Encryption
* LZW Compression
* Embedded files
* External content references
* PDF Transparency
* Multi-media
* JavaScript

## **PDF/A-2b** <a href="#pdf-a-2-b" id="pdf-a-2-b"></a>

PDF/A-2b is the extension of the PDF/A1b conformance. Part 2 of the PDF/A Standard is based on a PDF 1.7 (ISO 32000-1), rather than PDF 1.4 and offers a number of new features:

* ​[JPEG2000](https://en.wikipedia.org/wiki/JPEG2000) image compression.
* Support for transparency effects and layers.
* Embedding of OpenType font.
* Provisions for digital signatures in accordance with the PDF Advanced Electronic Signatures – PAdES standard.
* Embedding PDF/A files to facilitate archiving of sets of documents with a single file.

## **PDF/A-3b** <a href="#pdf-a-3-b" id="pdf-a-3-b"></a>

PDF/A-3 (ISO 19005-3:2012. Part 3) differs from PDF/A-2 in only one regard - it allows embedding of arbitrary file formats (such as XML, CSV, CAD, word-processing documents, spreadsheet documents and others) into PDF/A conforming documents.

## References <a href="#references" id="references"></a>

1\. Wikipedia - <https://en.wikipedia.org/wiki/PDF/A>​


# Alternate forms

The **Alternate Forms** feature provides a way to generate the PDF files using an alternate Notes form which has been optimized for PDF rendering.

Using alternate forms is recommended when the default Notes form is not converted to PDF file in a desired way, or when you wish to show or hide specific information in the generated PDF files.

To deploy an alternate Notes form you will first need to design the form in Domino Designer. It is advised to store alternate forms in source database, as it is the safer option.

When storing alternate forms in Seascape database, all dependencies (subforms, shared fields) must also be available in Seascape database. In case some of the subforms included is missing, an error will occur.

Then you will need to add a new setting in Seascape and specify a rule for when the alternate form should be used instead of the default form.

To create a new alternate form setting click on the **New alternate form settings** link and then edit the configuration document.

To edit an existing alternate form setting, open the configuration document from the provided list, and then edit and save the changes:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FGfRSOjAGI28bahnQogkq%2FalternateForms1.PNG?alt=media\&token=7d212aae-2448-4186-9a2b-d9b0569ab76b)

Below is a screenshot of the alternate forms setting options:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FrGG789l9dF5wf4E8WPIl%2FalternateForms2.PNG?alt=media\&token=890d5a3d-3fcd-4f4a-be27-7c85449e37c2)


# Folder formulas

To create a new folder formula (for creating custom folder structures in SharePoint or disk archives) click the **New Folder Formula** link:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBHXlxxRgksYgRIgaW%2F-MlBHf957L5oWqPn-uKq%2Fimage.png?alt=media\&token=8a57d52d-78ec-4de4-8e22-c7bcacdcc518)

Folder formulas defined on this page will appear in the export settings section when you're exporting your databases, where you can simply select an appropriate formula for each archiving job:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlKhDP9iCTkt08yeqUY%2F-MlKhLZbUGWiu7ai8sef%2Fimage.png?alt=media\&token=664c99fa-0876-4ef6-869f-8919b59808ff)


# Product limitations

SWING Seascape supports most of the standard Lotus Notes design elements, however there are a few exceptions.

The following is a list of the design elements which are currently not supported:

* Layout regions
* Custom date formats
* Custom currency formats
* Custom embedded view column icons
* Pass-Thru HTML on Lotus Notes forms (for a potential workaround see [How to export HTML fields](/seascape-for-notes/faq/how-to-export-html-fields))
* Hide-when formulas with User Roles are evaluated only when the database is exported from the server


# FAQ


# How to disable HTTP stream

Disabling the HTTP stream can greatly improve the conversion speeds for documents that link to a lot of external resources (for example images and CSS files from old newsletter emails).

A grey image placeholder will be displayed in the place of the external image.

To disable the HTTP stream navigate to **Settings > PDF settings** in your Seascape database and open the settings configuration document you are using for PDF conversions:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlV7a79SRmG0EKSkCsN%2F-MlV8XSTg2a3RDYqZmYb%2Fimage.png?alt=media\&token=7a1ea149-ae04-4fae-9ed5-144d4adb5360)

Now change the **Enable HTTP Stream** option to **No** and save your settings:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlV7a79SRmG0EKSkCsN%2F-MlV8gPfB5fnkOEA6-ff%2Fimage.png?alt=media\&token=8adcdaf8-b813-4cae-a351-76a12eb64438)

{% hint style="info" %}
If you don't want to completely disable the HTTP stream it is also possible to set a timeout by setting the **HTTP timeout** option on the **General** tab to desired number of seconds (greater than zero).
{% endhint %}


# How can I change styles in the Web Archive?

To change the styles in your Web Archives, edit the **custom-root.css** file in the archive's CSS folder. The **custom-root.css** file applies to all databases in the catalog.

If you wish to change the styles of an individual archive, you can edit the **custom-db.css** file in the CSS folder of that particular archive.

If needed, you can also edit the **catalog.html** and the **index.html** files to change the appearance of the database and web viewer components.

### Change styles for all future archives

If you are creating many separate archives, you can also modify the HTML and CSS templates in the Seascape database, so that you don't have to edit them later after the archives have been created.

{% hint style="info" %}
Please note that these changes will be overwritten when you upgrade to a newer version of Seascape. Please keep a backup of your custom CSS files so you can reapply them after the upgrade.
{% endhint %}

#### Seascape Viewer zip

The Seascape Viewer zip file is included with Seascape and contains Web Viewer files. Mentioned CSS files, **custom-root.css** and **custom-db.css**, are in the css subfolder of the zip file. You can modify these files, save the changes in the zip.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FEKuumO1tAq5648HYaNv3%2Fimage.png?alt=media&amp;token=ec94cf71-f43b-4f4e-ab7e-b09f5d118c3e" alt=""><figcaption></figcaption></figure>

If you are using the Notes JVM for your exports, you need to update the Seascape Viewer zip file in the **SeascapeResources** form. If you are using the External JVM, you need to update the Seascape Viewer zip file in the **resources** folder on your disk. Newer versions of Seascape use the External JVM by default. You can verify which JVM is in use in your Seascape General settings.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FNdMnPleTWs3zyjnjruJr%2Fimage.png?alt=media&amp;token=1eca07f1-fd94-4922-a849-d8a4b35d4586" alt=""><figcaption></figcaption></figure>

#### Notes JVM: Modify SeascapeResourcesForm

If you are using Notes JVM, open the Seascape database in Domino Designer and locate the **SeascapeResources** form.

On top of the form, you will see the file seascape-viewer-XX.XX.XXX.zip.&#x20;

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FT2POVaQCChJzOfuF99aP%2Fimage.png?alt=media&amp;token=2a9a74f1-935c-4879-9592-992fffff2403" alt=""><figcaption></figcaption></figure>

Replace this zip file in the **SeascapeResources** form with your modified version.&#x20;

#### External JVM: resources folder

If you are using the External JVM, you need to replace the Seascape Viewer zip file in your \<Notes Data>\SwSSC\\\<X.XX.XX>\resources folder with your modified version.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F9uaG7KcAf9jf1jPEWfUc%2Fimage.png?alt=media&amp;token=1c24d330-46ca-4410-a1f4-7896423341ea" alt=""><figcaption></figcaption></figure>


# Which view/folder types are supported?

SWING Seascape supports all view/folder types except "**Shared, desktop private on first use**".

![](https://gblobscdn.gitbook.com/assets%2F-MlCAurE6RSGoCmtmAET%2F-MlFpxz73O59EQ-bKd8x%2F-MlFq9aOW3pKGfhNC1iE%2Fimage.png?alt=media\&token=9369937e-82dc-41b7-8509-ae15bff4bf24)


# How to Change the default view for the web-archive?

To change the default view of your web archive, open the "**views-list.js**" file in your text editor. The file is found in the "ROOT FOLDER\REPLICAID\db" folder:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FHeNN352PABVgHNVqItLX%2FviewsList_JSON.png?alt=media\&token=9b74df3b-08ea-451b-91ea-ec9ef8cc00da)

Next, locate the view that is currently set as the default view, and change its "is\_default" key to "false".

Finally, locate the view that you would like to set as the new default view, and change its "is\_default" key to "true".

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FFqkeKZULCPrh8c8rQ4Pf%2FdefaultView.png?alt=media\&token=cd98d1ad-a250-4f67-aa9b-f6a78236281a)

After you save the changes the new view you selected will be opened automatically when the archive is launched in the browser.


# What is the SWING Seascape installation footprint?

This article lists the files that are created or modified on the server system during the installation of SWING Seascape and its usage.

Once SWING Seascape is installed on the system and the first conversion is initiated then SWING Seascape will:

* Create a SwPDFC folder on the system. This folder is located at "\Data\SwPDFC\\" (typically C:\Program Files\IBM\Lotus\Notes\Data or C:\Lotus\Notes\Data if using the product on a local workstation) or at "\Data\SwPDFC\\" (if using the product on a Domino server). Here are some additional notes about the SwPDFC folder:
  * The SwPDFC folder contains SWING PDF Converter Java resources (.jar files) which contain the software logic together with dependencies
  * The folder path for the Java resources is "\Data\SwPDFC\java\ver\[x.xx.xxx]"
  * The SwPDFC folder also contains a temporary folder with the unique name for each document conversion and which is used to store temporary resources, such as extracted Notes document attachments, image resources, etc... The folder path is "\Data\SwPDFC\java". This folder gets automatically deleted after the conversion job is completed.\\
* Create a SwSSC folder on the system. This folder is located at "\Data\SwSSC\\" (typically C:\Program Files\IBM\Lotus\Notes\Data or C:\Lotus\Notes\Data if using the product on a local workstation) or at "\Data\SwSSC\\" (if using the product on a Domino server). The SwSSC folder contains additional Java resources (.jar files) needed to run exports.&#x20;
* Create an external JVM in "C:\Users\USERNAME\AppData\Local\SWING Seascape"
* Create the SPUploader sub-folder in the SwPDFC folder. This folder stores the "Seascape-SharepointUploader.exe" file which is used with the SharePoint export method to upload PDF files, metadata, and attachments into a SharePoint site. The SPUploader folder also includes the Log and Repositories subfolders that store the job information and settings, including a session.json file to store session data.
* Create a swllrend.dll file in "" (only if the low level rendering option has been enabled in PDF settings). This DLL file is used for low level document rendering and creating better quality PDFs.
* Write entries to notes.ini file. Here is a list of entries:

```
SWJ0
SWJ1
SWJ2
.
.
JavaMaxHeapSize,
JavaMinHeapSize
$SwPDFJavaDir
$SwPDFJarVer
$SwPDFDoc
$swFileDlgDirectory
$swPDFAutoFileOpen
$SwPDFcLVSO
$SwPDFProgressCount
$swPDFAutoFolderOpen
$SwPDFFileDlg
$SwPDFCreatorServer
$SwPDFCreatorDB
$SwPDFDllVer
$SwPDFDb
$SwPDFServer
$SwPDFForm
$SwPDFViewTitle
$SwPDFContext
```

{% hint style="info" %}
Your notes.ini file might not contain all entries listed here.
{% endhint %}

* Create a temporary PDF document (or documents) once the conversion job is completed. The documents will be stored in the Windows temp folder before being saved to a desired location. Folder path: C:\Users\\\AppData\Local\Temp


# PDF filename Unicode compliance tips

SWING Seascape supports Unicode compliant file naming from version 5.6 on MS Windows.

This compliance includes toolbar icon UI, LotusScript API and Java API.

If computed PDF file names are not readable on your operating system (shown as rectangles, question marks or any other generic symbol) like on image below then most common reason for this is wrong Windows localization.

Example: Far eastern symbols shown on European Windows localization:

<div align="center"><figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FddNnnOfmPjoStZXaXczW%2Fsymbol-no-font.png?alt=media&amp;token=26ac4759-e7b9-41f9-86b5-29abe8754721" alt=""><figcaption></figcaption></figure></div>

Incorrect localization settings can also result in the same symbols appearing in Notes fields and forms.

If you for example work in USA and receive a Notes database from Japan, then symbols in Japanese Database might not be visible on your computer.

Localization should be changed to Japanese, this will force MS Windows to install all required fonts and resources for Japanese language.

Once this is done, localization can be safely reverted to US, without loss of Japanese resources.

[Here's the link for help page that describes how to change localization.](https://www.tenforums.com/tutorials/68106-change-country-region-home-location-windows-10-a.html)​


# How to enable PDF search in Windows (64-bit)

Modern operating systems have the PDF search functionality already built-in, so you won't need a third party tool to search PDFs - the operating system will do it for you. However if you are not able to search the PDF files, you may need to edit your Windows settings and/or install the iFilter plug-in.

The iFilter plug-in usually gets automatically installed when you install a PDF reader software (such as Adobe Reader) on 32-bit Windows. However the iFilter plug-in does not install automatically on any version of 64-bit Windows.

To find out what version of Windows is installed on your workstation, click Start, right-click Computer, click Properties and see the System type information (an example screenshot is shown below).

![](https://gblobscdn.gitbook.com/assets%2F-MlCAurE6RSGoCmtmAET%2F-MlFjQ-sIbcsxR3tQYnL%2F-MlFjepEpL3w4Uj2sVi6%2Fimage.png?alt=media\&token=1b4b8af0-1ed8-4024-a114-6499492f7c9b)

If you have a 64-bit version of Windows installed, you would now have to go to the Control Panel, open Indexing Options and then click the Advanced button. Then on the File Types tab check that "pdf" is shown on the list. If Filter Description states "Registred IFilter is not found" you will need to install the iFilter plug-in manually. At the moment of writing this article the latest version of iFilter for 64-bit Windows is 11. You can download it from [Adobe's web site](http://www.adobe.com/support/downloads/thankyou.jsp?ftpID=5542\&fileID=5550) and install it.

![](https://gblobscdn.gitbook.com/assets%2F-MlCAurE6RSGoCmtmAET%2F-MlFjQ-sIbcsxR3tQYnL%2F-MlFjjjQ-pY4nXSiPlMn%2Fimage.png?alt=media\&token=927a7a02-391d-400c-a31a-cd07f267b6c6)

When iFilter is successfully installed the Filter Description will state "PDF filter" which means that Windows can now index PDF files. If you additionally wish to index the content of the PDF documents (and not just the document properties) you will need to un-check the "Index Properties Only" option and check "Index Properties and File Contents" option instead (see below screenshot).

![](https://gblobscdn.gitbook.com/assets%2F-MlCAurE6RSGoCmtmAET%2F-MlFjQ-sIbcsxR3tQYnL%2F-MlFjo0LqbKGWfDUEni4%2Fimage.png?alt=media\&token=a1ef606e-8ac5-4f63-a273-40da49f011e6)

When all of this is done it is also a good idea to rebuild the index in order to make sure that the existing PDF files are indexed correctly. Go back to Index Setting tab and hit the Rebuild button.

![](https://gblobscdn.gitbook.com/assets%2F-MlCAurE6RSGoCmtmAET%2F-MlFjQ-sIbcsxR3tQYnL%2F-MlFjsHcdqbDZq6pkHEn%2Fimage.png?alt=media\&token=8911838a-61c9-4df8-92f7-d772469e0a1a)

**Note:** In order to search PDF attachments as well, an iFilter should be installed which supports indexing of PDF attachments. Several commercial alternatives are available on the web.

Learn more: [Lotus Notes](https://www.swingsoftware.com/blog/lotus-notes-alternatives) [backup](https://www.swingsoftware.com/blog/lotus-notes-backup) and [PDF Converter for Notes](https://www.swingsoftware.com/pdf-converter-for-notes).


# Do I need to have the latest JRE (Java Runtime Environment) installed on my Workstation?

Yes, but only if you are using Notes/Domino 6.5. For newer versions (R7 and above) it is **not** required.

Notes/Domino R6.5 incorporates an older version of Java (1.3) which does not have all the required functionality to allow SWING Seascape to run correctly and efficiently. So the latest JRE should be obtained and installed on machines that will be using SWING Seascape.

You can get the latest release from here : <http://www.java.com/en/download/manual.jsp>​


# How are licenses consumed?

Seascape licenses are issued for a specific number of workstations and databases.

For example, a **3 Workstation / 150 database** license allows you to install Seascape on up to three different workstations, and export a maximum of 150 databases.

Each time you activate Seascape on a new workstation, a single workstation license seat is taken (eg. 1 of 3) by registering the name of the workstation in an online registration database.

Similarly, each time you begin to export a database, a single database seat is taken (eg. 1 of 150) by registering the replica ID of the database in the online registration database.

Once the replica ID of a database has been registered, you may process that same database any number of times without consuming any additional license seats.&#x20;

Also you can distribute the workloads across different workstations as you prefer. For example, you could export 40 databases from the first workstation, 80 from the second, and 30 from the third workstation.

You can check on your current license usage from the **About** page in your Seascape database:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBHlw_h8oBDMW9U0pd%2F-MlBHuiosaKgmm2xiqt2%2Fimage.png?alt=media\&token=3e309ccf-2a00-415d-8c88-4973da231024)

Note that the **About** page does not refresh automatically. To view the latest license usage counts simply reactivate your license using the **Change License** button. Once the license has been reactivated the page will refresh to show the current license usage.&#x20;

{% hint style="info" %}
After a workstation license has been consumed, you may re-install Seascape on such a workstation multiple times without consuming a new license seat. Similarly, after a database license has been consumed, you can process the registered database multiple times without taking up another license seat.
{% endhint %}


# How can I access attachments in the Web Archive?

When you create a Web Archive, your Notes attachments are saved both in the generated PDF file and in the content/attachments subfolder.

To access the attachments that are embedded in a PDF file, download the PDF file from your archive and open it in Adobe Acrobat.

You can then open the attachments from the Attachment pane on the left, or simply by double-clicking on the attachment icons:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBHyop4W9Jfon2zvjd%2F-MlBIDse28fJk3e70cnO%2Fimage.png?alt=media\&token=8c4745d3-218f-409a-bd68-233916b2782e)

If you disabled the Attachment embedding option in the export settings, that your attachments will be saved in the **content/attachments** subfolder of your web archive.

In this case the attachments can be accessed in two ways in the web viewer.

The first way is to simply click on the attachment icon in the PDF document you're viewing in the browser:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FiwHPvzKzBapz0pMZ9Agv%2Fimage.png?alt=media\&token=2b890c8f-5e3c-4e54-8e07-bc061d65b53d)

The second way is to expand the document properties sidebar on the right and download the attachment from the Attachments section:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBHyop4W9Jfon2zvjd%2F-MlBId-Y603Q7M9Uic1z%2Fimage.png?alt=media\&token=e2c32588-b3d4-4243-989b-7984a50e2273)

{% hint style="info" %}
To disable the attachment embedding option uncheck the following setting in your Web Archive export settings:

<img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FM7xesiZpyfzXIaU6i9cR%2Fimage.png?alt=media&amp;token=10122f2e-eaa5-4438-9c29-be1a1ab73083" alt="" data-size="original">
{% endhint %}


# How to configure PDF file naming rules

The PDF files generated using the **SharePoint** or **Extract to disk** export methods can be saved using custom naming rules.

The naming rule is applied using a simple Notes formula which combines one or more Lotus Notes fields into a single text string to be used for the file name.

Here are the instructions for setting up a custom naming rule for your PDF files.

1\. Open your Seascape database, click **Settings > Export Settings**, and open the export configuration document you would like to edit by double-clicking on it:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBIh_vpo_KmMGZsbvQ%2F-MlBIs54CMk1MxO3GGOV%2Fimage.png?alt=media\&token=b08437c6-96a8-4e93-9272-8977c39e8ff8)

2\. Enter your file naming formula in the provided field, and save your changes:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBIh_vpo_KmMGZsbvQ%2F-MlBIyBXzpPWo3fjrnry%2Fimage.png?alt=media\&token=5544021f-80ed-476b-9c92-01e980bff96a)

3\. When you start an export the next time, select the export settings you updated and the PDF files will be named according to the new rule you set up:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBIh_vpo_KmMGZsbvQ%2F-MlBJ1-ZyULrC94dvETD%2Fimage.png?alt=media\&token=a11e10e0-ccae-4faf-90e7-7bcd1d2bf85d)

### **Lotus Notes form fields**

To locate the correct names of the Notes form fields to be used in your formula, open your Lotus Notes document, then right-click on it and open the document's properties popup.

In the popup which appears open the second tab from the left. The list of available form fields that you can use will now be shown in the popup:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBIh_vpo_KmMGZsbvQ%2F-MlBJ6LxG-wVl64emddM%2Fimage.png?alt=media\&token=04a2c4e6-8ca2-4e90-9915-bba762cfae2c)

{% hint style="info" %}
It is recommended to use either "@DocumentUniqueID" or "@NoteID" in the file naming formula, as these are the only two fields that are guaranteed to be 100% unique across all Notes documents.

We recommend using @NoteID because its value is slightly shorter.
{% endhint %}

{% hint style="info" %}
If the file naming formula does not include either of these two fields (@DocumentUniqueID and @NoteID), an additional subfolder named UNID-att will be created.&#x20;

All attachments will be stored in this subfolder, ensuring that attachment links remain functional in cases where the file naming formula does not produce a 100% unique filename.
{% endhint %}

### **Notes formula examples**

Here are a few typical examples of Notes formulas which can be used in your Notes mailbox:

1\. The following formula can be used for emails to name PDF files by delivery date and time and subject, separated with underscore:

`@Text(DeliveredDate) + "_" + @Text(Subject)`

"DeliveredDate" and "Subject" are typical fields for email documents. For example, a message with subject "Re: Follow-up message" received on December 8th 2011 will be converted to PDF with following file name: **08.12.2011 19 39 31\_Re Follow-up message.pdf**

2\. In this example we removed time, so our file name contains only date and subject:

`@Text(@Date(DeliveredDate)) + "_" + @Text(Subject)`

The result: **08.12.2011\_Re Follow-up message.pdf**

3\. In this example we decided to format date differently and we included "From" field, now we can see who sent this message without opening it:

`@Text(@Year(DeliveredDate)) + "-" + @Text(@Month(DeliveredDate)) + "-" + @Text(@Day(DeliveredDate)) + "_" + @Text(Subject) + "_" + @Text(From)`

The result: **2011-12-8\_Re Follow-up <message_info@swingsoftware.com.pdf>**

4\. This example is slightly different, file name contains form name and date of the conversion:

`@Text(Form + "-" + @Text(@Year(@Today)) + "-" + @Text(@Month(@Today)) + "-" +@Text(@Day(@Today)))`

The result: **Memo-2011-12-9.pdf**

5\. \*\*\*\* In this example, the PDF files will be named simply according to their unique document ID:

`@documentuniqueid`

The result: **9900B68769EDF884C12576DD005CC16E.pdf**


# How to create a single database catalog from existing archives

To create a single database catalog from Full Archives follow these steps:

1\. Copy the archives into the same root folder

2\. Download and run the Seascape Archive Updater according to instructions in this article:

{% content-ref url="/pages/-MlAdTTqVgyB0P9o9qr3" %}
[How to update a Seascape archive](/seascape-for-notes/faq/how-to-update-a-seascape-archive)
{% endcontent-ref %}

After the Seascape Archive Updater finishes running it will both update the Full Archives to the latest version and generate a new database catalog which features all of the archives that you copied into the root folder.


# How to exceed SharePoint list view threshold

SharePoint libraries and lists come with a default limitation of 5,000 items per list (SharePoint Server 2013) or 20,000 items per list (SharePoint Server 2016 and SharePoint Server 2019).

If you need to upload a bigger number of documents than is allowed by your SharePoint threshold, you can create a new library or list and then add then add indexes to the required view columns.

If a SharePoint list column is indexed, then you will be able to upload any number of documents to SharePoint and still be able to search and sort all documents by indexed columns.

Note that the SharePoint library or list will need to be set up with column indexes before you begin uploading any of your Notes data.

For more information on adding indexes to SharePoint columns please see this article in Microsoft's knowledge base:

{% embed url="<https://support.microsoft.com/en-us/office/add-an-index-to-a-list-or-library-column-f3f00554-b7dc-44d1-a2ed-d477eac463b0>" %}


# How to export computed fields

There are 3 different types of Computed fields:

| Type of computed field | Formula calculates                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Computed               | A computed field formula calculates each time a user creates, saves, or refreshes a document. The field is not refreshed when the user opens the document, even in edit mode.                                                                                                                                                                                                                                                                      |
| Computed when composed | A computed-when-composed field formula calculates only once: when the user first creates the document. Use this type of formula in a field to preserve information about the origin of a document, such as the creation date or original author, or to create a field whose original value never changes, such as a document sequence number.                                                                                                      |
| Computed for display   | A computed-for-display field formula recalculates each time a user opens or saves a document. Use this type of formula in a field to display information that is relevant only to the immediate session, such as the current time or the results of calculations that you don't need to save. The field value exists during the current session only and is not stored. You cannot display the contents of a computed-for-display field in a view. |

“Computed” and “Computed when composed” are part of Notes backend document and therefore will be part of a XML metadata.

As for “Computed for display” fields, they are not part of the Notes backend and therefore will not be part of metadata XML either.

For “Computed for display” type fields to be included in metadata XML, custom metadata needs to be created.


# How to export hidden email folders

The Inbox and several other Notes mail-file folders are by default hidden.\
In order to include such folders in your export, click on the Show hidden settings in your folder selection window.

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBKkrucXahl3v9wI2t%2F-MlBKngB-Z0VP_M-QPXa%2Fimage.png?alt=media\&token=c20b43cd-9c4d-474f-afac-9e5ffdd3a4f3)

Your hidden mail-file folders will now be shown in the folder list and you can select them. For example, to include your Inbox in the export, select the ($Inbox) hidden folder.

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBKkrucXahl3v9wI2t%2F-MlBKr5jy2i1dN4Q4j3z%2Fimage.png?alt=media\&token=b120491c-70c6-4e9b-b8fb-6e89d89a4ec0)


# How to export mail outline

When exporting a mail file to a Full Archive, use the NotesMailOutline option under the "Views in outline" tab in order to export the standard mail file outline:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBKtfgHq9LJGmcGSD7%2F-MlBKwtgRR73Nh13wfMN%2Fimage.png?alt=media\&token=733b117d-93bf-4a5c-975b-a04a0eb9a266)

Here is an example of one such mail outline when exported to a Full Archive:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlBKtfgHq9LJGmcGSD7%2F-MlBL-TPU1d6Uw7piS8G%2Fimage.png?alt=media\&token=aa7d1a78-5891-4a83-b4db-8bd2cb6069fa)


# How to update a Seascape archive

Below are the instructions to update the Seascape web archives design to the latest version:

1\. [Download Seascape Viewer Updater](https://www.swingsoftware.com/download/dl-ssc) and run the application (you will need to have Administrator rights).&#x20;

2\. Select the folder that contains your web archive(s). Click Update and all the archives will be updated to the latest version including the archive catalog.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2Fk0qDdAK78w1KOWHPoTj5%2FsscViewerUpdater.png?alt=media&amp;token=350528d1-d965-4f0c-85ee-f864e89ff620" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If you select the "Update catalog only" option, only the catalog page will be updated. Otherwise the Archive Updater will update both the catalog page and every database in the archive.&#x20;
{% endhint %}

{% hint style="info" %}
By clicking on "Validate archives", the updater will go through all the databases in the archive, and check if they have any errors. A confirmation message will be shown.
{% endhint %}

{% hint style="info" %}
If you select the "Force Update" option, this will force the Archive Updater to update every database in the archive.
{% endhint %}


# How to export HTML fields

A Lotus Notes form may contain one or more fields with pass-thru HTML content.

By default, SWING Seascape does not render the pass-thru HTML content in PDF, and such content will appear in the PDF files as HTML code.

However a workaround is available by which the HTML fields can be rendered in PDF. Here are the steps to apply the workaround:

1. Using Domino Designer, add a new computed field to your Notes form and configure it so that it stores the HTML content of all form fields which contain pass-thru HTML. You can keep this field hidden so that your Notes form will appear same as before in the Notes client.
2. Create and run a new agent that will re-save each document in your Notes database, causing the computed field to re-evaluate itself and save all of the pass-thru HTML content. Note that the last modified date property of the Notes documents will be changed as a result of running the agent.
3. Using Domino Designer create a new form which will display the new computed field created in step 1, and hide all of the other fields that contain pass-thru HTML. The computed field must not be saved in a table. Once the form is created, save it in your Seascape database.
4. Create a [new alternate form setting](/seascape-for-notes/seascape-settings/alternate-forms) which will instruct Seascape to convert documents to PDF using the alternate form created in step 3 as opposed to the default Notes form. With the alternate form deployed in this way, Seascape will render the HTML content in the generated PDF files accurately.

{% hint style="info" %}
The workaround described above can be used only in cases where the fields with pass-thru HTML content can be recreated in an alternate form without compromising the basic structure of the document.
{% endhint %}

{% hint style="info" %}
If you need help with creating an agent to re-save the Notes documents or building the alternate Notes form please contact SWING Software's support team for assistance.
{% endhint %}


# How can I preserve non-English characters in PDF

To export non-Western characters, such as [CJK](https://en.wikipedia.org/wiki/CJK_characters) (Chinese/Japanese/Korean), Cyrillic, Indian, etc. to PDF files correctly you will need to set the **Embed all fonts** option to **Yes** in your [PDF Settings](/seascape-for-notes/seascape-settings/pdf-settings):

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F3B5pxC6aYUry8gkyoMgs%2Fimage.png?alt=media\&token=522460a3-b72d-4a29-927e-e2802169f412)

### Exporting Mixed Fonts

When there is a document with mixture of English and Chinese / Japanese / Arabic / etc.. fonts, Lotus Notes exports all those fonts as plain "Arial" font.

SWING Seascape gets the Lotus Notes document export in raw DXL and processes paragraphs one by one. In this process Seascape looks for paragraph text and its font.

Paragraph text comes LMBCS (Lotus Multi Byte Character Set) encoded. LMBCS provides region code which tells Seascape what type of string it's working with.

If there is a mixed text in the document, Seascape gets (from Lotus Notes) that only "Arial" font is used in entire document.&#x20;

The default "Arial" font does not contain all glyphs required to show international symbols in pdf document. To overcome this issue Seascape uses Adobe recommended fonts which are chosen by LMBCS region.

These fonts are not being embedded by default as they are 15MB+ in size, so that the resulting PDF documents will be 15MB+ in size which is not optimal.

### Converting Thai symbols

To convert documents with Thai symbols, one of the required fonts must be installed. Learn more:

{% content-ref url="/pages/-MlL6aDpFshqXDZohm2Y" %}
[Thai symbols not shown in PDF document](/seascape-for-notes/troubleshooting/general-issues/thai-symbols-not-shown-in-pdf-document)
{% endcontent-ref %}


# How to open .zip attachments in Adobe Reader

Adobe Reader does not allow opening .zip file attachments directly from Adobe Reader. Attachments represent a potential security risk because they can contain malicious content, open other dangerous files, or launch applications. However, if you need this option there is a workaround to enable it by editing registry data:

1. Click Start and find Run application
2. In the Open box type "regedit" and click OK to open Registry Editor
3. In Registry Editor navigate to the following registry key:\
   HKEY\_LOCAL\_MACHINE\software\policies\adobe\AdobeAcrobat\DC\FeatureLockDown\cDefaultLaunchAttachmentPerms
4. Double-click on sBuiltInPermList
5. In the Value data field, locate the .zip file type extension
6. Change the number directly after the .zip file type extension to 1 and click OK

Reopen Adobe Reader and now you should be able to open .zip file attachments directly from Adobe Reader.


# How to edit/remove views in exported web archive

You have exported the database into a web archive but now you see that some of the views are not necessary or they could have been named better.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FpJ8eOOaqcN8oRPy7uw05%2Fimage.png?alt=media&amp;token=953d6551-6ead-4025-9f64-a38cfc5f87b7" alt=""><figcaption></figcaption></figure>

All views of the exported web archive are saved in the *views-list.js* file which is located inside of db folder: *DESTINATION\_FOLDER\YOUR\_DATABASE\_ID\db.*

In order to change/remove some views, open the file is any text editor.&#x20;

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FErm9lbeQcNpk4vOqhpNk%2Fimage.png?alt=media&amp;token=4b08a22a-00cd-4c42-9dee-e06b7c8f67b8" alt=""><figcaption></figcaption></figure>

Let's say we have accidentally exported the view *Admin -> Test* and now we want to delete it. It is enough to delete the whole object where that view is in the *views-list.js* file.

Other thing we might want to do is to change the name of the view "Teams by conference" into "Conferences". To do that, we need to change the title value inside the object where that view is located.

This is how the *views-list.js* file looks after the changes:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FV5BNHPX7h0XvqqoKe3h1%2Fimage.png?alt=media&amp;token=52c4d259-0ef0-4cff-95df-ef4f983836c0" alt=""><figcaption></figcaption></figure>

Save the file, reopen the web archive in your web browser and the changes will be visible:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FGut6VVKw8TGQgE2S6vOj%2Fimage.png?alt=media&amp;token=d319bdb3-7592-41a8-a25e-64e77f03b3e1" alt=""><figcaption></figcaption></figure>


# How to change default view in exported web archive

In order to change the default view in exported web archive, first thing you need to do is to find the *views-list.js* file which is located inside of db folder: *DESTINATION\_FOLDER\YOUR\_DATABASE\_ID\db*. You can open it any text editor, it should look like this:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FlY7uMqaUrhBzYYtvW6xS%2Fimage.png?alt=media&amp;token=ff8cd559-db6c-4b3a-aa76-ebf2208d28dd" alt=""><figcaption></figcaption></figure>

In this web archive the default view is "*NFL\\\Conferences*". We can see that because the value of "*is\_default"* is set to *true.* Let's say we want the view *"NFL\\\Superbowl stats"* to be default. We need to change the value of *"is\_default"* in the view "*NFL\\\Conferences"* to *false* and set the value of *"is\_default"* in the view "*NFL\\\Superbowl stats"* to *true*. File *views-list.js* should now look like this:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FFq6doSaouc9Mox7uzbMz%2Fimage.png?alt=media&amp;token=4979a46f-096b-44e9-9feb-c6691136f1db" alt=""><figcaption></figcaption></figure>

Save the file, reopen your web archive in the browser and now when you open the database the default view will be "*NFL\\\Superbowl stats*".


# How to enable Notes doclinks in SharePoint

In order to keep the Notes document links working on SharePoint, a web part must be installed and added to the SharePoint site.

### Installing the web part

The web part can be installed by a SharePoint administrator using the following procedure:

* Open “SharePoint admin center” by using the following link (make sure to replace `\<your\_sharepoint\_tenant\_name>` with your tenant name): https\://\<your\_sharepoint\_tenant\_name>-admin.sharepoint.com/\_layouts/15/online/AdminHome.aspx
* Click on “More features” and open “Apps”

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FSnYy5m3GfKCZRsohRqYD%2Fimg1.png?alt=media&amp;token=fbb4cc1b-0f72-44ed-be69-cf0d9d509c68" alt="" width="325"><figcaption></figcaption></figure>

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FmFCjicwSI2SUMoP9DJtt%2Fimg2.png?alt=media&amp;token=9711dbac-ba23-48e9-93dd-dc0ea094e5ca" alt="" width="563"><figcaption></figcaption></figure>

* Next, download the [swing-doclinks-webpart.sppkg](https://www.swingsoftware.com/dl/ssc/swing-doclinks-webpart.sppkg) file and upload it to SharePoint using the "Upload" button:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F6WQPeyYbTH9zSmrecYr0%2Fimg3.png?alt=media&amp;token=9e4c4842-6779-4977-83ac-623c1158d91e" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
Note: In case previous version has already been installed, you will be prompted to replace it with newly uploaded version:
{% endhint %}

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FunqXXiAVzTUdBI2Hlj57%2Fimg4.png?alt=media&amp;token=4a154ace-bf16-425e-83d3-159154e77dff" alt="" width="448"><figcaption></figcaption></figure>

* After successful upload, you will be prompted to enable the app; we suggest using the "Only enable this app" option, as it will allow you to add it only to the sites where it is actually needed.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FpEXR2BbV9HTYEdBnzYkm%2Fimg5.png?alt=media&amp;token=9d6fdbd6-615f-489b-bc97-6175cc0950da" alt="" width="424"><figcaption></figcaption></figure>

* After it’s been enabled, the web part will be shown in the apps list:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2Fp2q6HL9afWvebH1syLdY%2Fimg6.png?alt=media&amp;token=fb35dbb2-f1fc-4456-9883-7a51a25061e7" alt="" width="375"><figcaption></figcaption></figure>

### Adding the web part to a site

* Navigate to your site, go to “Settings” and select “Add an app”

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F1nYZ4cjlQgvg1xCHMGL2%2Fimg7.png?alt=media&amp;token=1c5f7a1f-70af-4e3e-9993-72ac5eb52c27" alt="" width="326"><figcaption></figcaption></figure>

* The web part is now available in the "Apps you can add" section and you can add it using the Add button:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FuZR1VkkgdA3hT0YJwYRD%2Fimg8.png?alt=media&amp;token=9f3d9028-07f6-4626-a57a-4a3b160c78c5" alt="" width="563"><figcaption></figcaption></figure>

### Creating a page with web part

As a first step, you should check if “doclinks.aspx” is already available in a document library that you are using to upload exported documents and delete it.

If “doclinks.aspx” is not available, you need to create it by using “Web Part Page” content type. It should be available under the “New” button in your document library. If it is not there, you need to add it first.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2Ft9sWJN0Ptw4KDZU0N1bC%2Fnew%20Web%20Part%20Page.png?alt=media&amp;token=3ed901e0-fd62-4c56-920b-e46aceb95657" alt="" width="563"><figcaption></figcaption></figure>

#### Add “Web part page” as a content type

* Open your document library, go to Settings and then “Library settings”. Click “More library settings”.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FodN8TacBfe7MYw8qr4V7%2FmoreLibSettings.png?alt=media&amp;token=bc3a53a2-ebd5-4a66-a807-387daa1f82f9" alt="" width="375"><figcaption></figcaption></figure>

* Under “General Settings”, select “Advanced settings”

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FazsRDBt56ZXIRkLs82lj%2FadvSettings.png?alt=media&amp;token=e53f02bc-72b5-4e07-8da7-07d344102d4b" alt="" width="422"><figcaption></figcaption></figure>

* Under “Content Types”, set “Allow management of content types” to “Yes” and click OK at the bottom of the page to save your settings. You will be returned to the Advanced library settings page.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FRy8QfDfwTP0oYyOAi7Qb%2FmgmtContentTypes.png?alt=media&amp;token=3e27f35d-5322-4ff4-bb58-70d2925738e6" alt="" width="563"><figcaption></figcaption></figure>

* On the Advanced library settings page, go to the “Content Types” section and click “Add from existing content types”.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FOa9Lbc2Uh0CKyX2kgfZp%2FexistingSiteContent.png?alt=media&amp;token=81f9eb37-93d7-4e35-8aef-dfb2e6e715f8" alt="" width="559"><figcaption></figcaption></figure>

* Select “Web Part Page” and click “Add >”. Web Part Page will be added to a list of available site content types. Click OK to confirm your changes.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FTZ7CgxpYwwPjUUJv5oal%2FwebPartADD.png?alt=media&amp;token=0797308a-7b24-4320-9510-8725e8e5110a" alt="" width="563"><figcaption></figcaption></figure>

* You can now navigate to your document library and under the “New” button, “Web Part Page” will be available.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FFpaaMYfxcGvDxPPFQZ3o%2Fnew%20Web%20Part%20Page.png?alt=media&amp;token=92804009-0661-4376-ba56-805a185a2743" alt="" width="563"><figcaption></figcaption></figure>

### Create a web part page

* Navigate to your document library, click the “New” button and select “Web Part Page”.
* As an alternative, you can navigate to your site, go to “Pages” and create a new “Web Part Page”.
* This will open a new Web Part Page screen, where you need to set the page name to “doclinks” and choose a document library that you are using to upload exported documents (this option is available only if you used the alternative way of creating Web Part Page from site Pages). We suggest setting a layout template to “Full Page, Vertical”, although this is not a requirement.
* Finally, you should add the web part to a page. It will be available under the “Advanced” category.
* Once done, you can stop editing the page and make sure the doclinks.aspx page is available in your document library.


# How to Create Custom Title and ND Metadata Fields in SharePoint

Follow these steps to create a custom Title and ND metadata fields for a SharePoint export.

1. Start a new SharePoint export as you normally would. During the export setup, create a **new custom metadata field**. You can create two or more Notes fields if required.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FoOxk4er5pTedeNE69LZJ%2Faa1.png?alt=media&amp;token=3e6daa04-9a8f-4745-acf1-441b02e82038" alt=""><figcaption></figcaption></figure>

2. **Run the export.**
   \
   When the export starts, the new custom field will be generated and saved in the output XML files alongside the standard metadata fields. After the export is complete, locate the db-**analysis.json file** in the **\db** subfolder of your selected destination folder. Right-click the file and open it in a text editor.
3. **Update the custom field's weight.**
   \
   In **db-analysis.json**, locate the new custom field you created during the export setup. The field must be a String. Change its **weight** value to a very high number, such as **10000**, and save the file.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FL7OzuYLLKAL4mEYn4fEJ%2Faa2.png?alt=media&amp;token=1f0f127e-8cb4-4af1-89ae-21870aeef5a4" alt=""><figcaption></figcaption></figure>

4. **Upload the export to SharePoint.**
   \
   Once the **db-analysis.json** file has been updated and saved, proceed with uploading the files and metadata to SharePoint using the normal procedure.

Once the data has been uploaded, your new custom metadata will be used for the **Title** and **ND columns** in SharePoint.


# Troubleshooting


# Troubleshooting Guide

The most common issues with extracting Notes content using Seascape occur due to:

* System environment issues (e.g. lack of necessary permissions to perform certain actions, network connectivity issues etc.)
* Notes design issues (e.g. complicated document form design, Notes/Domino related issues etc.)
* Incorrect installation (eg. NSF file was not unzipped) or lack of write permissions in the installation folder or in Lotus Notes
* Out of date version of the product. Please make sure that the [latest update](/seascape-for-notes/installation/release-history) has been installed.

{% content-ref url="/pages/-MkmS6nBSalgw7sIGz0y" %}
[Release history](/seascape-for-notes/installation/release-history)
{% endcontent-ref %}

## Contacting SWING Support

To submit an issue to SWING Support please send an email to <support@swingsoftware.com>

In order to resolve issues as quickly as possible, the SWING Support Team requires several types of information from the user who experienced the issue, including:

* A description of the issue including steps to recreate it
* Your license key or license information
* The version of Lotus Notes and Windows used
* Screenshots of error messages (if any)
* Content of the Java debug console (Tools - Show Java Debug Console) at the time of error. If you don't see the console option in your Notes menu, here is how to enable it:

{% content-ref url="/pages/-MlPVnGv1vcQ0vHos7ky" %}
[There's no "Show Java Debug Console" option in my Notes client](/seascape-for-notes/troubleshooting/general-issues/no-show-java-debug-console-option)
{% endcontent-ref %}

* Database or document examples. More info:

{% content-ref url="/pages/-MlQU8DiRgXkoYyXzp3R" %}
[How to send sample Notes documents to Support](/seascape-for-notes/troubleshooting/general-issues/how-to-send-sample-notes-documents-to-support)
{% endcontent-ref %}

Sending as much information as possible from the above list helps locating the cause of the issue and finding a solution faster.

## Good to know <a href="#good-to-know" id="good-to-know"></a>

* Typically, it is not required to send your entire database to SWING Support Team, but only a few documents in the database (that the issue can be re-created with) will suffice.
* If you cannot send document examples due to confidentiality concerns, you can instead send only the document forms (deleting any confidential data). During the troubleshooting, the SWING Support Team typically focuses only on the design of the Notes document form, and not so much on the content.
* If needed, SWING Software can also sign a non-disclosure agreement which will allow you to send confidential forms for troubleshooting. Please contact SWING Software for more information.

​


# Error messages


# Type mismatch (13)

Type mismatch (13) error can occur if one of your settings documents is corrupted. Re-saving settings documents should resolve the issue

## **Description**

`Type mismatch(13)`\
`at SwPDFC.SwPDFMain.GENERATEPDF : 35`\
`at SwPDFC.SwPDFMain.PROCESSDOCUMENT : 35`\
`at SwPDFC..PDFLib.SWCREATEPDF : 149`

## **Solution**

The above error may occur if Seascape's settings documents get corrupted. Follow these steps to resolve the issue:

1. Open your Seascape database in the Notes Client
2. Go to Settings -> General and click the **Save** button (without changing any settings)

You should follow a similar procedure for **Export settings** and **PDF settings**:

1. Go to **Settings** -> **Export settings**
2. Double-click on setting that you are using
3. Click on **Edit Settings** and **Save & Close**
4. Go to **Settings** -> **PDF settings**
5. Double click on the setting that you are using
6. Click on **Edit Settings** and **Save & Close**


# There is another PDF conversion process already started

It usually means that the Seascape or PDF Converter dialog is already open in one tab of your Notes client or that notes.ini was not updated properly (e.g. due to the Notes crash during conversion)

The message "*There is another PDF conversion process already started*" usually means that the Seascape or PDF Converter dialog is already open in one of your Notes client tabs, or that the notes.ini file was not updated properly with Seascape's information (e.g. due to Lotus Notes crashing during a conversion job, etc.).

To solve the issue try any of the following:

* Hit OK to close the error message and start a new conversion job. With this action, the notes.ini file should be updated properly so you can start a new conversion job normally.
* Locate and close another open Seascape dialog tab in your Notes client and start a new conversion job.
* Open your notes.ini file (located in the Notes installation folder) using a text editor and delete the "$SwPDFDialogOn=1" line manually (this line is automatically written to your notes.ini file each time a conversion is started using the PDF toolbar icon, and also deleted from the notes.ini file once the tab containing the PDF Converter dialog is closed. In some circumstances the line may not be deleted, in which case manual deletion should be attempted)
* If none of the above works, then it is recommended to remove Seascape completely from your system and run a fresh install. Instructions for complete removal of the tool from your system are available in the following article:

{% content-ref url="/pages/-MkmS6n8suGIdzK3tKjn" %}
[Uninstalling](/seascape-for-notes/installation/uninstalling)
{% endcontent-ref %}


# swllrend.dll corrupted or not extracted

The DLL file is used to provide enhanced PDF conversion quality. If the DLL file gets corrupted or if it is not extracted properly, it can be added manually to the Notes Data folder

When the **low-level rendering** feature of the PDF Converter engine is enabled (in the PDF settings on the General tab), SWING Seascape will attempt to use the **swllrend.dll** file from the **SwPDFC\Libs** subfolder inside your **Notes Data** folder.

The DLL file is used to provide **enhanced PDF conversion quality**. If the DLL file gets corrupted or if it is not extracted properly it can be added to the Notes installation directory manually.

You can download the swllrend.dll file from this page and copy it to the **SwPDFC\Libs** subfolder\*\*,\*\* which is located in **\<Notes Data>\SwPDFC\Libs**

If you are using an ICAA/HCAA client, copy the DLL file to the ICAA/HCAA client installation folder (typically in **C:\Program files(x86)\HCL\HCAA**)

{% hint style="info" %}
You must **unzip** this DLL file before copying it into the **SwPDFC\Libs** folder
{% endhint %}

If the low-level rendering feature is disabled Seascape will **NOT** attempt to copy the DLL file to your system. Note that in that case, the PDF rendering quality may be somewhat lesser when you are converting Notes application documents. However, the conversion of emails will remain unaffected since the emails are processed using a different method altogether.

{% hint style="info" %}
All instances of Notes software should be closed before the new DLL is copied
{% endhint %}

{% hint style="info" %}
If you don't have system permission to copy the DLL file to the Notes Data folder, please contact your Administrator.
{% endhint %}

{% hint style="info" %}
If needed, the DLL file can also be found and copied from the **SWExternalResources** form in the SWING Seascape database (the form can be accessed using **Domino Designer**).
{% endhint %}

{% file src="/files/UXjCcqbdYM22i2FYzE4Q" %}


# ExceptionConverter: java.security.NoSuchAlgorithmException

This error usually occurs if there is a leftover JAR ibmjcaprovider.jar from the previous version of the Notes client

## **Description**

When converting a document, the conversion fails and this error appears in the SWING Seascape dialog or in the Java Debug Console:

```java
AGENT ERROR: ExceptionConverter: java.security.NoSuchAlgorithmException: class com.ibm.crypto.provider.MD5 configured for MessageDigest(provider: IBMJCE version 1.2) cannot be accessed.
class "com.ibm.crypto.provider.MD5"'s signer information does not match signer information of other classes in the same package 
        at java.security.Security.createAlgInstance(Security.java:1338) 
        at java.security.Security.createAlgInstance(Security.java:1232) 
        at java.security.Security.getImpl(Security.java:1123) 
        at java.security.MessageDigest.getInstance(MessageDigest.java:135) 
```

## **Solution**

This problem happens if there is a leftover JAR file named **ibmjcaprovider.jar** in your Notes Java virtual machine folder. It is usually left when upgrading to a higher version of Notes where this JAR has been replaced by a new JAR named **ibmjceprovider.jar**.

To resolve this, all you need to do is to delete the **ibmjcaprovider.jar** file (usually in the **Lotus\Domino\ibm-jre\jre\lib\ext\ibmjcaprovider.jar** folder).


# Exception in thread "Launcher: SwCreatePDF" java.lang.NoClassDefFoundError: -CLASS NAME-

The error message means that PDF Converter engine jar files did not extract properly and were not loaded by Notes client Java Virtual Machine.

PDF Converter engine is written in Java and its JAR files must be loaded in the Notes client JVM.\
The JVM **loads new JARs only on startup** so a restart is required if JVM is already running.

To resolve the issue locate the **ext** folder in your Notes installation (for example C:\Program Files\IBM\Notes\jvm\lib\ext).

If you find any of the JARs listed below in that folder, delete them:

* bcpkix-jdk13-151.jar
* bcprov-jdk13-151.jar
* commons-codec-1.4.jar
* commons-httpclient-3.0.jar
* commons-io-1.4.jar
* commons-logging-1.1.1.jar
* flying-saucer-sw\.jar
* htmlcleaner2\_1.jar
* iText-2.1.7-sw\.jar
* jai\_codec.jar
* jai\_core.jar
* jodconverter-3.0.4.jar
* juh-3.2.1.jar
* jurt-3.2.1.jar
* ridl-3.2.1.jar
* slf4j-api-1.7.7.jar
* swlmbcs.jar
* swpdfc-2.0.0.jar
* sw-unoil-3.2.1.jar
* swUtilities.jar
* xstream-1.3.1.jar
* zip4j\_1.3.2.jar

Now install the latest version of Seascape and restart your Notes client afterwards.

If restarting does not help it is recommended to do a **complete SWING Seascape removal** and start the conversion again. This will force SWING Seascape to set up all required resources again. Removal guidelines are available here:

{% content-ref url="/pages/-MkmS6n8suGIdzK3tKjn" %}
[Uninstalling](/seascape-for-notes/installation/uninstalling)
{% endcontent-ref %}


# Domino HTTP Error Loading Java Virtual Machine

The error usually occurs because of a conflict with the Java heap size setting in the notes.ini file. Lowering value or completely removing JavaMinHeapSize entry should resolve the issue

## **Problem**

Domino HTTP fails to load Java Virtual Machine. As result, the HTTP task fails to start.

## **Cause**

Conflict with Java heap size settings in the notes.ini file prevented the Java Virtual Machine (JVM) from loading.

## Diagnosing the problem

Domino Server console reported the following messages:

```
HTTP JVM: JVMJ9GC019E -Xms too large for -Xmx
HTTP JVM: JVMJ9VM015W Initialization error for library j9gc24(2): Failed to initialize
JVM: The Java Virtual Machine creation returned an invalid JVM machine pointer.
JVM: Java Virtual Machine failed to start
HTTP Server: Error Loading Java Virtual Machine
HTTP Server: JVM: Missing entrypoint in JVM runtime library.
HTTP Server: Shutdown
```

The message **-Xms too large for -Xmx** indicates that the initial **Java heap size** is **larger than the maximum** Java heap size.

In one case, the notes.ini file had the following parameters:

```
HTTPJVMMaxHeapSize=64M
HTTPJVMMaxHeapSizeSet=1
JavaMaxHeapSize=268435456
JavaMinHeapSize=134217728
```

The JavaMinHeapSize of 128MB is set higher than the HTTP's JVM heap size 64MB.

## **Resolving the problem**

The solution is to remove or lower **JavaMinHeapSize** (JavaMinHeapSize=67108864) or alternatively, increase **HTTPJVMMaxHeapSize** to 128M (HTTPJVMMaxHeapSize=128M).\\

## **Note**

This article is copied from HCL support resources.

Learn more: **HTTP/JVM Out of memory**\
<https://ds_infolib.hcltechsw.com/ldd/dominowiki.nsf/dx/HTTPJVM_Out_of_memory>

{% hint style="warning" %}
[Lotus Notes’ life support is over – what now?](https://www.swingsoftware.com/blog/lotus-notes-support)

End of support means end of life for old IBM-branded versions of Lotus Notes and Domino. It’s time to commit. Decide what to do with your existing IBM Domino infrastructure and databases: upgrade or finally retire your IBM Domino environment. Just don’t stay in a half-migrated deadlock.
{% endhint %}

{% hint style="info" %}
[Lotus Notes Data Migration and Archiving: Seascape for Notes](https://www.swingsoftware.com/seascape-for-notes)

Seascape for Notes helps you preserve historical data outside of HCL Notes and Domino. It exports Lotus Notes databases as stand-alone PDF/XML/JSON archives, retaining documents, views, links, and metadata. Plus, Seascape enables the easy uploading of archived documents to Microsoft SharePoint or Office 365.
{% endhint %}


# Cannot write or create file (file or disk is read-only)

Error usually occurs if you try to open the Seascape NSF file directly from the ZIP file without extracting it first to your Notes Data folder

## **Description** <a href="#description" id="description"></a>

The below error message appears upon an attempt to open the PDF Converter .nsf file.

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlKPaEa-QNSB57WFyeH%2F-MlKQ0twzc-etbVpzoEG%2Fimage.png?alt=media\&token=8d053e13-d8a7-4515-a321-3a80393ecbd3)

## **Solution** <a href="#solution" id="solution"></a>

This problem occurs if you try to open the .nsf file from inside the .zip package file without extracting the file first. Therefore you should right-click on the **Seascape.zip** file, extract the .nsf file to the desired location (recommended is inside your Notes Data folder), and then open it from there.


# ReferenceError

The JavaScript error occurs in the Adobe Reader when a document link is clicked in a PDF file (Disk Archive)

When a doclink is clicked in a PDF file, the following JavaScript error message appears:

`ReferenceError: openLinkPriv is not defined`

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FCvPcIJxva42TnsELx5MY%2Fimage.png?alt=media\&token=34b8b6f5-d080-48c8-9d74-447270bbc147)

The error is caused due to a missing **swpdfc.js** file which is normally installed in the Adobe Reader installation folder automatically.

To resolve the issue, create the `swpdfc.js` file (see the code below) and copy it manually to the Adobe Reader installation folder. The default path to the folder is normally "C:\Program Files (x86)\Adobe\Reader 11.0\Reader\Javascripts", however the actual path on your system may be different.

```javascript
var openLinkPriv = app.trustedFunction( function(dbId, docUnid) {
	app.beginPriv();
	try {
		var depth = 50;
		try {
			depth = this.path.split("/").length;
		}
		catch(e) {
		}
		
		var dirUp = "../";
		var xmlRoot = "";
		var xmlFile = "doclinks.xml";
		var xmlStream = null;
		var count = 0;
		do {
			try {
				xmlStream = util.readFileIntoStream(xmlFile);
			} catch(e) {
				xmlStream = null;
			}
			
			if(xmlStream == null) {
				xmlRoot = dirUp.concat(xmlRoot);
				xmlFile = dirUp.concat(xmlFile);
			}
			
			count++;
		} while(xmlStream == null && count < depth);
		
		if (xmlStream == null) {
			app.alert("XML not found");
			return;
		}
		
		var xml = XMLData.parse(util.stringFromStream(xmlStream), false);
		var xPath = "string(//data/element[@id = '";
		xPath = xPath.concat(dbId);
		xPath = xPath.concat("-");
		xPath = xPath.concat(docUnid);
		xPath = xPath.concat("']/location)");
		var location = XMLData.applyXPath(xml, xPath);
		location = xmlRoot.concat(location);
		app.openDoc(location);
	} catch(e) {
		app.alert("Linked document could not be found: " + location);
	}
	app.endPriv();
});
```

To find the Adobe installation folder on your machine easily, right-click on the Adobe icon that you use to start the program and open click Properties.

The Properties popup then appears as shown in the below example, and you can click Open File Location to open the installation folder:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FIaFmTwlcMqJS7SXeVdz7%2Fimage.png?alt=media\&token=89b03dbb-23d1-4c90-a783-48863d37ff21)

Once you are in the folder, locate the Javascripts folder and save the `swpdfc.js` file in it.


# General issues


# There's no "Show Java Debug Console" option in my Notes client

The Show Java Debug Console menu is considered an Advanced Menu in Notes 8 and higher and if enabled, it is available under the Tools menu. Click on the below image for a bigger display.

![](https://gblobscdn.gitbook.com/assets%2F-MlCAurE6RSGoCmtmAET%2F-MlFmn-NSlJ2HRl2GU3B%2F-MlFmzz_emLv8-MTgj3P%2Fimage.png?alt=media\&token=3e5c79c4-4d11-4d56-9115-9bb8c99bf55b)

If you have Lotus/IBM/HCL Notes, Domino Designer® client and Domino Administrator client installed on your workstation, but the Show Java Debug Console menu does not appear in the Tools menu, then you need to enable the Advanced Menus by selecting View (1) -> Advanced Menus (2) in Notes (see below image). After that, the Show Java Debug Console menu will appear under the Tools menu as in the above image.

![](https://gblobscdn.gitbook.com/assets%2F-MlCAurE6RSGoCmtmAET%2F-MlFmn-NSlJ2HRl2GU3B%2F-MlFn1KjRNCNlc2e60NG%2Fimage.png?alt=media\&token=cb917565-6743-4411-8879-b9a94d7f80ba)

If you have a Notes-Only installation on your workstation then the Advanced Menus are **not available** by default. In this case, the following parameter can be supplied in your notes.ini file which will enable access to advanced menu actions: MenusAdvanced=1

In Lotus Notes 6 or 7, the Show Java Debug Console menu is found in File > Tools > Show Java Debug Console.


# Notes password issue

If you get this Notes password issue:

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FksgkOW8eOj3J2Qz89TYP%2FpassIssues1.PNG?alt=media&amp;token=83a18cad-d7f1-4a9b-9d60-733ce3fff272" alt="" width="404"><figcaption></figcaption></figure>

**Please follow these steps:**

1\) Open Seascape and navigate to **Actions → Installation → Verify Installation**.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FGiVrSDmzUQ9PP8cqsBek%2Fpass1.png?alt=media&amp;token=da281e33-9e67-430d-b19f-df1e2be86592" alt=""><figcaption></figcaption></figure>

2\) When the verification window appears, click **"Verify Installation"**.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FG0mCuAbOiETtfeep6zMz%2Fpass2.png?alt=media&amp;token=88c854eb-82a0-4777-958d-ca1ddec57a8f" alt=""><figcaption></figcaption></figure>

3\) If all items have a green tick (as shown in our screenshot), then go to **Actions → External JVM → Reset user credentials**.&#x20;

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FKAVyIwHjL0t4cueGitHE%2Fpass3.png?alt=media&amp;token=826acee5-e805-4e08-9a54-8fd224aba5da" alt=""><figcaption></figcaption></figure>

4\) In the popup window, enter your credentials, then exit Seascape and try running the conversion again.

5\) If the issue persists after completing steps 1–4, navigate to **Settings** and change the **JVM in use** to **Notes JVM** instead of **External JVM**.&#x20;

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FRH9yVy8e9scZwqJuBFP5%2Fpass4.png?alt=media&amp;token=d9c88211-f9f0-4660-9596-cafe9d2f2e89" alt=""><figcaption></figcaption></figure>


# Activation error: Signature validation error

"Activation error: Signature validation error." is a known issue that was caused by a PHP upgrade on our license registration server.

If you encounter this **Signature Validation error**, you must update to the latest version.

<figure><img src="https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F8k10wV2WddSwCSU8lLhX%2FsignatureError.png?alt=media&amp;token=36824e1d-c594-44f1-a86e-5d8664ad63df" alt=""><figcaption></figcaption></figure>

**Download** and **install** the latest version of Seascape for Notes, which you can get here: <https://www.swingsoftware.com/download/dl-ssc>

You can upgrade your existing installation or perform a fresh install.

Instructions for **upgrading** can be found here: [https://docs.swingsoftware.com/seascape-for-notes/installation/installing-and-activating](https://docs.swingsoftware.com/seascape-for-notes/installation/upgrading)


# View the conversion log in case of a Notes crash

If Notes client crashes or freezes during a conversion job, the export log won't be generated but you can access the log file on your hard disk

A temporary log file is written on your hard disk which stores information on the progress of the export as well as the last processed document (which most likely caused Notes to crash).

This file can be found in the folder located in **%USERPROFILE%\AppData\Local\Temp\SWING Seascape** (the file name is random, so you will need to look for a .log file).

Once you’ve located this file you can send the information (and possibly the document which caused the crash) to SWING Support for further troubleshooting.


# Zip files can not be detached from PDF

Opening zip attachments depends on security settings of your PDF reader

Adobe Reader does not allow this type of attachment to be opened, so in PDF settings we have an option to overcome this issue.

You can choose to rename the zip extension to 7z (or any other, but with 7z you can open a file directly in 7-Zip or another program that supports that file type).

This setting can be found in the Attachments tab of your PDF settings:

![Change zip extension to 7z](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FMHEodtFY7XLkybyohcSl%2Fimage.png?alt=media\&token=1bb57fd5-ae3c-4423-ae7c-c54303586b59)


# Conversion speed is slow

The below is a list of common causes for slow PDF conversion speeds:

## External resources

External resources, such as inline images in emails, need to be downloaded in order to render and extract an email or a document from a Notes database. These resources can be hosted anywhere on the Internet, and some of them are no longer available. This can significantly increase the time it takes to export. In order to speed things up, it is possible to disable HTTP stream:

{% content-ref url="/pages/-MlUmCpfLR3r64FNAxhW" %}
[How to disable HTTP stream](/seascape-for-notes/faq/how-to-disable-http-stream)
{% endcontent-ref %}

## **Symantec Endpoint Protection (SEP)**

Symantec Endpoint Protection client feature "Notes Auto Protect" can cause serious performance degradation.\
This is due to extraction and scanning of SWING Seascape Java Archive files (JAR's).\
Java files are part of SWING Seascape core deployment and they do not pose security risk.

However, these files are archives containing thousands of Java classes which overload's antivirus scanner as it is extracting all files from the archive and scans them for viruses.\
This issue can be resolved by disabling JAR files scanning in SEP:

{% content-ref url="/pages/-MlL5ZE5c38kbkwjS1zY" %}
[How to enable SWING Seascape with Symantec Endpoint Protection (SEP)](/seascape-for-notes/troubleshooting/general-issues/how-to-enable-swing-seascape-with-symantec-endpoint-protection-sep)
{% endcontent-ref %}

## **Startup time**

When a conversion job starts for the first time, the Java Virtual Machine needs to be initialized which can take some time. However once initialized, all subsequent conversions should take much less time (because the system is up and running).

## **Network issues**

Network issues my cause slower conversion speeds in case users are converting documents from remote databases that are accessed via LAN or Internet connection. These documents need to be downloaded in order for the conversion job to be initiated, and if the connection speed is not good or there is a high network traffic then this may account for some extra processing time. If you're experiencing network related issues, you may consider replicating your database locally or installing Seascape on the server and running it there.

## **Document design**

@DbLookup formulas and document embedded views cost a lot of time as database has to be searched for each document that is being converted with those design elements.\
Bigger databases take more time to finish the search. To improve the conversion speed, consider using [Alternate Forms](/seascape-for-notes/seascape-settings/alternate-forms).

If conversion is running on Domino Server which serves multiple purposes, conversion might be interrupted frequently by Domino Server's agent manager.\
Please check your Domino Servers log for processes that might interrupt conversion process.

## **Lotus Notes 6.5 and 7**

SWING Seascape uses the cross Java Virtual Machine (JVM) communication in Lotus Notes 6.5 and 7 (because the Lotus 6.5 Java 1.3.1. and Lotus 1.7 Java 1.4 do not provide the required framework for SWING Seascape to work properly).

The cross JVM communication is going over TCP/IP protocol and in this case it is required to initialize the Notes 6.5 and Notes 7 JVM and the local system JVM.

The time needed to communicate between two virtual machines may account for some extra processing time.

Operating system issues

If the user's operating system is congested or infected with malicious software, the conversion speeds may be slower.

## Hardware

Outdated hardware can also cause slow conversion speeds.\\


# How to send sample Notes documents to Support

Here are the instructions on how to send documents/emails to SWING Software Support Team for troubleshooting, in case you experience any difficulties with PDF conversions.

1\. In your Notes client, right click on database containing the error prone document and select **Application > New Copy:**

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlQTylB3QLdOo4h3E_Q%2F-MlQUhkaL0cbNvUrw1pC%2Fimage.png?alt=media\&token=c42a9d3e-68af-42d5-943f-8ba010d6f246)

2\. In the **Copy Application** window:

* Select **Application design only**
* Uncheck **Access Control List**.

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlQTylB3QLdOo4h3E_Q%2F-MlQUoz9i8zeXhs2VLvi%2Fimage.png?alt=media\&token=5335ec5f-8dc9-4f14-9089-8b3c51e78441)

3\. Click on the **Encryption** button and select **Do not locally encrypt this database** option. Click **OK**, and one more time in the **Copy Application** window. The new database will be created in your Lotus Notes workspace:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlQTylB3QLdOo4h3E_Q%2F-MlQUu_iXNTGiV2jUcAr%2Fimage.png?alt=media\&token=7e87af13-3f90-4e3c-98a4-0d1f8e7054a2)

4\. Right click on the new database in Lotus Notes workspace and select **Application > Access Control**:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlQTylB3QLdOo4h3E_Q%2F-MlQV-sYhyzY0NEJ15ip%2Fimage.png?alt=media\&token=73d059d8-7563-4550-bb4c-025830829e33)

5\. Set the database ACL **-Default-** user to **Manager** and click **OK**:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlQTylB3QLdOo4h3E_Q%2F-MlQV5Aeul7aJfEnq7GF%2Fimage.png?alt=media\&token=f45289d8-5004-430b-840a-1b8302cf403e)

We now have an empty database which has same design as original database.

6\. Open original Lotus Notes database and select and copy the emails/documents which are not converted properly to PDF.

7\. Return to the database which you just created and paste the documents here, then close the database.

8\. Finally, locate the newly created database file on your hard drive (usually `C:\Program Files\IBM\Lotus\Notes\Data` ) and send it to <support@swingsoftware.com>.

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlQTylB3QLdOo4h3E_Q%2F-MlQV9a_nr-1kC0-tDSC%2Fimage.png?alt=media\&token=a231fa1b-ed40-46c0-83ae-8bbca02156bd)


# How to enable SWING Seascape with Symantec Endpoint Protection (SEP)

This content has been created by Symantec support and engineering team.

> **Delay in Email to PDF conversion using SWING Software when SEP Lotus notes Auto protect is enabled.**\
> <https://support.symantec.com/en_US/article.TECH235512.html>

## Situation

While using SWING Seascape or PDF Converter for Notes to convert email into PDF IBM Notes 9.0.1 Social Edition there is a delay for email conversion when SEP Lotus notes plug-in is enabled. With SEP Lotus notes plug-in disabled, the email is converted instantly to a PDF. With SEP plug-in enabled, it takes around 10 minute to convert the email to PDF. This converter is installed as a plug-in on Lotus notes .

## Environment

Windows 7 and Windows 10 with IBM Notes 9.0.1 Social Edition

## Cause

When a sample document is opened using SWING Seascape, each time SEP intercepts and extracts all the files to temp folder "C:\Users\Symantec\AppData\Local\Temp\LDVPScan\\". It includes SWING Seascape files also. There may be images, JAR files, DLL, JS files and so on.

When a JAR file is given to the scanner, decomposer decompresses all the files and scanner scans each file. This behavior is by design.

## Solution

### A. For managed SEP clients:

1. Edit the "Virus and Spyware protection policy
2. Under Windows Settings > Email scans > Lotus Notes Auto-Protect > Scan details Tab
3. Select the option to "Scan only selected extensions"
4. Once you click on "Select extensions" button, ensure that JAR is not added in the file extensions list (by default not added)

### B. For unmanaged SEP clients:

1. Open SEP GUI > Change Settings tab
2. Click on "Configure settings" button under Virus and Spyware Protection section
3. Click on Notes Auto-Protect Tab
4. Choose the option "Selected" under File Types.
5. Ensure that JAR is not added in the file extensions list


# Header and footer not visible in my emails

Headers and footers are supported for all documents except email messages

Support for headers and footers in email messages is planned for a future product update.


# Email images do not appear in PDF

Some images (e.g. newsletter images and similar) are not saved within the email body, but are pulled from an external location or site when the email is opened in Notes.

During processing, Seascape will attempt to pull all email images from external sites, but if it is unable to do so (due to connectivity issues, or if the image is no longer available) then the PDF file will be created without the image.


# Document links not working

If the document links in the PDF files are not working properly after performing an export from Notes, first check if a required javascript file is found in the Javascripts folder (for Adobe Reader DC).

The javascript file is called swpdfc.js, while the Javascripts folder is typically located in C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\Javascripts

If the file is not found, it will need to be copied to the Javascripts folder manually. Contact SWING support team in order to get a copy of the file.

If the javascript file is found in the Javascripts folder, you will also need to check Adobe Reader's security settings. In Adobe Reader DC, Go to Edit > Preferences and on the Security (Enhanced) tab set the settings as shown in the below screenshot:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlL3Lma9E2hbAvoSHXA%2F-MlL47Pk1dzuQFTTaDgT%2Fimage.png?alt=media\&token=d01707b2-2fd0-4efb-96b0-7ce307e40123)


# Thai symbols not shown in PDF document

To convert documents with Thai symbols one of the required fonts must be installed on the system

When converting documents with Thai symbols, SWING Seascape checks if **Angsana New** font is installed on system. Font *Angsana New* is the most common Thai font on Microsoft Windows.

If *Angsana New* cannot be found, SWING Seascape checks for **Garuda** font, which can be freely downloaded from [the web](http://slice-of-thai.com/fonts/Garuda.ttf).

Finally, if both fonts are not present, SWING Seascape will look for **Arial Unicode MS**.

Follow these steps to install downloaded fonts:

* Download the font to your computer
* If the font is compressed, unzip it
* In Windows Explorer right-click on the font file and select **Install for all users**![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2F84KZuhEXNpzn08CCryu6%2Funknown.png?alt=media\&token=4f9c7576-90f9-44dd-8fe1-e6cd3cc5287f)
* Close Notes client and all other Notes applications (Designer, Administrator, etc.) and then start it again

{% hint style="info" %}
It is important that font is **installed for all users**. If the font is installed just for the current user Windows will be able to use it but it won't be available for Seascape
{% endhint %}


# Twistie icons not showing in Firefox 68

When a locally hosted Seascape archive is opened in Firefox 68 or higher, the twistie icons are replaced with a different icon as shown in this screenshot:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlPvDFcMA1MolEkLrfZ%2F-MlPvRR7kphKlsKQcuLq%2Fimage.png?alt=media\&token=7192fc3d-12a6-468e-8c82-1d0730fb2faa)

The issue is caused due to a change in the way that the origin of the page is defined in Firefox starting with version 68.

\
More info: <https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSRequestNotHttp>\
\
To resolve the issue, you'll need to set the **privacy.file\_unique\_origin** setting in your Firefox settings to **false**.

\
Type **about:config** in your address bar, look for the **privacy.file\_unique\_origin** setting, and double click the **Value** entry so it changes to **false**:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlPvDFcMA1MolEkLrfZ%2F-MlPvYW-UAE8BIkBt1KF%2Fimage.png?alt=media\&token=141690a4-b6c3-4a85-aca7-7f64f352fbad)

After restarting Firefox, the twistie icons will be displayed normally:

![](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkmLDl5OXrWVfn2nv57%2F-MlPvDFcMA1MolEkLrfZ%2F-MlPve20ia0LCwO_nDI5%2Fimage.png?alt=media\&token=bde889cf-608f-4ebe-aff6-45ff2c8e6d95)


# "Too many columns" for SharePoint upload

SharePoint has a limitation on number of columns in a single document library or a list, so SharePoint Uploader will warn you if you try to go over that limit

When uploading archives to SharePoint using our Uploader on the 3rd step you have an option to select metadata fields from your archive that you want to transfer to SharePoint.

![Click on "Review and map fields between Notes and SharePoint"](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FgdrMgIJLUKOOqGHl1WBQ%2Fimage.png?alt=media\&token=840c25ef-f5ca-4c90-9304-65aed2e58a90)

For each selected field the tool will create a column in the SharePoint library or list. However, SharePoint has limitations on the maximum number of columns that each library or list can have and the tool will warn you if you select too many columns.

![Warning message "Too many columns selected"](https://1039028294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkmLDl5OXrWVfn2nv57%2Fuploads%2FkLiTcn6JwK72JhAYzAnf%2Fimage.png?alt=media\&token=f2c6aaea-422c-4049-a60c-5f1f01d25740)

In this situation, we recommend that you unselect metadata fields that you don't plan to use in SharePoint views or for search. That information will not be lost, it is still preserved inside your PDF documents that are uploaded to SharePoint.

If you disregard this message and start the upload without deselecting fields you will probably get this error and it will cause the upload to fail:

```csharp
ERROR SharepointUploader.MetaData.MetaProcessor - Microsoft.SharePoint.Client.ServerException: The column cannot be added because the total size of the columns in this list exceeds the limit. Please delete some other columns first.
```

{% hint style="info" %}
The limitation depends on the type of each column. Each type has its own size, and the total size of all columns in a library or a list must be under a limit. You can read the details and find the sizes of each column type in [this article on Microsoft Docs.](https://docs.microsoft.com/en-us/sharepoint/install/software-boundaries-limits-2019#Column)
{% endhint %}


# PDF Converter for Notes

Export Lotus Notes emails, documents and databases to PDF + XML

Welcome to the SWING PDF Converter for Notes documentation!

### What is PDF Converter for Notes?

SWING PDF Converter for Notes exports HCL Lotus Notes emails, documents and databases to PDF+XML. The tool introduces greatly simplified email and document export and archiving capabilities to Lotus Notes. It adds the PDF icon to the Notes client toolbar, which lets users convert one or more Notes emails or documents. LotusScript API is provided for application developers.

### PDF Converter vs. Seascape for Notes

If your goal is to bulk archive a couple, dozens, or even hundreds of Lotus Notes databases, you should consider [SWING Seascape for Notes](https://docs.swingsoftware.com/seascape-for-notes/). It produces standalone, browsable archives. It also includes the SharePoint Uploader module to let you store your records in SharePoint.

### Technical Support

You are a customer with a valid Software Subscription or Maintenance Plan, and have a product-related question or issue – let us give you a hand! Our technical support team is standing by to offer friendly, high-quality, responsive technical support.

{% hint style="info" %}
Before you contact our Technical Support, please consult the FAQ lists and technical articles - someone may have already asked your question. It is also recommended that the latest update has been installed before reporting a problem with your software.
{% endhint %}

If you are unable to find the answer you are looking for, please submit your [Support Request](https://swingsoftware.freshdesk.com/support/tickets).




---

[Next Page](/llms-full.txt/1)