iManage.Import.DocClass

Specifies the default document class when saving files to iManage Work as new documents or new versions.

Example: <key name="iManage.Import.DocClass" value="DOC"/>

If the value string is empty, a blank Class field appears in the iManage Save dialog and users are prompted to enter a document class when saving documents.

NOTES:

• This option is applicable only for saving new documents, not for new versions.

• The default doc class and default email class are no longer read from the default classes configured from iManage Work Server. These two values will be read only from the imWorkOptions.xml file. 

• If the iManage.Import.DocClass and iManage.Import.EmailClass options are missing in the file, "DOC" is used as the default document class and "E-MAIL" is used as the default email class.

DOC

iManage.Import.EmailClass

Specifies the default email class and subclass (optional) when saving emails to iManage as new documents or new versions.

NOTE: This setting doesn't apply to file uploads of emails.

Example: <key name="iManage.Import.EmailClass" value="E-Mail"/>

Email

iManage.Import.EmailSubClass

Specifies the default email class subclass when saving emails to iManage Work Desktop for Windows as new documents or new versions.

Example: <key name="iManage.Import.EmailClass" value="E-Mail"/>
<key name="iManage.Import.EmailSubClass" value=""/>

NOTES:

• If no default email class is specified, any default subclass specified will be ignored.

• If a class and subclass are specified in the folder profile, these values are inherited from the folder profile.

• If no class or a subclass is specified in the folder profile, then the default class and subclass from the imWorkOptions.xml file is applied.

"" (no value)

FileSave

Used to map the Microsoft Office's File->Save (idMso) command to a predefined iManage Work command ID—for example, "iManage.WorkSiteSavenSync". By mapping to the "iManage.WorkSiteSavenSync" command, you can save edits to iManage Work when the File->Save operation is performed.

Example: <key name="FileSave" value="iManage.WorkSiteSavenSync"/>

NOTES:

• This setting works for all environments, including Citrix environments. It is used to save changes to iManage Work when a document is saved. 

• By mapping to the existing iManage.WorkSiteSavenSync ribbon ID, edits can be saved to iManage Work when the File > Save operation is performed.

"" (no value)

ValidateCheckoutLocation

Used to validate the location of a checked-out file against the logged in user's current device.

If this value is set to N, only the file's checkout path is validated during check-in.

Example: <key name="ValidateCheckoutLocation" value="Y"/>

NOTE: For users using a multi-user environment like Citrix, the value should be set to N.

Y

EnableMicrosoft365forthedesktop

This setting allows Admins to control the default behavior when users open iManage Work files in Word, Excel, or PowerPoint. The setting affects how documents are accessed and edited collaboratively. These file types can now be accessed in an open state in iManage Work Next Generation Co-authoring, in which the AutoSave feature is enabled, and co-authoring can occur, or files can be opened using the traditional exclusive check-out process:

• With the value set to Disable (the default), iManage documents are opened with the classic checkout model, and the iManage Work Next Generation Co-authoring is not available.

NOTE: The Next Generation Co-authoring is only enabled when this setting is set to one of the two enabled states.

• With the value set toEnable-M365forthedesktopAsDefault, iManage files are opened in co-authoring mode with AutoSave enabled. The Co-authoring toggle is visible on the ribbon, enabling the user to switch to exclusive checkout.

• With the value set to Enable-ExclusiveCheckoutAsDefault, iManage Work files are opened with the traditional checkout process, locking the file. The Co-authoring toggle button is visible on the ribbon, enabling the user to switch to Next Generation Co-authoring mode if desired.

Example: <key name=“EnableMicrosoft365forthedesktop” value=”Enable-M365forthedesktopAsDefault”/>

Disable

iwOnlyKeepLatestVersionatLocal

Ensures that only one version of the file is kept in the "Recent" directory. By default, whenever you save the document as a new version, the previous version of the document will be deleted from your local directory.

Valid values:

• Y or N

• true or false

Example: <key name="iwOnlyKeepLatestVersionatLocal" value="Y"/>

Y

iwCopyCommentsFromPreviousVersion

Ensures version comments are copied over from previous version when a new version is created using Microsoft Office applications. 

• With the value set to Y, when saving the document as a new version, the comments from the previous versions are carried over to the new version of the document. For example, when saving version 2 of the document to create version 3, all the comments from version 2 are carried over to version 3.

• With the value set to N, when saving the document as a new version, no comments are carried over from previous versions of the document. For example, when saving version 2 to create version 3 does not carry any comments from version 2. 

When the value is Y, the comments are carried over only when users are creating a new version of the document using Microsoft Office integration. If the users upload a new version using the right-click context menu from iManage Work or iManage Work Panel in Microsoft Outlook, the comments aren't carried over from previous version.

If users are saving a new version of a document by using smart documents or by saving attachments from an email, the comments from the previous version aren't carried over. This is because when using Microsoft Office integration, users are typically creating a new version of an existing document. However, when uploading a new version from the web, it's a new document. Similarly, uploading Smart Attachments is a new file. Hence, the comments aren't carried over from previous version. Instead, the sender information and date/time stamp are placed in the comments.

NOTES: 

• This setting doesn't apply when using the Upload as New version option from iManage Work or iManage Work Panel. This is because the user is uploading a new document as a new version instead of editing a previous version.

• Also, when an email attachment is saved as a new version, the comments will continue to display the sender information—for example, Sent by Jerry Isaac jIsaac@imanage.com on 4/26/2024 2:20:43 PM.

Example: <key name="iwCopyCommentsFromPreviousVersion" value="Y"/>

Y

iwFileCaptionFormat

Specifies the document caption format in the Microsoft Office applications: Word, Excel, and PowerPoint. The value can be combined with other text or characters. It uses the members of the WSProfileAttributeID enumeration, enclosed with brackets { and }.

Example: <key name="iwFileCaptionFormat" value="#{imProfileDocNum}v{imProfileVersion}<{imProfileDatabase}> - {imProfileDescription}" />

#{imProfileDocNum}v{imProfileVersion}<{imProfileDatabase}> - {imProfileDescription}

SaveAsPDFDefaultDisposition

Specifies the default disposition for documents that are saved as a PDF. 

The valid values are new version and new document. 

Example: <key name="SaveAsPDFDefaultDisposition" value=""/> 

• If the value defined is invalid, it takes the default value: none.

• If the value isn't defined, and:

  • the user saves an existing iManage Work document as PDF, both the New Version and New Document options are enabled in the Save As PDF Options dialog. New Version is selected by default. 

  • the user saves a new document as PDF, the New Document option is enabled and selected in the Save As PDF Options dialog. The New Version option is disabled.  

• If the value defined is new version, and:

  • the user saves a new document as PDF, the New Document option is enabled and selected by default. The New Version option is disabled. 

  • the user saves a iManage Work document, both the New Document and New Version options are enabled, and the New Version option is selected by default. 

• If the value defined is new document and:

  • the user saves an existing iManage Work document, both the New Document and New Version options are enabled, and the New Document option is selected by default. Also, the Relate to original check box is selected by default.

  • the user saves a new document, both the New Document and New Version options are enabled, and New Document option is selected by default.

"" (no value)

iwBackstageFileFormatSection1

Used for displaying the first part of the document details string in the Backstage view. It uses the members of the WSProfileAttributeID enumeration, enclosed with brackets { and }.

Example: <key name="iwBackstageFileFormatSection1" value="{imProfileDescription}.{imProfileExtension}"/>

{imProfileDescription}.{imProfileExtension}

iwBackstageFileFormatSection2

Used for displaying the second part of the document details string in the Backstage view. It uses the members of the WSProfileAttributeID enumeration, enclosed with brackets { and }.

Example: <key name="iwBackstageFileFormatSection2" value="| v{imProfileVersion} | #{imProfileDocNum} | {imProfileAuthor} | {imProfileEditDate} | {imProfileSize}"/>

| v{imProfileVersion} | #{imProfileDocNum} | {imProfileAuthor} | {imProfileEditDate} | {imProfileSize}

iwFileShortcutFormat

Used for displaying the shortcut of files under My Favorites in the Backstage view; the default value will be the description only. It uses the members of the WSProfileAttributeID enumeration, enclosed with brackets { and }.

Example: <key name="iwFileShortcutFormat" value="{imProfileDescription}"/>

{imProfileDescription}

iwFileShortcutDescriptionFormat

Used for displaying a shortcut document's target information. The same string can also be found in iwAddinExtensionRes.dll. It uses the members of the WSProfileAttributeID enumeration, enclosed with brackets { and }.

Example: <key name="iwFileShortcutDescriptionFormat" value="Shortcut to document {imProfileDocNum} in library {imProfileDatabase}"/>

Shortcut to document {imProfileDocNum} in library {imProfileDatabase}

iwAttachmentFileNameFormat

Formats the file name information when sending it as an email attachment. This applies to both the NRL and the document attachment.

Example: <key name="iwAttachmentFileNameFormat" value="{imProfileDescription}({imProfileDatabase}.{imProfileDocNum}.{imProfileVersion}.{imProfileExtension})" />

{imProfileDescription}({imProfileDocNum}.{imProfileVersion}.{imProfileExtension})

iwSaveAttachmentAsNewVersion.SelectAllFilterByDefault 

This option ensures that all supported file formats are shown by default in the dialog used when saving a document. If not specified, the default behavior is to filter the document list based on the extension of the selected attachment.

Example: <key name="iwSaveAttachmentAsNewVersion.SelectAllFilterByDefault" value="N"/>

N

iwSaveAttachmentAsNewVersion.SelectAllFilterByDefault.ForPdf

This provides the same functionality as iwSaveAttachmentAsNewVersion.SelectAllFilterByDefault but applies only to PDF attachments.

N

iwSaveAsNewVersionInAcrobat.SelectAllFilterByDefault

This option ensures that all supported file formats are shown by default in the Select a File dialog when saving a PDF file as a new version. 

Example: <key name="iwSaveAsNewVersionInAcrobat.SelectAllFilterByDefault" value="N"/>

N

iwUseFileName4NewVersion

Sets the new document version's description field based on the local file name, instead of using the description of the existing version.

Valid values:

• Y or N

• true or false

Example: <key name="iwUseFileName4NewVersion" value ="N"/>

N

iwPurgeRecentAgeThreshold

Whenever you open a file from iManage Work using the iManage Work Desktop for Windows application, a copy of the file is downloaded to the %AppData%\Roaming\iManage\Work\Recent folder. Unless deleted manually, the files remained in the folder. To prevent files from accumulating and unnecessarily increasing hard disk space usage and to prevent the risk of accidentally deleting files that were taken offline, the Purge feature automatically removes files that are older than a configurable number of days from the Recent folder.

Minimum value: 1

Example: <key name="iwPurgeRecentAgeThreshold" value ="30"/>

NOTES:

• System or hidden files, such as, .ini, .prf, and .cmt are not purged.

• iManage files that are checked out, modified offline, or newly created offline are excluded.

• Purged files are moved to the local recycle bin instead of being permanently deleted.

30

iwAllowIWLCallsFromSpecifiedBrowsers

This option can be used to control which web browsers are allowed to make direct iwl:// calls. Microsoft Edge, Chrome, and Firefox are enabled by default. This is for the integration between the browser and the iManage Work Desktop for Windows to function. Other browsers don't require this support and hence are disabled by default. Disabling this functionality when not required is advised for security reasons.  

This is a comma-delimited list of browser names. Valid values are: edge, firefox, chrome, i explore, and opera.

Example: <key name="iwAllowIWLCallsFromSpecifiedBrowsers" value ="edge"/>

edge,chrome,firefox

iwReEnabledAddinOption

Determines the automatic re-enabling behavior for the disabled iManage add-ins for Microsoft Outlook, Word, PowerPoint, Excel, Visio, and Microsoft Project when you launch the applications the next time.

Valid values:

• 0: Add-ins are automatically enabled and an iManage Work Agent notification is displayed the next time the user launches the applications.

• 1: Add-ins not enabled automatically and users can manually enable them as desired.

• 2: iManage Work Agent prompts the user to enable the add-in the next time the user launches an integrated application. If the user selects Yes, the Agent displays a notification that the add-in is enabled.

Example: <key name="iwReEnabledAddinOption" value ="0"/>

0

iwCheckoutOverdueAgeThreshold

iManage Work Desktop for Windows reminds users that they have documents checked out that they need to check in. By default, users see iManage Agent notifications if documents are left checked out for more than six hours.

Specify the number of hours after which the user is reminded if documents remain checked out.

Example: <key name="iwCheckoutOverdueAgeThreshold" value="6"/>

NOTE: Ensure that the value is not 0. This setting can be enabled or disabled using the following key:

<key name="iwUseCheckoutOverdueReminder" value="Y"/>

6

iwUseCheckoutOverdueReminder

Enable or disable the reminder that warns the user about the documents that remain checked out.

Valid values: Y or N

Example: <key name="iwUseCheckoutOverdueReminder" value="Y"/>

Y

iwDocCloseReminderTimeOfDay

Specify the time of the day when the user is reminded to close the checked out documents. For example, if the user generally leaves office at 6.30 pm, change the default time to 18:30.

Valid values: hour:minute (24-hour format)

Example: <key name="iwDocCloseReminderTimeOfDay" value="16:30"/>

16.30

iwDocCloseReminderSnoozeDuration

Specify the duration in minutes after which the close documents reminder reappears if the user closes it.

Value range: 5-30

Example: <key name="iwDocCloseReminderSnoozeDuration" value="10"/>

10

iwDocCloseReminderMaxSnoozeNum

Specify the number of times the close documents reminder appears before being dismissed for the day.

Value range: 1-10

Example: <key name="iwDocCloseReminderMaxSnoozeNum" value="3"/>

3

iwUseDocCloseReminder

Enable or disable the reminder that warns the user to close the document that remain checked out after the specified time of the day.

Valid values: Y or N

Example: <key name="iwUseDocCloseReminder" value="N"/>

N

iwAdditionalHelpLanguages

Specifies other languages for which help file is available, other than the base set of languages. The value consists of comma-separated list of two-letter ISO language IDs.

Example: <key name="iwAdditionalHelpLanguages" value="en, de, fr, es, pt, ja, zh"/>

"" (no value)

iwFirmID

The value for this key is a unique identifier for that company (usually the firm ID). When enabled, it allows iManage profile fields to be manually inserted in the footer of a Microsoft Word document. The inserted fields are linked to the value specified.

NOTES: 

• The value enables a field drop-down with the header and footer ribbon.

• It applies only to footer in the Microsoft Word document.

• Document properties can be inserted without replacing the existing information. For more information refer to the Inserting document information fields section in iManage Work Desktop for Windows User Guide.

• The property fields inserted are bound to the document metadata as it is specified in your own document management system (DMS). If your document is imported into a DMS belonging to another firm or company, your document metadata will remain in the document. It isn’t replaced by the document metadata of the new firm or company's DMS to which it is imported.

Valid values: English language characters. This has a character limit of 15.

Example: <key name="iwFirmID" value=""/>

A list of default fields available to add to the footer in Microsoft Word when the feature is enabled are specified below. The field names are specified in the value enclosed by curly braces.

These are available under <ws_option name="iManFields">:

• <key name="iManage.Field.Database" value="{imProfileDatabase}"/>

• <key name="iManage.Field.DocNum" value="{imProfileDocNum}"/>

• <key name="iManage.Field.Version" value="{imProfileVersion}" />

• <key name="iManage.Field.Description" value="{imProfileDescription}"/>

• <key name="iManage.Field.Author" value="{imProfileAuthor}"/>

• <key name="iManage.Field.Operator" value="{imProfileOperator}"/>

• <key name="iManage.Field.Custom1" value="{imProfileCustom1}"/>

• <key name="iManage.Field.Custom1Description" value="{imProfileCustom1Description}"/>

• <key name="iManage.Field.Custom2" value="{imProfileCustom2}"/>

• <key name="iManage.Field.Custom2Description" value="{imProfileCustom2Description}"/>

• <key name="iManage.Field.EditDate" value="{imProfileEditDate}"/>

You can add fields by adding the value to a key in the same syntax.

For example, to add the imProfileDatabase field, enter imProfileDatabase as the value with the appropriate key name, under <ws_option name="iManFields">.

<key name="iManage.Profile.Database" value="{imProfileDatabase}"/>

For a complete list of fields, refer to WSProfileAttributeID Enumerators.

"" (no value)

iwLocale

Sets the locale for the iManage Work Desktop Windows in Microsoft Office and Microsoft Outlook. The value provided within the empty string overrides the configured Windows display language for Microsoft Windows.

If the strings are empty (default setting), the Windows display ‌language that is specified using the regional setting in the Control Panel in Microsoft Windows applies. The value can be any language that iManage Work Desktop for Windows supports.

Empty strings ("") are provided to add the locale value as desired. The value must be specified in "languagecode-country/regioncode" format, where:

• languagecode is a lowercase two-letter code derived from ISO 639-1, and

• country/regioncode is derived from ISO 3166 and usually consists of two uppercase letters, or a BCP-47 language tag.

Example:

To display the application in Spanish, use the following setting:

<ws_option>
<key name="iwLocale" value="es-ES"/>
</ws_option>

Similarly, to display the application in Japanese, use the following setting:

<ws_option>
<key name="iwLocale" value="ja-JP"/>
</ws_option>

NOTES:

• The supported languages are English (en-US and en-GB), Spanish (es-ES), German (de-DE), Portuguese-Brazil (pt-PT), French-France (fr-FR), Simplified Chinese (zh-CN), Canadian French (fr-CA), and Japanese (ja-JP).

• If a value specified for iwLocale is a valid locale setting, for example—Italian (it-IT), but not supported by iManage Work Desktop for Windows, then the application is displayed in English.

• If the value specified for iwLocale isn't a valid locale setting, for example— es-US, then the application is displayed in the Windows display language.

"" (no value)

iwTestServerDomains

Used to identify non-production servers that have data analytics feature enabled.

Example: <key name="iwTestServerDomains" value=".test1.com"/>

"" (no value)

iwAutologinOnAgentStartup

Enables authentication to iManage Work without user interference when iManage Work Agent starts. 

Valid values:

• Y: enabled

• N: disabled

• blank "" (let iManage decide).

If enabled, you can also configure a delay in seconds before attempting authentication.

Example:

<key name="iwAutologinOnAgentStartup" value="Y"/>
<key name="iwAutologinOnAgentStartupDelayInSeconds" value="0"/>

N

iManageEnhancedAccessibility

Enables or disables iManage Work enhanced accessibility functions in iManage Work Desktop for Windows. For example, tab-stoppable label in the message box. 

Valid values:

• Y: enabled

• N or "": disabled

<key name="iManageEnhancedAccessibility" value =""/>

"" (no value)

iwResetWebView2CacheFolderOnStartup

This option controls whether cached WebView2 data is used when starting an integrated application.

The WebView2 cache writes to "C:\Users\username\AppData\Local\Temp\iManage\WebView2"

Valid values:

• Y : Prevents Work Desktop for Windows from recycling cached information.

• N or "" : Cached information is reused.

Example: <key name="iwResetWebView2CacheFolderOnStartup" value="Y"/>

"" (no value)

OpenAsReadOnlyTypes

This option ensures documents with the specific matching type are opened as read-only. Users can add or remove any document type (separated by comma) which needs to be opened as read-only by using this setting.

Example:  <key name="OpenAsReadOnlyTypes" value="MIME,NOTES,GW,ZIP" />

NOTE: OpenAsReadOnlyTypes takes precedence over OpenAsEditByTypes.

"MIME,NOTES,GW,ZIP"

OpenAsEditByTypes

Document NRLs open in Protected Mode/Protected View by default. Add the specific File Type Alias to this setting to make those associated NRLs open in Edit Mode. This setting replaces the previous NRL Shell Open Command modification in the registry. This setting applies to PDF and Office applications.

Example: <key name="OpenAsEditByTypes" value="ACROBAT,WORD,WORDX,EXCEL,EXCELX,PPT,PPTX" />

"ACROBAT"

EnableSmartAttachment

Lets you turn on or turn off the smart attachment feature for Microsoft Office documents when custom XML with cloud information is embedded into the document attached to email.

NOTE: If a user opens and edits a document that was opened using smart attachment, the user will be prompted to save their changes when closing the document, as shown in the following example.

Valid options:

• 1: enabled 

• 0: disabled

Example:
"EnableSmartAttachment": 1

1

DNSFlushBeforeTokenGet

Clear the DNS cache and close the connection group before getting the refresh token. Could be useful for VPN users.

Valid options:

• Y: enabled

• N or "" (blank): disabled

"" (no value)

iwAttemptOpen

Configures the on-screen text for the Open action available within the iManage Work Open dialog box. You can set the values of these keys to any desired string. For example, the iwAttemptOpen key can be set to "Open My Document".

Example: <key name="iwAttemptOpen" value="Open" />

Default options:

After setting the iwAttemptOpen key to "Open My Document":

Open

iwAttemptOpenReadOnly

Configures the on-screen text for the Open Read-Only action available within the iManage Work Open dialog.

Example: <key name="iwAttemptOpenReadOnly" value="Open Read-Only" />

Open Read-Only

iwAttemptOpenasCopy

Configures the on-screen text for the Open As Copy action available within the iManage Work Open dialog.

Example: <key name="iwAttemptOpenasCopy" value="Open as Copy" />

Open as Copy

iwAttemptOpeninProtected

Configures the on-screen text for the Open in Protected View action available within the iManage Work Open dialog.

Example: <key name="iwAttemptOpeninProtected" value="Open in Protected View" />

Open in Protected View

EnableExplicitComRelease

This option provides an optional workaround for the conflicting requirements for Microsoft Word.

Use value Y if you're using OLE actions that embed Microsoft Word documents.

Use value N if you have issues with iManage Save buttons in low-memory environments.

Y

EnableEventsWhenEmbedded

NOTE: This workaround causes the WorkbookBeforeSave and WorkbookAfterSave events to trigger twice when you try to save the workbook using the Microsoft Excel object model.

Use value Y in the case you’re experiencing issues using OLE actions that embed Microsoft Word documents.

Use value N if you have issues with iManage Save buttons in low-memory environments.

N

EnableResaveWithLocale

This setting enables a workaround for currency and date formatting issues when working with Excel files across multiple different locales.

N

iwAttemptInsertLink2Latest

These settings provide the default options in the iManage Work Browse dialog box to insert the selected document as a hyperlink (IWL link). The first option inserts the link to the latest version of the selected document, and the second option inserts
the link to the current version of the document. You can set the values of these keys to any desired string. For example, the iwAttemptInsertLink2Latest key can be set to My Latest Document.

Example:

<key name="iwAttemptInsertLink2Latest" value="Latest" />

Latest

iwAttemptInsertLink2ThisVersion

Example:
<key name="iwAttemptInsertLink2ThisVersion" value="This Version" />

This Version

EnableAuditWordPrint

Enable audit history events related to the print operation for Microsoft Word.

Example: <key name="EnableAuditWordPrint" value="Y"/>

Y

EnableAuditExcelPrint

Enable audit history events related to the print operation for Microsoft Excel.

Example: <key name="EnableAuditExcelPrint" value="Y"/>

Y

EnableAuditPowerPointPrint

Enable audit history events related to the print operation for Microsoft PowerPoint.

Example: <key name="EnableAuditPowerPointPrint" value="Y"/>

Y

EnableAuditProjectPrint

Enable audit history events related to the print operation for Microsoft Project.

Example: <key name="EnableAuditProjectPrint" value="Y"/>

Y

AuditWordPrintPages

Log the audit history events related to the print operation for Microsoft Word.

Example: <key name="AuditWordPrintPages" value="IWEnumAuditPrintPageType.All"/>

IWEnumAuditPrintPageType.All

AuditExcelPrintPages

Log the audit history events related to the print operation for Microsoft Excel.

Example: <key name="AuditExcelPrintPages" value="IWEnumAuditPrintPageType.None"/>

IWEnumAuditPrintPageType.None

AuditPowerPointPrintPages

Log the audit history events related to the print operation for Microsoft PowerPoint.

Example: <key name="AuditPowerPointPrintPages" value="IWEnumPrintType.None"/>

IWEnumPrintType.None

EnableAuditWordSaveBeforePrint

Enable audit history events related to the print operation for Microsoft Word.

Example: <key name="EnableAuditWordSaveBeforePrint" value="N"/>

N

WordDocumentOpenFilter

Customize the document type filters that appear in the File Open dialog in Microsoft Word.

The <filter> xml syntax can be used to specify custom filters. Each node represents another filter that should appear in the File Open dialog.

The name attribute of the filter is the label for that filter that'll appear in the user interface.

The types attribute is the comma-delimited list of document types that should be displayed when that filter is selected.

If no types are specified, then that filter will match any document type.

NOTE: The pipe symbol and semicolon characters are reserved and can't be used in a filter name or its associated list of document types.

<filter name="All Word Documents (.docx,.docm,.dotx,.dotm,.doc,.dot,.htm,.html,.rtf,.mht,.mhtml,.xml,*.odt)" types="WORDX,WORDXT,DOCX,DOCM,DOTX,DOTM,WORD,DOT,HTM,HTML,RTF,MHT,MHTML,XML,ODT"/>

ExcelDocumentOpenFilter

Customize the document type filters that appear in the File Open dialog in Microsoft Excel.

<filter name="All Excel Files (.xlsx,.xlsm,.xlsb,.xlam,.xltx,.xltm,.xls,.xlt,.htm,.html,.mht,.mhtml,.xml,.xla,.xlm,.xlw,.odc,.ods)" types="EXCEL,EXCELX,EXCELXT,XLSM,XLSB,XLAM,XLTX,XLTM,XLT,MHT,XLA,XLM,XLW,ODC,ODS"/>

PowerPointDocumentOpenFilter

Customize the document type filters that appear in the File Open dialog in Microsoft PowerPoint.

<filter name="All PowerPoint Presentations (.pptx,.ppt,.pptm,.ppsx,.pps,.ppsm,.potx,.pot,.potm,.odp)" types="PPTX,PPT,PPTM,PPSX,PPS,PPSM,POTX,POT,POTM,ODP,PPTXT"/>

VisioDocumentOpenFilter

Customize the document type filters that appear in the File Open dialog in Microsoft Visio.

<filter name="All Visio Files (.vsdx,.vsdm,.vsd,.vdx,.vssx,.vssm,.vss,.vsx,.vstx,.vstm,.vst,.vtx,.vsw,.vdw)" types="VSDX,VSDM,VSD,VDX,VSSX,VSSM,VSS,VSX,VSTX,VSTM,VST,VTX,VSW,VDW"/>

ProjectDocumentOpenFilter

Customize the document type filters that appear in the File Open dialog in Microsoft Project.

<filter name="All Projects Files (.mpp,.mpt)" types="MPP,MPT"/>

PictureDocumentOpenFilter

Use this configuration to display specific image file types when using the Picture option to insert pictures into Microsoft Word, Excel, and PowerPoint documents from iManage Work.

<filter name="All Picture Files (.emf,.wmf,.jpg,.jpeg,.jfif,.jpe,.png,.bmp,.dib,.rle,.gif,.emz,.wmz,.pcz,.tif,.tiff,.eps,.pct,.pict,.wpg)" types="EMF,WMF,JPG,JPEG,JFIF,JPE,PNG,BMP,DIB,RLE,GIF,EMZ,WMZ,PCZ,TIF,TIFF,EPS,PCT,PICT,WPG"/>

VisioPictureDocumentOpenFilter

Use this configuration to display all the image types when using the Picture option to insert pictures into Microsoft Visio from iManage Work.

<filter name="All Picture Files (.emz,.emf,gif,.jpg,.jpeg,.png,.svg,svgz,.tif,.tiff,*bmp,dib,.wmf)" types="EMZ,EMF,GIF,JPG,JPEG,PNG,SVG,SVGZ,TIF,TIFF,BMP,DIB,WMF"/>

PassiveMode

iManage Work Desktop for Windows supports passive integration mode with Microsoft Office. If PassiveMode is set to Y, upon creating a new document, iManage Work Desktop for Windows won't try to take over the build-in operations unless it's an iManage file. Ribbon buttons don't need to be remapped in this mode and the functionality of the Open and Save operations remain unchanged.

N

AdobeReaderIntegrated

Configure non-integrated mode with Adobe Acrobat Reader. When users check out PDF files from iManage Work, make necessary edits, and close files, all changes made are checked in to iManage Work. This integration helps users who run Adobe Acrobat Pro or Adobe Acrobat Reader in Protective mode to continue working seamlessly on PDF files saved to iManage Work.

Set this value to N to turn on non-integrated mode. 

Users can use non-integrated mode when the iManage Work add-in isn't installed in these applications. Non-integrated mode shouldn't be enabled if iManage Work add-in is already added and is used actively. 

Y

AdobeIntegrated

Configure non-integrated mode with Adobe Acrobat Pro.

Set this value to N to turn on non-integrated mode. 

For more information, refer to AdobeReaderIntegrated.

Y

SaveReadOnlyToiManage

When set to Y, saving a read-only document displays the iManage Save dialog instead of the native Save dialog. This allows users to save read-only documents to iManage Work. 

N

IntegratedProcesses

iManage Work Windows for Desktop has a hard-coded list of integrated applications like Microsoft Office and Adobe Acrobat, and this option extends the list. Integrated processes are expected to check-in documents on their own when the document is closed. The value is the process names separated by a comma.

Example: <key name="IntegratedProcesses" value="NuancePDF"/>

"" (no value)

ResetWordTemplatesAfterKeyboardBinding

Binding keyboard shortcuts to commands in Microsoft Word can cause changes to the Normal template. The iManage add-in for Microsoft Word doesn’t save this change by default.

Use this option to disable resetting the Normal template's Saved status ‌after keyboard binding. By disabling this option, a user might be prompted to save the changes in Normal template when closing the application.

Y

MonitorWordTemplates

Disable monitoring the Microsoft Word template's saved status when closing the file or Microsoft Word.

Y

iwLegacyFilePostConvertionAction

This option saves the Microsoft Office documents that have been changed from old file formats to the latest file formats to iManage Work. It replaces the old document with the latest version automatically.

This option is enabled by default and can be disabled by setting the value to 1.

Example: <key name="iwLegacyFilePostConvertionAction" value ="0"/>

NOTE: If this option is disabled, the converted file format won't be uploaded and the changes will exist only locally. If the file isn't saved to iManage Work, the file in the Recent directory may be corrupted even if the same user tries to download the file again.

0

iManageOleLinking

Enables or disables iManage OLE linking feature in Microsoft Office integration. 

Valid values:

• Y: enabled

• N or "" (blank): disabled 

Example: <key name="iManageOleLinking" value =""/>

"" (no value)

iManBlockUpdateLinkAtOpen

Enables or disables Microsoft Word and Microsoft Excel to prompt user to update links when opening a container file from iManage Work.

Valid values:

• Y: user doesn't see a prompt to update links when opening a container file using the iManage file open picker dialog.

• N or "" (blank): follows Microsoft Word and Microsoft Excel default settings.

Example: <key name="iManBlockUpdateLinkAtOpen" value =""/>

"" (no value)

WordDoNotShowOpenOnMailMerge

Enable or disable Microsoft Word to show the iManage Open dialog when using mail merge (Step-by-Step Mail Wizard).

Example: <key name="WordDoNotShowOpenOnMailMerge" value=""/>

"" (no value)

AllowWordUnsafeSave

Enable or turn off Microsoft Word’s unsafe save option.

N

UpdateOnOpen

Specifies whether to update the footer when documents open. Possible values are Y and N. 

Example: <key name="UpdateOnOpen" value="Y"/>

Y

iwFooterFormat

Specifies the format of the document footer. It uses the members of the WSProfileAttributeID enumeration, with "{" and "}" around them.

For the list of the members of the WSProfileAttributeID enumeration that is used in the iwFooterFormat key and the other keys mentioned in the following text, refer to WSProfileAttributeID enumerators.

More advanced footer integration can be achieved by writing your own custom Microsoft Office add-in, such as merging the iManage footer with your existing custom footers.

For more information, refer to the iManage Work Desktop for Windows SDK Guide.

#{imProfileDocNum}v{imProfileVersion}<{imProfileDatabase}> - {imProfileDescription}

AutoInsert

Specifies whether you want to automatically insert the iManage document profile information into the footer. The auto insert operation is triggered when a new version or a new copy of the document is saved to iManage Work.

When this is enabled, the iManage footer replaces any existing custom footer in documents.

N

SeekAccess

Specifies whether to use footer seek operation for footer content check. Use value Y to avoid insertion of document header and footer for narrow margin documents. Use value N (default) to avoid document scroll on load when the header becomes partially invisible.

N

FontName

Name of the font to use for the footer. 

"" (no value)

FontSize

Font size of the footer. 

"" (no value)

Alignment

Alignment to apply to the footer. Possible values are Right, Left, Center, and Justify. 

"" (no value)

NotificationCountThreshold

Automatically cleans up old notifications from iManage Work Agent when the specified number is reached.

Example: <key name="NotificationCountThreshold" value="50"/>

50

NotificationAgeThreshold

Automatically cleans up old notifications from iManage Work Agent after the specified number of days.

Example: <key name="NotificationAgeThreshold" value="7"/>

7

AttentionCountThreshold

Automatically cleans up old error messages from iManage Work Agent when the specified number is reached.

Example: <key name="AttentionCountThreshold" value="50"/>

50

AttentionAgeThreshold

Automatically cleans up old error messages from iManage Work Agent after the specified number of days.

Example: <key name="AttentionAgeThreshold" value="7"/>

7

NonIntegratedProcesses

Includes a comma-separated list of non-integrated applications that cannot lock the file while editing.

Example: <key name="NonIntegratedProcesses" value="notepad"/>

notepad

RestrictOriginsToRegisteredServers

When enabled, iwl calls through localhost are accepted from the URLs for the user's registered servers. Default is Y.

NOTE:

If you have certain partner integrations, you must add the appropriate urls from the partner tools to the AllowedOrigins option (below), or set RestrictOriginstoRegisteredServers to "N".

Example: <key name="RestrictOriginsToRegisteredServers" value="Y"/>

Y

AllowedOrigins

A comma-separated safe list of additional origins (server URLs) allowed to invoke IWLs through localhost. When not configured and the RestrictOriginsToRegisteredServers option (above) is set to "N" there are no restrictions.

Example: <key name="AllowedOrigins" value=""/>

NOTE:

This must be configured if you have partner applications with URLs involved, and have set RestrictOriginsToRegisteredServers (above) set to "Y".

"" (no value)

HideAgentAutoUpdateMenu

When enabled, Auto Updates-related menu options in the Work Agent are not visible to your end-users.

NOTES: 

• The HideAgentAutoUpdateMenu registry setting in the following location hive is overwritten by this configuration: HKEY_CURRENT_USER\Software\iManage\Work\10.0\Client

• The changed setting applies 1 minute after the Work Agent is restarted or 30 minutes after the option is changed in the configuration file.

Example: <key name="HideAgentAutoUpdateMenu" value="N"/>

N

ListeningPortRange

Range of TCP ports scanned by the iManage Work Agent to secure a free port for communication with iManage Work. 

Example: <key name ="ListeningPortRange" value="17872-21871"/>

17872-21871

AutoUpdateCheckInterval

Frequency in minutes with which the iManage Work Agent should check for auto updates in the background.

Example: <key name="AutoUpdateCheckInterval" value="15"/>

15

ThirdPartyIntegratedProcesses

Lists the third-party applications that can handle the file through iManage Work REST SDK. This allows iManage Work Desktop for Windows to recognize the application so that it can activate the REST SDK feature.

This means once the document is checked out and is opened using a third-party application, the document remains checked out when it’s closed. It doesn't get checked in automatically as the third-party application is responsible for the check-in. 

Example: <key name="ThirdPartyIntegratedProcesses" value=""/>

"" (no value)

EnableAutoUpdateChannelSelection

When set to Y, the user can switch auto-update channel in iManage Work Agent update settings.  

Example: <key name="EnableAutoUpdateChannelSelection" value=""/>

"" (no value)

UpdateCountdownInDays

This option can be used to specify the number of days (grace period) that users should be allowed to install available software updates through iManage Auto Updates functionality.

The countdown begins when an update is available. If users have the option selected to automatically install updates, then updates are installed as soon as they're available and this option doesn’t apply.

Example: <key name="UpdateCountdownInDays" value=""/>

"" (no value)

Enabled

Enables the optional iManage Cost Recovery feature. The Cost Recovery module is available only for:

• customers who have purchased a Cost Recovery license

• on-premises installation of iManage Work Server.

When a user opens an iManage Microsoft Word document and types in a few words, the Cost Recovery module records the time spent by the user editing the document based on the typing activity.

The information is recorded in the DURATION column in the DOCHISTORY table of the iManage Work Server against the Edit Time activity, along with other history details:

• Document number

• Document version

• iManage User who performed the activity

• Time and date this activity was performed

Cost Recovery module documentation is available upon request for licensed customers.

Valid values: Y or N

N

Interval

Specify an interval value in minutes. If the duration between two keystrokes exceeds the value, the time won't be counted as the edit time. The value range is 1 to 60 in minutes.

1

enabled

Enables users to choose the Adobe convertor for saving documents as PDFs to iManage Work using the iManage > Save as PDF option in integrated Microsoft Office applications.

Valid values: Y or N

Example: <key name="Enabled" value="N"/>

N

WebDownloadFileFormat

When downloading multiple files locally, they'll follow this format. This doesn’t apply to single downloads. The files downloaded locally will have its name in the following format: {imProfileDescription}.{imProfileExtension}.

 Example: <key name="WebDownloadFileFormat" value="{imProfileDescription}.{imProfileExtension}"/>

{imProfileDescription}.{imProfileExtension}

WebDownloadVersionFormat

When multiple versions of the same document are downloaded, their name will be formatted as {imProfileDescription}(v{imProfileVersion}).{imProfileExtension}, by default.

Example: <key name="WebDownloadVersionFormat" value="{imProfileDescription}(v{imProfileVersion}).{imProfileExtension}"/>

{imProfileDescription}(v{imProfileVersion}).{imProfileExtension}

WebDownloadPath

Specify a folder where the iManage files will be downloaded when downloading multiple files. By default, the location will be the current user's Downloads directory. Users can also specify a windows directory which may or may not exist locally. For example, <key name="WebDownloadPath" value = @"C:\iMAN" />. If the value is blank, that is, value = "", the user will be prompted to choose a folder.

Example: <key name="WebDownloadPath" value="" />

"" (no value)

WebDownloadAlwaysLatest

If this value is set as Y, the user won't be prompted to select the latest version, and the latest version will be downloaded automatically.

Example: <key name="WebDownloadAlwaysLatest" value="N"/>

N

FixMessageOnOpen

Enable automatic correction of message properties for the Reply, Reply All, and Forward options in encrypted emails.

Example:  <key name="FixMessageOnOpen" value="N"/>

N

InsertAttachmentDocumentFilter

Configures the document filters that appear in the file selection dialog when performing an insert attachment action in Microsoft Outlook. Each filter is listed as a separate filter node with a name (label) and the set of document types that should be shown when selected. 

The list of types associated with a filter are expected to be a comma-delimited list of file types which should be allowed to appear when the filter is selected.

NOTE: Dollar sign ($) and pipe symbol (|) can't be used in filter names or type lists. These are reserved characters.

Example: 
<key name="InsertAttachmentDocumentFilter" value="">
<filter name="All Files (*.*)" types=""/>
<filter name="Adobe PDF Files (*.pdf)" types="ACROBAT,PDF"/>
<filter name="All Word Documents (*.docx,*.docm,*.dotx,*.dotm,*.doc,*.dot,*.htm,*.html,*.rtf,*.mht,*.mhtml,*.xml,*.odt)" types="WORDX,WORDXT,DOCX,DOCM,DOTX,DOTM,WORD,DOT,HTM,HTML,RTF,MHT,MHTML,XML,ODT"/>
</key>

See example.

InsertAttachmentDocumentFilterDefaultSelection

Specifies which filter should be selected by default in the file selection dialog when performing an Insert Attachment action in Microsoft Outlook. The value is a zero-based index of the filter to select. The default value is zero (that is, the first filter in the list).

Example: <key name="InsertAttachmentDocumentFilterDefaultSelection" value="0"/>

0

MaxOutgoingAttachmentSizeInMB

This specifies the maximum attachment size in megabytes that a user should be able to attach to an outgoing email.

Example: <key name="MaxOutgoingAttachmentSizeInMB" value=""/>

"" (no value)

SecureSend.DefaultExpirationInDays

The default number of days before the secure send link should expire.

Example: <key name="SecureSend.DefaultExpirationInDays" value="7"/>

7

SecureSend.RestrictedAccessEnabledByDefault

Decides whether access to secure send links is restricted by default.

Example: <key name="SecureSend.RestrictedAccessEnabledByDefault" value="Y"/>

Y

EnableAzureSSOInWorkPane

This option enables Microsoft Azure single-sign on in the Work Panel when using the WebView2 browser control.  Values are Y and N. 

Example: <key name="EnableAzureSSOInWorkPane" value = "N"/>

N

EnableDefaultScriptDialogsInWorkPane

Enables support for JavaScript alerts and other default scripting dialogs in the Work Panel.

Example: <key name="EnableDefaultScriptDialogsInWorkPane" value="N"/>

N

blacklist

Enables you to reduce security vulnerabilities by blocking certain file types to prevent users from opening or printing these files using iManage Work Desktop for Windows or the iManage Work web client.

Specify additional type of files from being shell executed. The value is a list of file extensions in lowercase separated by commas like "txt, js, exe". The default value is empty.

NOTE: The following file types are automatically blocked. As a result, users can't open or print these type of files.

• bat, // Batch File

• bin, // Binary Executable

• cmd, // Command Script

• com, // Command File

• cpl, // Control Panel Extension

• exe, // Executable

• gadget, // Windows Gadget

• inf, // Setup Information File

• ins, // Internet Communication Settings

• inx, // InstallShield Compiled Script

• isu, // InstallShield Uninstaller Script

• ob, // Windows Task Scheduler Job File

• jse, // JScript Encoded File

• lnk, // File Shortcut

• msc, // Microsoft Common Console Document    

• msi, // Windows Installer Package

• msp, // Windows Installer Patch

• mst, // Windows Installer Setup Transform File

• paf, // Portable Application Installer File

• pif, // Program Information File

• ps1, // Windows PowerShell Cmdlet

• reg, // Registry Data File

• rgs, // Registry Script

• scr, // Screensaver Executable

• sct, // Windows Scriptlet

• shb, // Windows Document Shortcut

• shs, // Shell Scrap Object

• u3p, // U3 Smart Application

• vb, // VBScript File

• vbe, // VBScript Encoded Script

• vbs, // VBScript File

• vbscript, // Visual Basic Script

• ws, // Windows Script

• wsf, // Windows Script

• wsh, // Windows Script Preference

Example: <key name="blacklist" value=""/>

"" (no value)

whitelist

If whitelist values are provided, it only opens file types in the list. All other types will be blocked.

Example: <key name="whitelist" value=""/>

"" (no value)

iManage.Field.Database

You can add fields by adding the value to a key in the same syntax.

For example, to add the imProfileDatabase field, enter imProfileDatabase as the value with the appropriate key name, under <ws_option name="iManFields">.

For a complete list of fields, refer to Appendix C - WSProfileAttributeID Enumerators.

Example: <key name="iManage.Field.Database" value="{imProfileDatabase}"/>

{imProfileDatabase}

iManage.Field.DocNum

Example: <key name="iManage.Field.DocNum" value="{imProfileDocNum}"/>

{imProfileDocNum}

iManage.Field.Version

Example: <key name="iManage.Field.Version" value="{imProfileVersion}" />

{imProfileVersion}

iManage.Field.Description

Example: <key name="iManage.Field.Description" value="{imProfileDescription}"/>

{imProfileDescription}

iManage.Field.Author

Example: <key name="iManage.Field.Author" value="{imProfileAuthor}"/>

{imProfileAuthor}

iManage.Field.Operator

Example: <key name="iManage.Field.Operator" value="{imProfileOperator}"/>

{imProfileOperator}

iManage.Field.Custom1

Example: <key name="iManage.Field.Custom1" value="{imProfileCustom1}"/>

{imProfileCustom1}

iManage.Field.Custom1Description

Example: <key name="iManage.Field.Custom1Description" value="{imProfileCustom1Description}"/>

{imProfileCustom1Description}

iManage.Field.Custom2

Example: <key name="iManage.Field.Custom2" value="{imProfileCustom2}"/>

{imProfileCustom2}

iManage.Field.Custom2Description

Example: <key name="iManage.Field.Custom2Description" value="{imProfileCustom2Description}"/>

{imProfileCustom2Description}

CacheObjects

This option enhances the performance on loading the items shown on the backstage when performing file open and save actions. It also loads the recent documents and folders in a background tasks once the server is connected.  

Example: <key name="CacheObjects" value="Y"/>

Y

AutoUpdateView

By default, users must manually refresh the backstage view. If this option is enabled, every time a file is opened (checked-out) or closed (checked-in or unlocked), the backstage view should be updated with the latest changes.  

Example: <key name="AutoUpdateView" value="N"/>

N

EnableNativeFilePicker

Enables users to opt in and opt out of the new and improved iManage Open and Save experience. Setting this option to N hides the banner and the Try the new interface option in the classic dialogs.

If a user has already switched to the new interface, after setting this option to N, the classic interface is displayed.

Example: <EnableNativeFilePicker>N</EnableNativeFilePicker>

Y

DisplayFormat

These settings control how information is displayed in the native file picker dialogs.

UsernameFormat

Configure the format of usernames to be displayed in iManage Work Desktop for Windows with the Native File Picker.

• 0: USERID | Full Name

• 1: USERID

• 2: Full Name

• 3: Full Name | USERID

0

MetadataFormat

Configure the display format of metadata fields in iManage Work Desktop for Windows with the Native File Picker.

• 0: Alias & Description

• 1: Description Only

0

EnableCustomTab

Show or hide the display of the custom metadata options in the new Open and Save experience dialogs. By default, this is enabled and displays the Recent Clients (custom1) in the list of Quick links and Clients tab in the Advanced Search.

Setting this option to N removes these elements, as shown:

Y: Show Custom tab

N: Hide Custom tab

NOTE: To display a different custom metadata property, other than custom1, refer to the CustomTabMetadata setting.

Y

CustomTabMetadata

When EnableCustomTab is enabled, this option sets the custom metadata field used for the Custom tab. Update the captions for CUSTOM1VIEW, and RECENTCUSTOM1
in Control Center to reflect appropriate labels in Work Desktop for Windows file picker for the Custom tab and recent items. Supported metadata (one field only):

• custom1

• custom2

• custom3

• custom4

• custom5

• custom6

• custom7

• custom8

• custom9

• custom10

• custom11

• custom12

• custom29

• custom30

custom1

ShowNewFolderButton

When enabled, displays the New Folder button to allow users to create a new folder within the new (native) file picker dialogs.

• Y: Enabled

• N: Disabled

If blank or any other values are entered, it will be enabled.

Y

EnableSearchLanguageSelection

Enables advanced searches in different languages.

• Y: Enabled

• N: Disabled

If blank or any other values are entered, it will be enabled.

Y

DefaultGridColumns

The following settings control what columns are displayed for each of the respective views in the new iManage Open and Save dialogs.

NOTE: iManage advises against removing columns from the respective <RequiredColumns> sections. These default columns are minimally required to present meaningful information.

Documents

• <DefaultColumns>: A comma-separated list of columns shown by default when viewing a list of documents in iManage Work. This list also controls the column order shown by default.

• <AvailableColumns>: A comma-separated list of properties that are shown as Available Properties in the Add/Edit Columns dialog. Users access this dialog by selecting Grid Settings in the new Open and Save dialogs.

• <SupportedColumns>: This section includes a complete list of all supported columns for reference.

<DefaultColumns>
is_checked_out,
version,
document_number,
size,
create_date,
edit_date,
author,
author_description,
custom1,
custom1_description,
custom2,
custom2_description,
workspace_id,
workspace_name,
from,
to,
received_date,
is_declared,
is_external,
database

Emails

• <DefaultColumns>: A comma-separated list of columns shown by default when viewing a list of emails in iManage Work. This list also controls the column order shown by default.

• <AvailableColumns>: A comma-separated list of properties that are shown as Available Properties in the Add/Edit Columns dialog. Users access this dialog by selecting Grid Settings in the new Open and Save dialogs.

• <SupportedColumns>: This section includes a complete list of all supported columns for reference.

<DefaultColumns>
has_attachment,
sent_date,
received_date,
custom1,
custom1_description,
custom2,
custom2_description,
workspace_id,
workspace_name,
is_declared,
is_external

Folders

• <DefaultColumns>: A comma-separated list of columns shown by default when viewing a list of folders in iManage Work. This list also controls the column order shown by default.

• <AvailableColumns>: A comma-separated list of properties that are shown as Available Properties in the Add/Edit Columns dialog. Users access this dialog by selecting Grid Settings in the new Open and Save dialogs.

• <SupportedColumns>: This section includes a complete list of all supported columns for reference.

<DefaultColumns>
workspace_id,
workspace_name,
owner,
owner_description,
is_external,
database

Workspaces

• <DefaultColumns>: A comma-separated list of columns shown by default when viewing a list of workspaces (matters) in iManage Work. This list also controls the column order shown by default.

• <AvailableColumns>: A comma-separated list of properties that are shown as Available Properties in the Add/Edit Columns dialog. Users access this dialog by selecting Grid Settings in the new Open and Save dialogs.

• <SupportedColumns>: This section includes a complete list of all supported columns for reference.

<DefaultColumns>
custom1,
custom1_description,
custom2,
custom2_description,
owner,
owner_description,
is_external,
database

MyWorkspaces

• <DefaultColumns>: A comma-separated list of columns shown by default when viewing My Workspaces (My Matters) in iManage Work. This list also controls the column order shown by default.

• <AvailableColumns>: A comma-separated list of properties that are shown as Available Properties in the Add/Edit Columns dialog. Users access this dialog by selecting Grid Settings in the new Open and Save dialogs.

• <SupportedColumns>: This section includes a complete list of all supported columns for reference.

<DefaultColumns>
edit_date,
owner,
owner_description,
database

CustomTabMetadata

• <DefaultColumns>: A comma-separated list of columns shown by default when viewing a list of clients (custom1) in iManage Work. This list also controls the column order shown by default.

• <AvailableColumns>: A comma-separated list of properties that are shown as Available Properties in the Add/Edit Columns dialog. Users access this dialog by selecting Grid Settings in the new Open and Save dialogs.

• <SupportedColumns>: This section includes a complete list of all supported columns for reference.

<DefaultColumns>
database

MyFavoritiesAndCategories

• <DefaultColumns>: A comma-separated list of columns shown by default when viewing My Favorities in iManage Work. This list also controls the column order shown by default.

• <AvailableColumns>: A comma-separated list of properties that are shown as Available Properties in the Add/Edit Columns dialog. Users access this dialog by selecting Grid Settings in the new Open and Save dialogs.

• <SupportedColumns>: This section includes a complete list of all supported columns for reference.

<DefaultColumns>

(blank - no default columns are defined)

AdvancedSearchCriteria

The following settings control what fields are displayed when performing an advanced search in the new iManage Open and Save dialogs.

NOTE: The criteria included in the respective <DefaultSearchCriteria> sections cannot be removed from the Advanced Search dialogs.
Removing criteria from the respective <AvailableSearchCriteria> sections will mean they are not shown as available search criteria in the Advanced Search Dialog.

Documents

• <DefaultSearchCriteria>: A comma-separated list of properties shown by default when performing an advanced search for documents from the new iManage Open and Save dialogs.

• <AvailableSearchCriteria>: A comma-separated list of properties that users can include as search criteria when performing an advanced search.

• <SupportedSearchCriteria>: This section includes a complete list of all supported properties for reference.

<DefaultSearchCriteria>
title,
keyword </DefaultSearchCriteria>

Emails

• <DefaultSearchCriteria>: A comma-separated list of properties shown by default when performing an advanced search for emails from the new iManage Open and Save dialogs.

• <AvailableSearchCriteria>: A comma-separated list of properties that users can include as search criteria when performing an advanced search.

• <SupportedSearchCriteria>: This section includes a complete list of all supported properties for reference.

<DefaultSearchCriteria>
subject,
document_number
</DefaultSearchCriteria>

DocsAndEmails

• <DefaultSearchCriteria>: A comma-separated list of properties shown by default when performing an advanced search for documents and emails from the new iManage Open and Save dialogs.

• <AvailableSearchCriteria>: A comma-separated list of properties that users can include as search criteria when performing an advanced search.

• <SupportedSearchCriteria>: This section includes a complete list of all supported properties for reference.

<DefaultSearchCriteria>
name,
document_number
</DefaultSearchCriteria>

Folders

• <DefaultSearchCriteria>: A comma-separated list of properties shown by default when performing an advanced search for folders from the new iManage Open and Save dialogs.

• <AvailableSearchCriteria>: A comma-separated list of properties that users can include as search criteria when performing an advanced search.

• <SupportedSearchCriteria>: This section includes a complete list of all supported properties for reference.

<DefaultSearchCriteria>
name,
description
</DefaultSearchCriteria>

Workspaces

• <DefaultSearchCriteria>: A comma-separated list of properties shown by default when performing an advanced search for workspaces (matters) from the new iManage Open and Save dialogs.

• <AvailableSearchCriteria>: A comma-separated list of properties that users can include as search criteria when performing an advanced search.

• <SupportedSearchCriteria>: This section includes a complete list of all supported properties for reference.

<DefaultSearchCriteria>
name,
keyword
</DefaultSearchCriteria>

CustomTabMetadata

• <DefaultSearchCriteria>: A comma-separated list of properties shown by default when performing an advanced search for custom1 (Clients) from the new iManage Open and Save dialogs.

• <AvailableSearchCriteria>: A comma-separated list of properties that users can include as search criteria when performing an advanced search.

• <SupportedSearchCriteria>: This section includes a complete list of all supported properties for reference.

<DefaultSearchCriteria>
custom1
</DefaultSearchCriteria>