iManage Integration Office Add-in Development
Budget: €30 – €250 EUR
Word Add-in for iManage Metadata Injection
Initial proof of concept.
Purpose:
Develop a simple Word Add-in (modern, web-based) that automatically detects when a document is saved to iManage Work (cloud, version 10.x) via the iManage Work Desktop plugin, and populates specific fields (e.g., Matter, Client, Document Number) in the document based on workspace metadata.
Requirements
Platform & Technology
Must be a modern Office Add-in (OfficeJS/Office Web Add-in), compatible with Word for Windows and ideally Word for Mac/Online.
Developed in JavaScript or TypeScript, using Office.js API.
Deployed as a Task Pane Add-in (side panel).
Integration with iManage Work
Detect when a document is saved to iManage Work using the iManage Work Desktop plugin (i.e., when the user saves the document to an iManage workspace from Word).
Retrieve the unique document or workspace ID (e.g., from a custom document property, filename pattern, or any available method).
Use iManage Work 10 REST API (documentation and Postman collection available) to retrieve workspace/document metadata (e.g., custom1 = Client, custom2 = Matter, docnum = Document Number).
Word Document Interaction
Locate specific Content Controls or Document Properties in the open document (by tag or property name).
Insert or update the following fields in the document with data from iManage:
Client (custom1)
Matter (custom2)
Document Number (docnum)
(Optionally: other custom fields, e.g., Partner, Description, etc.)
User Experience
The add-in should run automatically after saving to iManage, or offer a clear “Update Metadata” button for the user.
Provide feedback (success/error) to the user in the task pane.
If authentication to the iManage REST API is required, leverage existing iManage session (SSO) if possible, or prompt user with a simple login.
Configuration & Deployment
Code and manifest must be provided for sideloading/testing.
Deployment instructions for Office 365 Centralized Deployment must be included.
Any setup steps for iManage REST API access should be documented (including how to obtain required tokens or configure permissions).
Deliverables
Complete Office Add-in project (source code).
Manifest.xml and deployment guide.
Brief user guide for testing and use.
Background Information Provided
iManage Work 10 is cloud-hosted and uses OAuth2 authentication.
REST API documentation (PDF) and Postman collections are available and can be shared.
Example metadata fields: custom1 = Client, custom2 = Matter, docnum = Document Number, etc.
Clarifications
The focus is to demonstrate basic metadata insertion – advanced UI is not required.
Freelancer may suggest best way to detect iManage context and retrieve document/workspace ID.
Initial proof of concept.
Purpose:
Develop a simple Word Add-in (modern, web-based) that automatically detects when a document is saved to iManage Work (cloud, version 10.x) via the iManage Work Desktop plugin, and populates specific fields (e.g., Matter, Client, Document Number) in the document based on workspace metadata.
Requirements
Platform & Technology
Must be a modern Office Add-in (OfficeJS/Office Web Add-in), compatible with Word for Windows and ideally Word for Mac/Online.
Developed in JavaScript or TypeScript, using Office.js API.
Deployed as a Task Pane Add-in (side panel).
Integration with iManage Work
Detect when a document is saved to iManage Work using the iManage Work Desktop plugin (i.e., when the user saves the document to an iManage workspace from Word).
Retrieve the unique document or workspace ID (e.g., from a custom document property, filename pattern, or any available method).
Use iManage Work 10 REST API (documentation and Postman collection available) to retrieve workspace/document metadata (e.g., custom1 = Client, custom2 = Matter, docnum = Document Number).
Word Document Interaction
Locate specific Content Controls or Document Properties in the open document (by tag or property name).
Insert or update the following fields in the document with data from iManage:
Client (custom1)
Matter (custom2)
Document Number (docnum)
(Optionally: other custom fields, e.g., Partner, Description, etc.)
User Experience
The add-in should run automatically after saving to iManage, or offer a clear “Update Metadata” button for the user.
Provide feedback (success/error) to the user in the task pane.
If authentication to the iManage REST API is required, leverage existing iManage session (SSO) if possible, or prompt user with a simple login.
Configuration & Deployment
Code and manifest must be provided for sideloading/testing.
Deployment instructions for Office 365 Centralized Deployment must be included.
Any setup steps for iManage REST API access should be documented (including how to obtain required tokens or configure permissions).
Deliverables
Complete Office Add-in project (source code).
Manifest.xml and deployment guide.
Brief user guide for testing and use.
Background Information Provided
iManage Work 10 is cloud-hosted and uses OAuth2 authentication.
REST API documentation (PDF) and Postman collections are available and can be shared.
Example metadata fields: custom1 = Client, custom2 = Matter, docnum = Document Number, etc.
Clarifications
The focus is to demonstrate basic metadata insertion – advanced UI is not required.
Freelancer may suggest best way to detect iManage context and retrieve document/workspace ID.