If you decide not to commit the changes you made, use the cancel check-out option in the Document Actions menu to restore the document to the version prior to. KnowledgeTree Administrator Manual – June Table of Contents .. Upgrading KnowledgeTree OSS (manually installed) to KnowledgeTree. Professional. A dvanced Computer Systems œ Project Management. KnowledgeTree Document. Management System User. Manual. [KTDMS-SUM].
|Published (Last):||8 March 2010|
|PDF File Size:||2.59 Mb|
|ePub File Size:||3.6 Mb|
|Price:||Free* [*Free Regsitration Required]|
For example, a document type named Invoice can be created, which stores all documents related to invoices generated during the process.
The ProcessMaker plugin uses web services to connect to KnowledgeTree and automatically login as a KnowledgeTree user. The document can be downloaded directly from KnowledgeTree and it displays generic and general information about the file.
Depending upon how the web browser manuaal configured, the document may be displayed in a browser plugin or a stand-alone application. To create other categories of Document Types, login to KnowledgeTree as the “admin” user and go to Admin. Click on a knowledgetrde to see its files and subfolders. All assigned documents will be displayed below the list of documents:. Knowlddgetree documents are place inside of folders whose names can be configured when designing a process.
Assign a variable from the process to fieldset:. Attach a Document in the Input Document Window and once it is uploaded, this message will be displayed: This helps to organize documents uploaded to ProcessMaker according to the document type. The Community Edition can be found in this page. First, install gcc if it isn’t already installed:. Select rating Give 2. Free trials of the plugin are available.
2.0/2.X – KnowledgeTree Integration
Alternatively, it may be downloaded and stored on the local computer. Defining Map Fields where ProcessMaker variables will be used to show some specific information about the document s stored in KnowledgeTree. Click on Destination path to specify a path where the document will be stored. It is important to create Document Types to manage large amounts of documents, which will be uploaded or generated in ProcessMaker and stored in KnowledgeTree.
For example, if a user wants to stored documents in a folder named ProcessMaker and on a subfolder with the user name, the path will be:. Field names will be created once the Fieldset is created. The Input Documents and Output Documents which are configured to be managed by KnowledgeTree will now appear in folders. Storage in KnowledgeTree allows ProcessMaker documents to be easily accessed by external applications and seamlessly integrated into an organization’s wider operations.
The General Information contains the case variables which were created when the case was executed.
Installing KnowledgeTree Download the source code file for KnowledgeTree, which will have a filename like kt-src-oss It can be installed by either clicking on Install from File and uploading the plugin file or by clicking on its Install Now button in the list of available plugins.
To download or view one of the documents, click on its Get button.
To save documents in KnowledgeTree, it is required to assign which ones of the process will be saved, they will be either Input Documents or Output Documents. A file which is stored in KnowledgeTree will have a Get button to download it, whereas a file stored normally in ProcessMaker will have a Download button. ProcessMaker Enterprise Edition 2. At this point Document Type is defined in the default type and Destination path as –not defined– because no path has been defined for storing the documents.
In the dropdown select the Identification Input Document and click on assign to add the Input Document to the list below:. Click on Assigned Documentswhich is the default for Document Types. This information will be placed on the general information of the document uploaded inside Knowledge Tree where:. Remember that this information was set in map types.
/2.X – KnowledgeTree Integration | [email protected]
Adding metadata about documents creates a high-level storage structure for both KnowledgeTree and ProcessMaker. Configuring the mnual layer involves adding the document types, fieldsets and fields, so that ProcessMaker variables can be displayed next to each fieldset.
X, so that Input Documents and Output Documents which are used in ProcessMaker cases can be stored and managed in a centralized manner. To understand how the integration works, it is a good practice to create an example.
Then, click on Save. Installing required programs Install the Mankal requirements as the root user:. The two fields will be associated with ProcessMaker variables, so it is recommended to use field names which can be easily associated with ProcessMaker variables.
In the configuration dialog box, enter the connection information to access a KnowledgeTree server:. Once a case is running and a document is attached Input Document or generated Output Documentopen KnowledgeTree and go to destination path knoweldgetree the document to see its Generic Information:. Once the DMS configuration is set, close the window and start a case.
Dropdowns knowledgehree list the ProcessMaker system and case variables. ProcessMaker cases will now be integrated into KnowledgeTree’s document management system. These fields will display information related to the process created in ProcessMaker, so it’s important to give clear names which will be associated with case variables.
Checking the Generic Information: To have documents stored in folders it’s necessary to specify the path where documents will be placed, it is possible to give a new path, just specifying the name of the folders, by clicking on the “Case Variable” button it is also possible to add case variables either system or process as folders names. If a map type is created on Knowledge Tree it will be displayed on this list. Knowledgetred the General Information: Input konwledgetree Output Documents which are configured to be managed by KnowledgeTree are automatically stored in KnowledgeTree when created during a case.
Once the path is defined, click on Save and the complete path will display at the top of the KnowledgeTree configuration screen:. By clicking on Assign Documents the list of Output and Input Documents created during the process will be listed. Nanual this knoqledgetree, two fields will be created, named Application Date and Place of Employment.
Map Fields between DMS Metadata and ProcessMaker variables are created to map case variables to KnowledgeTree, in other words it’s possible to specify which variables will be knowleddgetree in knowledge tree to display specific information of an uploaded document depending on the case variables chosen.