Deployment Guide – imDocShare app for Microsoft 365 SharePoint Online / SharePoint Server 2019 / SharePoint Server 2016 Copy

Introduction

This deployment guide assumes that the end user has the appropriate level of permissions to access and add/remove apps from the root site collection’s App Catalog. If you do not have these levels of permissions, please contact your Office 365 tenant’s global administrator and ask for Root site collection Administrator access.

This guide is meant to cover the deployment process of SharePoint Framework (SPFx) WebParts on various environments. If you would like further assistance with using and configuring the individual SPFx WebParts, please see our documentation entitled “imDocShare WebParts – Power User Guide”. This guide does NOT cover installation and usage of the imDocShare Teams app. For more info about this, please request documentation specifically for the Teams App.

Note: SPFx WebParts are not compatible with on-premises SharePoint Server 2013, 2010, 2007 or 2003 versions. SPFx specifically requires the “Feature Pack 2” update that comes with SharePoint 2016. We provide a Visual WebPart sandbox solution package for on-premises SharePoint Server 2013 environment.
Site Collection Libraries MUST be able to host JSON and JS files or else deployment will fail. Any security measures that block Popups or iFrames must be turned off as our authentication uses these resources. There is an auth option for users who cannot turn off iFrame blocking, please see the auth section for more info.

Supported Browsers

Supported Browsers:

Microsoft Edge
Google Chrome (latest released version)
Mozilla Firefox (latest released version plus immediate previous version)
Apple Safari (latest released version)
Internet Explorer 11 (limited support only. IE11 Protected Mode is not supported)

Not Supported Browsers:

Internet Explorer 10
Internet Explorer 9
Internet Explorer 8
Internet Explorer 7
Internet Explorer 6

Deploy to App Catalog

The SPFx framework uses SharePoint App Catalog as a container for deployment. Once you are logged in as an Admin user, navigate to the App Catalog of the site collection where you wish to deploy the WebParts. In the SharePoint Administrator center, click Classic features > Apps > App Catalog.

If your SharePoint site collection does not have an App Catalog, you will be guided through a process to create one. Please follow the instructions and create the appropriate App Catalog. This is required for the App to be deployed to the site collection. Once you have created and/or navigated to the location of the App Catalog, you should see a screen like this:

From here, click on Apps for SharePoint and click “Upload” to directly upload “imDocShare.sppkg” file.

All imDocShare assets should automatically be deployed into the same SharePoint location typically found here – https://{your-tenant-name}.SharePoint.com/sites/AppCatalog/ClientSideAssets/{WebPart GUID}

SharePoint On-Premises

For SharePoint On-Prem, instead of manually deploying to the app catalog, you will use a PowerShell script that will automatically deploy to the App Catalog and also deploy the required assets to the appropriate libraries. Please see the section entitled “Deploying on SharePoint On-Premises” for more information.

Deploying the App to SharePoint Online

Make sure that you have the required admin privileges on your tenant to be able to add / remove apps from the App catalog and / or create the app catalog itself. See the previous section for further instructions.

Drag & drop “imDocShareSPO.sppkg” file or click “+new” to browse and pick your file. Once the upload completes, your screen should look like this:

Note: Please check the box in the dialog above or else you will have to manually add the app to each site collection.

Eventually, the files will be stored in this location:

https://{your-tenant-name}.SharePoint.com/sites/AppCatalog/ClientSideAssets/{WebPart GUID}

Once the deploy is successful, please navigate to the location specified above where the app assets are deployed. Take the imDocShareLicenseKey.txt file provided and simply drop the file into this library. This should now enable your imDocShare license with the specific features you have requested. For more information on licensing, please consult our Power User Guide.

If your SPO environment follows a similar structure to the link above, you will need no further action to complete the deploy. However, if it does not, then you will have to run the included PowerShell install script to make sure that your assets are deployed to the correct location. We have included a convenient install script (install.ps1) to help you ensure that your deployment is successful regardless of the environment type.

If you would like to deploy your assets to a custom location OR your app catalog has an atypical name/structure, you can use our installation script to automatically install the sppkg and deploy the required assets to a location of your choice. Simply execute the script (install.ps1) that is packaged together with the sppkg file and answer the prompts to let the script determine where to deploy the assets. If you do not take this step, your installed webparts may have difficulty retrieving scripts or assets from the correct location.

Please note the location of your deployed assets folder. For SharePoint Online, this will often include the ID of the app. This ID will show up in the App Catalog’s list of apps after deploying the sppkg as in the screenshot above. This value needs to be used later when setting up webparts. It will be used in the config value named “assetPath”, which is required to retrieve static assets and also query licensing information. Your assetPath should look like

https://{yourSharepointTenant}/SiteAssets/imDocShare/folderIcons/

Adding WebParts on Modern Pages vs Classic Pages

While SPFx is meant to be compatible with both modern and classic pages, the experience might be slightly different for each one. Once “imDocShareSPO.sppkg” has been deployed, it is referred to as an “App” by SharePoint. You can now go to any page on the site collection and add this app to the site collection, which will, in turn, make the WebParts available for use in the insert WebPart menu.

Modern Page – Adding the App

This step can be skipped if you have checked the “Make this solution available to all sites” checkbox during deploy

Navigate to your site’s Site Contents page and click the +New button, then select App

If you have followed the instructions above for deploying “imDocShare.sppkg” file to the Site collection App Catalog, then the app that you added should be available under the “From your Organization” tab on the left side

Add the App from here and it will be available for all users on that specific site collection

If you are unable to see the app, this means that the App Catalog where the app has been deployed and the current site collection are disconnected from each other

If you can see the app, but trying to add it causes an error, this generally means that you are logged into an account that does not have the correct permissions or the site collection has not been configured to accept apps. In this case, please speak to your SharePoint Administrator to enable apps.

Modern Page – Adding imDocShare WebParts

Create a new site page or navigate to the page you want to add the WebPart. Upon entry, you should already be in “edit” mode. Click the + button to add a new WebPart to the page.

There should be a dropdown menu that opens and should contain the WebPart that you have added to the site via Apps

Classic Page – Adding the imDocShare WebParts

Navigate to your site’s Site Contents page and click the “add an app” button

From here, you will navigate to a page that looks the same as the modern version, choose “From Your Organization” and look for your app on this list. Add the app and your SPFx WebParts should become available once you try to add them to a site page.

Create a new site page or navigate to the page you want to add the WebPart. Click on the “Edit” button on the top right or open the page ribbon by clicking the “Page” button on the top left and choose the first tile “Edit”.

Once you are in edit mode, now there should be a tab named “Insert” on the ribbon. Click on it and choose to add a “WebPart”

By default, imDocShare WebParts will appear under “imDocShare”.

The process for adding webparts in On-Prem site collections is identical to the process for classic sites as older sites are considered to be classic.

Deploying on SharePoint On-Premises

Deploying to an On-Prem environment means that you must pay close attention to SharePoint Server versions to ensure compatibility. imDocShare SPFx WebParts can only be configured for on-premises SharePoint Server 2016 or 2019 and for SharePoint Online. For on-premises SharePoint Server 2016/2019, the update called “Feature Pack 2” must be installed on the SharePoint Server in order for the site collection to recognize and validate the “imDocShare.sppkg” file that we are deploying. Here are the general guidelines on compatibilities between the SharePoint version and what SPFx version should be used:

SharePoint Online: Can use latest SPFx version

SharePoint 2019 On-Prem: Use SPFx version 1.4.1 or earlier

SharePoint 2016 On-Prem: Use SPFx version 1.1.0

SharePoint 2013 On-Prem: Please contact us for a Visual WebPart Farm Solution

Once the SharePoint Server farm is configured to enable app deployment and usage, the process to add the SPFx WebParts project should be like deploying in SharePoint Online. If your SharePoint Server does not have apps enabled, ensure all pre-requisites are completed before any apps like imDocShare is deployed.

Note: Site Collection Libraries MUST be able to host JSON and js files or else deployment will fail. Any security measures that block Popups or iFrames must be turned off as our authentication uses these resources.

Pre-Requisite for iManage on-Premises Server

If your iManage Work server is open to public access and or using the iManage cloud implementation, this section can be skipped. However, servers which are NOT accessible through public internet must fulfill an additional pre-requisite: installation of our imDocShare proxy service through Azure App services.

This is required because our app uses a public service application to:

Authenticate with the iManage server
Send and receive queries to the iManage API server

If the server is not accessible to our public service (e.g. inside a private network or behind private firewalls) then imDocShare will not be able to retrieve the content you wish to see.

Our solution to this issue is to install a proxy service in your environment which will redirect to our app service. Clients who have specified that they are using On-Premises iManage server will be provided with a package and documentation to install this service app. The service app must be deployed either as an Azure app service or as an IIS site or app. Please see our “imDocShare On-Prem Proxy Service Installation Guide” to complete this process. If you have not received this info, please contact [email protected] in order to receive these essential components.

Setting up your SharePoint Server Environment to Enable Apps

There may be several blockers that affect whether your users can add apps to a site collection or not. Please contact your SharePoint farm administrator to troubleshoot these points if you are having issues but here are a few helpful tips:

Make sure Apps are enabled in your farm

Configure the subscription settings service application

Configure the user permission and groups

Make sure the App Management Service application is associated with the SharePoint web application

Configure App URLs

Configure SSL for IManage Authentication (requires HTTPS)

Installing the App into your App Catalog

Due to the lower version of this SPFx project, SPFx is unable to automatically deploy client-side assets to the App Catalog site collection

Our On-Prem deployment package will generally include a SharePoint Management PowerShell script that will execute an automatic deploy. You can recognize this file by its name: “install.ps1”. Here is a general breakdown view of the package contents:

The script will first install the sppkg to your site’s App Catalog

Then, it will create a custom list in the root site collection where it will deploy all the files required to load the webparts

Once deployed, you can check in your site Assets library where you will find the webpart assets as pictured below

In order to begin the process, please edit the file “install.ps1” file using a text editor (such as notepad) and replace the values on the first 3 lines with values that correspond to your particular site collection. These values are highlighted in the text and screenshot below (in case you cannot see in the screenshot):

$appCatalogUrl = “https://klstsp16/sites/AppCatalog“

$appLibFolderPath = “AppCatalog”

$assetSiteUrl = “https://klstsp16“

Once these values have been customized. Please execute the file by opening SharePoint Management Shell, navigating to the deploy folder and running “install.ps1”. Please ensure that this file remains in its default location in the deployment package.

Upon successful install, the script will automatically open a browser page leading to your App Catalog where the sppkg has been uploaded. Here, you should see a new sppkg file called “imDocShare” which should be automatically uploaded

Please select the file, click on the Files tab in the top ribbon and click the “Deploy” button. This will deploy the package to the site collection that you have specified. It should look something like this:

Once the app has been deployed to the App Catalog, now it can be added to any site collection by visiting the “Site Contents” of your site collection and selecting “Add an app…”

Once imDocShare has been successfully added, you should be able to create new webparts using imDocShare. Please see our “imDocShare Webparts: Power User Guide” to learn more about how to create, configure and update webparts.

If there is some problem with our automatic install script, we have also included instructions in a section below to manually deploy the sppkg and its required assets.

Manual Deploy

Go to “start” on your computer to open your SharePoint Central Administration Page

Navigate to Apps > Manage App Catalog.

Make sure that the correct site collection name is selected in “web application”, on the top right of the page

If your site collection does not already have an App Catalog, pick the option to create a new app catalog site. Once you have filled in the form to create the App Catalog, navigate to it and you should arrive at a familiar page:

Click on “Apps for SharePoint” and add a new document to this list. Select “imDocShare.sppkg” file and upload it. Now, your new WebParts should be available to use for any user in this site collection.

Adding the WebParts

Please note: the names and functionalities of webparts may vary depending on the version of imDocShare. For example, on SharePoint On-Premises 2016, instead of differently named webparts, there is a single universal webpart named “imDocShareViewer” which can be converted to all other webparts using configuration.

Navigate to the site collection where you would like to use the Web parts

Navigate to Site Contents and choose “Add an app”.

The app that you added through the admin deployment should be available here. Click on it to add it to Site Contents. *Note: Adding the app should be a similar process to SharePoint Online for Classic pages.

Now navigate to the page where you want to add the webpart and click “Edit”.

Click within the box you would like to add the webpart to and click “Insert” and “Web Part”.

imDocShare WebParts should appear under the “Other” folder in categories, unless you have specified some other way of populating the WebPart.

Asset Deployment for SharePoint On-Premises

We are providing a convenient PowerShell script for users to install their sppkg and assets. This install script will come together with the deployment package and offers a single solution for multiple environment types.

For SharePoint Online, assets are generally automatically deployed unless there is an irregularity in how the App Catalog is structured. Please see the final note in the “Deploying to SharePoint Online section.” For On-Premises SharePoint environments, asset deployment works a bit differently.

Manual Deploy For SPFx 1.1.0 (SP 2016 on Prem)

For Users who would prefer to manually deploy assets after deploying “imDocShare.sppkg” to the App Catalog, please follow the instructions below.

Using the Site Assets library is generally recommended as it is common among all site collections.

Now, you must create this directory and populate it with the assets that the WebPart needs to function. Its recommended to create a folder named “imDocShare” in order to keep different app assets separate

Copy any applicable Json and JS files required to load the WebPart.

Also copy any static assets such as icons or fonts into this folder. It should look something like this:

Finally, you can see that we have created this directory in the Site Collection’s “Site Assets” library within a folder we created called “imDocShare”. In the image below, you can see our WebPart retrieving icons from this location in the highlighted src link.

In order to properly retrieve these assets, a config value called “assetPath” must be included in each webpart config. Your assetPath should look like: https://{yourSharepointTenant}/SiteAssets/imDocShare/folderIcons/

This path must point to the location where your JS files and static assets have been deployed on SharePoint.

Uninstalling and Updating

In this step, you are updating the sppkg file. This is one of the last steps in the deployment process. Here all you need to do is backup the current sppkg file if applicable, and then delete it. If backing up, all that is necessary is to download the current file using the context menu depicted in the figure below. Similarly, the delete option can also be found in the same context menu. Once that is complete, click the “upload’ button towards the top of the screen, and pick your newly created .sppkg file.

Configuring imDocShare WebParts

Whether you are deploying to a modern page (SPO) or classic page (SPO) on SharePoint Online or SharePoint Server 2016/2019 on-Premises, the WebPart configuration process should remain the same. When you have added a WebPart in “Edit Mode”, each WebPart will have a small individual “Edit web part” button either on the top right-hand side or top left-hand side. Clicking this button will open a panel on the right side of the screen where you can input configurations.

Note: Make sure that the page created for the webpart is specifically a “webpart page” instead of “wiki page,” which is the default option. Clicking “new” to create a new page will default to wiki page. Using imDocShare webparts on a wiki page is generally supported but may result in unexpected behavior in some situations.

For Modern Pages

Modern pages have a special functionality which will automatically open the config builder in a popup window and import all existing settings to edit.

Clicking “Open config builder” will open a popup window in which you currently existing settings will be automatically imported for you to edit and update.

For Classic Pages

For classic, make sure to find the ribbon on the top and click Page > “Edit” to activate edit mode. Then find the individual dropdown menu on the top right of each WebPart:

Classic Mode does not support the popup config builder at the moment, so it is useful to create a new page just for the config builder. Here is the most simple config to create a config builder webpart:

{“viewType”: “createConfig”, “assetPath”: “/siteAssets/imDocShare/folderIcons”}

Once this config builder page has been created, it can be used to create all other configs.

Configuring imDocShare WebPart Settings

Different imDocShare WebParts have many different properties/settings that can be configured easily by using the imDocShare JSON Config Editor. You can enter your desired configs into the editor, and it will generate a piece of text that you can copy/paste into the WebPart JSON Settings. To see a list of all supported properties and related values refer to the document “IManage SPFx WebParts User Guide”.

Updating your Deployment Package

Occasionally, we may provide an update package that improves functionality or adds new features to the imDocShare product. In this case, users will need to deploy the new sppkg file using the steps below. Note that this process should not disturb webparts that have already been set up using our previous build.

SharePoint Online

Simply delete the previous .sppkg file from your App Catalog’s list of apps. And then upload the newest sppkg that we have provided. No other action needs to be taken. The update will apply immediately to all webparts created using imDocShare. During the time when the sppkg is deleted, users will not be able to use the webparts. Please ensure that you have backed up the previous sppkg file before deleting in case any errors or issues occur. It may take SharePoint Online 1-5 minutes to update all the assets on the server side.

SharePoint On Prem

After receiving our deploy package, please go through the same process found in the section entitled “Deploying to SharePoint On-Premises”. As a summary:

Delete the previous sppkg file from the app catalog

Run the ps1 install file after changing the library locations to reference your desired deploy location

The script will open your app catalog. Click on the imDocShare package and select the “Deploy” option from the top ribbon

There is no need to re-add the app to your site collection as it is already added. Simply visit your webpart page to see the updates

Please be aware that there may be invisible webparts on existing page webpart pages. These invisible web parts are created when a user does not finish the set-up process of a new webpart. This may cause authorization issues because invisible webparts are also loading code. You can delete these webparts by navigating to Site contents > Site Pages, and click on the page that you wish to check. Once there, go to properties, and click the link “open webpart page in maintenance view”.

END-USER imDocShare LICENSE AGREEMENT

This is a Legally binding agreement between you (either an individual or a single entity) and KLoBot, Inc. (“KLoBot”) for the “imDocShare” Software and associated media and printed materials, and many include online or electronic documentation for imDocShare Software Product or imDocShare Software (collectively “imDocShare”). By installing, copying or otherwise using imDocShare, you are agreeing to be bound by the terms and conditions of this agreement, including imDocShare license and disclaimer of imDocShare software warranty below. Please read this document carefully before using imDocShare. If you do not agree with the terms and conditions of this agreement you should not install or use imDocShare.

1. GRANT OF LICENSE; imDocShare USE RESTRICTIONS.
In consideration for your payment of any applicable license fee for imDocShare, KLoBot hereby grants to you a personal, non-transferable (except as expressly provided in Section 4 below) and non-exclusive right to use and execute imDocShare on a single Microsoft Office 365 SharePoint Online Tenant or Microsoft SharePoint on-premises farm (collectively “tenant”), without right to sublicense imDocShare. Under no circumstance may you store, use or allow the use of imDocShare in any manner on more than one tenant at a time. You agree that you will not reverse engineer, decompile or disassemble any portion of imDocShare. If you dispose of any media or apparatus containing imDocShare, you will ensure that you have completely erased or otherwise destroyed any imDocShare contained on such media or stored in such apparatus. Except as expressly provided in Section 4 below, you may not distribute, lease, transfer for profit, loan or otherwise convey imDocShare or any portion thereof to anyone.

2. COPYING RESTRICTIONS.
In order to effect your license rights hereunder, you may install imDocShare by copying it onto the tenant for use thereon, and you may make full or partial copies of imDocShare, but only as necessary for backup or archival purposes. You agree that

(i) your use and possession of such copies shall be solely under the terms and conditions of this Agreement, and

(ii) you shall place the same proprietary and copyright notices and legends on all such copies as included by KLoBot on the authorized copy of imDocShare that you downloaded from the imDocShare web site.

3. OWNERSHIP OF imDocShare AND MEDIA.
You agree and acknowledge that KLoBot transfers no ownership interest in imDocShare, in the intellectual property in any imDocShare or in any imDocShare copy, to you under this Agreement or otherwise, and that KLoBot and its licensors reserve all rights not expressly granted to you hereunder. After you pay any applicable license fees and/or the purchase price of the applicable KLoBot, you will own the media on which imDocShare was originally provided to you hereunder and on which you subsequently copy imDocShare, but KLoBot and its licensors shall retain ownership of all imDocShare and copies of imDocShare or portions thereof embodied in or on such media.

4. TRANSFER RESTRICTIONS.
If you transfer ownership of imDocShare you may transfer imDocShare and all licenses and rights in imDocShare granted to you under this Agreement to the transferee provided that:

(i) such transferee agrees in writing to accept the terms and conditions of this Agreement, and

(ii) you also transfer all imDocShare, including all copies thereof, to such transferee. Except as provided in this Section, you may not sublicense, transfer or assign this Agreement or any of your rights or obligations under this agreement, in whole or in part.

5. U.S. GOVERNMENT USERS.
If imDocShare is acquired by or on behalf of an entity of government of the United States of America, the following provision applies: U.S. GOVERNMENT RESTRICTED RIGHTS LEGEND. Use, duplication or disclosure of SOFTWARE by the Government is subject to restrictions as set forth in FAR 52.227.19( c)(2) or subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer SOFTWARE clause at DFARS 252.227.7013 and/or in similar or successor clauses in the FAR or the DOD or NASA FAR Supplement. Unpublished rights reserved under the Copyright Laws of the United States. Contractor/manufacturer is KLoBot, Inc.

6. EXPORT RESTRICTIONS.
The software is exported from the United States in accordance with the Export Administration Regulations. Diversion contrary to U.S. law is prohibited. You agree that you will not:

(i) export or re-export the software, directly or indirectly, to Iran, Syria, Sudan, Cuba or North Korea; or

(ii) release the software to a person on the denied persons list, unverified list, entity list, specially designated nationals list, debarred list or nonproliferation sanctions list (see http://www.bis.doc.gov/complianceandenforcement/liststocheck.htm ). The foregoing obligations will apply to you unless the Office of Export Licensing of the U.S. Department of Commerce has granted authorization to you in writing for the export or re-export of the software. Your obligations under this section shall survive any termination of this Agreement.

7. ENFORCEMENT OF TERMS; TERMINATION.
If you fail to fulfill any of your material obligations under this Agreement, KLoBot and/or its licensors may pursue all available legal remedies to enforce this Agreement, and KLoBot may, at any time after your default of this Agreement, terminate this Agreement and all licenses and rights granted to you under this Agreement. You agree that KLoBot licensors referenced in imDocShare are third-party beneficiaries of this Agreement and may enforce this Agreement as it relates to their intellectual property. You further agree that, if KLoBot terminates this Agreement for your default, you will, within thirty (30) days after any such termination, deliver to KLoBot or render unusable all imDocShare originally provided to you hereunder and any copies thereof embodied in any medium.

8. DISCLAIMER OF SOFTWARE WARRANTY.
KLoBot PROVIDES imDocShare TO YOU AS IS AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY ANY KLoBot EMPLOYEE, REPRESENTATIVE OR DISTRIBUTOR WILL CREATE A WARRANTY FOR THE imDocShare, AND YOU MAY NOT RELY ON ANY SUCH INFORMATION OR ADVICE.

9. INTELLECTUAL PROPERTY RIGHTS PROTECTION.
If any third party brings a suit against you that is based on a claim that imDocShare, solely as furnished to you under this Agreement, constitutes direct infringement of any patent issued by, or copyright registered in, the United states, KLoBot shall defend such suit or proceeding and shall pay any damages and costs finally awarded therein against you with respect to such matter, provided that you promptly inform KLoBot of any such claim, furnish KLoBot with a copy of each communication, notice or other action relating to the alleged infringement and give KLoBot the authority, information and assistance necessary to settle, compromise or litigate such suit or proceeding. Following notice of a claim or a threatened or actual suit, KLoBot may, without obligation to do so, at KLoBot sole option:

(a) procure for you the right to continue to use imDocShare as furnished,

(b) replace or modify imDocShare to make it non-infringing, or

(c) discontinue your license for imDocShare and refund to you any license fee that you paid for it, less a reasonable value for use, determined by prorating such license fee on the basis of a thirty-six (36) month straight line depreciation method, applied to the period of actual use.

KLoBot shall not be obligated to defend or be liable for costs and damages if the infringement or claim thereof arises out of:

(i) use or combination of imDocShare with products or data not provided by KLoBot,

(ii) use of other than the latest unmodified release of imDocShare made available to you by KLoBot if such infringement would have been avoided by the use of such release of imDocShare,

(iii) modification of imDocShare by anyone by KLoBot,

(iv) use of imDocShare after receiving notice, or having reason to believe, that imDocShare infringes a patent or copyright of a third party, or

(v) a claim based on any portion of the Windows(r) software that may be included with imDocShare.

THE FOREGOING STATES YOUR EXCLUSIVE REMEDY AND KLoBot ENTIRE LIABILITY WITH RESPECT TO INFRINGEMENT OF ANY PATENT OR COPYRIGHT BY imDocShare, AND KLoBot SHALL HAVE NO LIABILITY WITH RESPECT TO ANY OTHER INTELLECTUAL PROPERTY RIGHT.

10. GOVERNING LAW.
This Agreement shall be governed by and interpreted in accordance with New Jersey law, excluding its choice of law rules.

11. TECHNICAL SUPPORT TERMS.

Definitions.As used herein the following capitalized terms have the meanings set forth below:

“Correction” means, without limitation, a workaround, maintenance release, patch and/or documentation change, as KLoBot deems appropriate.
“Defect” means a material failure of imDocShare to operate substantially in accordance with the applicable user guides and reference manuals.
“Update” means a maintenance or minor release of imDocShare that provides corrections or performance improvements, is designated by KLoBot as an Update and is generally made available to all KLoBot technical support customers.
“Upgrade” means a major release of imDocShare that provides new features or functional enhancement, is designated by KLoBot as an Upgrade and is generally made available to KLoBot Premium technical support customers.

Technical Support.

During any 12/24/36-month support period for which you have pre-paid the required premium support payment, KLoBot will provide you:

Notification, if you have requested to be notified, when Updates are available for downloading from imDocShare website at www.imDocShare.com ;
Notification, if you have requested to be notified, when Upgrades are available for downloading from KLoBot’ website; and
Access to My imDocShare Support Portal on KLoBot’ website through which you may:

- Download Updates when commercially available;
- Download Upgrades (Premium technical support customers only) when commercially available;
- Report Defects in imDocShare and obtain Corrections as described herein and in accordance with the types of response and timing referenced on KLoBot’ website;
- Request General advice on implementation, operation, functionality and use of imDocShare as described on KLoBot’ website;
- Participate in community forums, review KLoBot’ extensive knowledge base and obtain usage tips and other useful information regarding imDocShare, including up-to-date information on current releases, product compatibility, restrictions, enhancements, workarounds and fixes; and
- Access on-line documentation regarding imDocShare, including application notes that include installation instructions, release notes and Frequently Asked Questions (FAQs).

Defect Correction.

When you report a suspected Defect in imDocShare to KLoBot using its My imDocShare Support Portal, KLoBot will attempt, based upon information provided by you, to recreate the suspected Defect. If the Defect is confirmed, KLoBot will use commercially reasonable efforts, given the nature and scope of the Defect, to make available to you through the My imDocShare Support Portal a Correction in accordance with the guidelines set forth on KLoBot’ website. KLoBot will make available to Premium technical support customers live chat, telephone call back and live meeting support as appropriate and warranted to confirm Defects and develop Corrections.
KLoBot will not be responsible for correcting Defects in any release of imDocShare other than the most recent release of imDocShare, provided that KLoBot shall continue to support the prior release superseded by recent release for a reasonable period sufficient to allow Premium technical support customers to implement the newest release or until the end of the current non-Premium technical support period.
You agree to implement within a reasonable time all Corrections provided by KLoBot hereunder.

Limitations.

KLoBot will not be obligated to provide technical support relating to problems, errors or malfunctions caused by

malfunction of the computer system and communications network on which you have installed and are using imDocShare,
other software installed in the same SharePoint environment not licensed pursuant to this Agreement,
any use of imDocShare in disregard of any known adverse consequences, including without limitation the failure of user to make appropriate backups, warning messages, and other written instructions,
any modification to imDocShare not authorized by KLoBot,
Mainstream Support of a given SharePoint Platform has been retired by Microsoft, or
any other cause not attributable to KLoBot.

Renewal of Support.

KLoBot provides the first year of basic technical support for no additional charge. Unless renewed in accordance herewith, basic technical support will cease on the last day of the 12-month support period that commenced upon the effective date of imDocShare license.
For an additional fee, you may obtain Premium technical support. Unless renewed in accordance herewith, Premium technical support will cease on the last day of the support period for which you have paid the additional Premium technical support fee.
Support fees for additional support periods must be paid in advance on or prior to last day of the support period for which you have paid the required support fee.
Approximately forty-five (45) days prior to the termination of the then current support period, KLoBot will invoice you for renewal of technical support. The support fee due for the next support period shall be KLoBot’ then current applicable list price for renewal of technical support as of the date of invoice.
KLoBot reserves the right to withdraw technical support of imDocShare, and to alter the prices, terms and conditions for technical support in advance of any renewal of support. Any such withdrawal or alterations will become effective as of such renewal date.

Reinstatement of Support.

If you allow technical support to expire, in order to reinstate support of imDocShare, you may be required to pay to KLoBot a reinstatement support fee, the then current annual support fee, and, If you are not licensing the then current release of imDocShare, an upgrade license fee for the current release of imDocShare.
Required Identifier.

In order to access My imDocShare Support Portal you must provide the identifier issued to you when you licensed imDocShare. Upon entry of such identifier access will be granted if you have paid in full the required maintenance fee.
Termination of Technical Support.

Notwithstanding Section 4 above, resale, assignment, or transfer of the technical support provided by KLoBot is strictly prohibited and will be grounds for termination of the technical support.