Document manager¶
Document Manager Overview¶
The Document Manager offers a way to store any kind of file. This could be for example pdf, Microsoft Word, videos, executable, etc.
Any type of files can be imported but only a few are natively recognized and can be opened directly from MIKE Workbench.
Organizing Documents¶
Create a new Document group¶
Create a new group by right clicking on the root node or an existing group, and select Add New Group from the context menu.
The new group is created as a subgroup under the group that was selected.
Rename a group¶
The model group name becomes now editable, and a new name can be entered.
Import Documents¶
New Documents can be imported from files (e.g. mp4 format files).
Import a Document¶
Select the group node to import the document to.
Select Import document tool.
Browse for file, define name and run.
The document is imported.
Rename a Document¶
Right-click the Document to rename and select Rename.
The text in the node becomes editable. Change the text and press Enter. To cancel editing press Esc.
After changing the name the node is placed alphabetically within the group.
Working with Documents¶
Editing a Document¶
Right-click a Document and select Open - or simply double-click the Document in the Explorer.
If the file format is recognized, the software set as default for this file type will be started.
The document can be edited.
Saving the document will automatically update it in the database.
Export a Document¶
Navigate to the document of interest. Click once on the document in the documents manager and in the tools explorer window select Export document.
Specify the location where you would like to have the file on your computer. Click Run.
Document Data Providers¶
The document manager supports external document data providers, for storing documents.
The data providers are configured from the root node of the Document Manager.
The connection string contains the following information (separated by a semicolon ;).
- Environment (Prod, Dev, Test)
Default is Prod (production). If the environment is not specified, Prod is used. - API key
The API key (a GUID) generated in the DHI Azure Admin Center. The API key is not required when using DHI single sign-on.
By default, the connection string is empty. This means that the Production environment is used, and that DHI single sign-on is used.
DHI single sign-on requires a login and is not suitable when using e.g. the job service of MIKE OPERATIONS for running scheduled jobs. In this case using an API key is recommended.
Select OK when the connection string has been specified.
Tip
If the connection fails, you should clear the cache by deleting the file (for Prod):
%localappdata%\DHI.oidccache.bin
When a service provider has been configured, a new root node will be shown in the Document Explorer for each document data provider configured.
The document data providers works as the default document provider, so that documents can be added, updated and deleted as documents in the MIKE OPERATIONS database.