Sometimes presented as right click context menu options, other times as icon on toolbar.  The can be configured to pass profile data e.g. client no, folder information or documentID's for upload to Sysero etc.

Below is just an example further details are available in iManage Developer Documentation.

First we need to create a zip file that will be uploaded to iManage via IMCC or sent to iManage if Cloud instance.  A zip file is attached to this KB article to assist in understanding the below steps:

1. In the below when I use word Example obviously you can replace with client name.  Also note this zip is case sensitive in text and file names etc.
2. Create a folder called SyseroExampleExtension.
3. In that folder create sub folders web_extensions and resources.
4. In the SyseroExampleExtension root folder create a file called mainfest.yaml, in that file add the following lines:
   
   1. api_key: copy your own GUID here (note down)
   2. api_secret: copy your own GUID here (note down)
   3. # Details
   4. id: SyseroExampleExtension
   5. name: Sysero Example Extension
   6. publisher: Sysero
   7. version: 1
   8. # Authentication
   9. redirect_url: http://www.example.com/login2.aspx
   10. # Web actions
   11. web_extensions:
   12. - SyseroExample (Note there can be multiple lines of web_extensions in same zip, just use unique name and new line with - in front and persist same spacing).
5. In the sub folder web_extensions create a text file matching the web_extensions you set in the manifest e.g. SyseroExample.yaml.
6. File needs to contain the following:
   
   1. id: SyseroExample (match file name without extension)
   2. title: Sysero Example (what will appear in iManage)
   3. type: window
   4. url: http://www.example.com/worksite/url.aspx?id=syseroexample
   5. menu: [folder, workspace]
7. In the resources sub folder you can add images named e.g. SyseroExample_disabled.svg and SyseroExample_enabled.svg to show icon in iManage.  This must be an SVG and must match the web_extension name.  Note disabled and enabled text is case sensitive.
8. Lastly in attached SyseroExample.zip it has an example of using the SyseroExample.js to hide or show the extension based on iManage context.
9. Zip file up from within SyseroExampleExtension directory.  Name the .zip something like SyseroExampleExtension.zip.
10. If on prem install follow the instructions below:
    1. Go to iManage Work home /imcc.
    2. Go to Configure > System Setup > Applications.
    3. Click Add Application.
    4. Upload zip file.
11. If cloud install please see article iManage Cloud Requesting new App Registration for Client

How the extension works:

1. You configure the iManage extension to point to a URL on the Sysero server e.g. http://www.example.com/worksite/url.aspx?id=demo
2. The ID will match a setting in Sysero > Admin > System > iManage Work Settings.
3. App setting may look something like one of these:
   • https://www.example.com/editclaimtabbed.aspx?companyid=1&applicationid=3&listitemtransaction=true&runtemplatepackid=2&textfield33=Yes&textfield34=[custom1]&textfield35=[custom2]
   • https://www.example.com/indexsearch.aspx?companyid=1&showarchived=false&application=1147&k=&Passthrough=Matter%CE%A9[custom2]%CE%94ItemName%CE%A9Test
   • https://www.example.com/worksiteupload.aspx?ApplicationID=1147&CompanyID=1&DocumentID=[documentid] (only works with Own Credentials)
   • https://www.example.com/ListContents.aspx?companyid=1&Passthrough=Matter%CE%A9[custom2]%CE%94ItemName%CE%A9Test
4. The process the above and replace the Psuedo values between [] with the correct values from Worksite.
5. You can always use the External field name if set as an alternative to the static database field name.
6. Note : When using the worksiteupload.aspx you can map fields to form data using Admin > Data Room > Advanced Settings > Worksite Integration > Inbound Field Mappings.