Document Stores
Within this section you can configure the following type of Document Store:
Source Document Stores - These are iManage libraries where you can search, find and nominate Documents to Blueprint
Knowledge Document Stores - These are iManage libraries where Blueprint will store copies of the nominated Documents to be used within the Blueprint application
Both of these are crucial to the functioning of the Blueprint application and need to be configured and enable to support Nominating Documents.
Source Document Stores
Multiple iManage Stores can be configured and enabled within this section to ensure that users can Nominate Documents from multiple iManage libraries. You are able to add new Stores and Edit/Delete existing Stores.
You will need to provide Server details along with API information and Service Account authentication.
Upon clicking Save a test will be conducted to ensure that the data entered is valid and a connection can be made to the Store.
Any existing Stores will have an indicator to highlight the current connection status, if this is Green then connections are live and if it is Red then connection could not be made and further attention is required.
SharePoint is automatically enabled and therefore will not appear as a configurable option.
The connection can be managed via the GraphApi settings.
iManage Field Mapping
Any iManage Source Document Stores can be configured to auto-populate metadata from iManage to Blueprint as part of the Nomination process.
Clicking ‘Edit’ on an existing Source Stores and selecting ‘Preferences’ will open the Field Mappings modal. Within this you can select standard iManage data fields and Custom fields and assign it to map to one of the Blueprint Fields. Provided that the Blueprint Field is assigned to the Nomination Context any data stored on the iManage Document will be auto-populated when navigating to the Refinement step.
You will only be able to map to the same field type. i.e. iManage Text fields will only be able to be mapped to Blueprint Text fields.
If the Blueprint field has been configured with any restrictions such as being mandatory or having a minimum number/date value then validation will be carried out on any data being auto-populated.
Knowledge Document Stores
These Stores are where your Blueprint Documents will be stored. Only one Store can be enabled at any one time. Enabling a new store will instantly disable the old Store. Documents can continue to be held within the old Store and accessed by Blueprint but any new Documents will be added to the new Store.
Any disabled iManage Stores can be deleted provided that there are no Documents linked to that iManage library.
You will need to provide Server details along with API information and Service Account authentication.
Upon clicking Save a test will be conducted to ensure that the data entered is valid and a connection can be made to the Store.
Any existing Stores will have an indicator to highlight the current connection status, if this is Green then connections are live and if it is Red then connection could not be made and further attention is required.
Once configured you will need to specify a folder/library within the iManage/SharePoint options, you can do this by clicking ‘Edit’ on an existing and disabled Knowledge Store and selecting ‘Preferences’. This can not be adjusted for the enabled Knowledge Store.
SharePoint is an automatically configured option and is shown as an option to ensure you can enable/disable