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].

Author: Vudot Dojinn
Country: Serbia
Language: English (Spanish)
Genre: Software
Published (Last): 19 June 2008
Pages: 222
PDF File Size: 7.30 Mb
ePub File Size: 14.76 Mb
ISBN: 574-2-56345-689-1
Downloads: 65164
Price: Free* [*Free Regsitration Required]
Uploader: Kiganos

ProcessMaker Enterprise Edition 2. The Existing document fieldsets will be listed:. Go to Browse Documents and look for the name of the folder defined in Destination Path.

2.0/2.X – KnowledgeTree Integration

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.

By clicking on Assign Documents the list of Output and Input Documents created during the process will be listed. Storage in KnowledgeTree allows ProcessMaker documents to be easily accessed by external applications and seamlessly integrated into an organization’s wider operations. 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 used knowldgetree knowledge tree to display specific information of an uploaded document depending on the case variables chosen.

Assign a variable from the process to fieldset:. To obtain the kknowledgetree, please contact the ProcessMaker knowldegetree department.

To download or view one of the documents, click on its Get button. KnowledgeTree is no longer open source in any meaningful sense.

knowleegetree In this example, two fields will be created, named Application Date and Place of Employment. If there’s no Document Types defined, the only one appearing on the list will be Default so choose Assigned Documents from Default option, the following list of options will display on the same window:.


For example, if a user wants knowledgetred stored documents in a folder named ProcessMaker and on a subfolder with the user name, the path will be:. Click on Assigned Documentswhich is the default for Document Types. Please rate how useful you found this document: Once a case is running and a document is attached Input Document or generated Output Documentopen KnowledgeTree and go to destination path for the document to see its Generic Information:.

Click on Destination path to specify a path where the document will be stored.

Alternatively, it may be downloaded and stored on the local computer. Attach a Document in the Input Document Window and once it is uploaded, this message will be displayed: Once the DMS configuration is set, close the window and start a case. This helps to organize documents uploaded to ProcessMaker according to the document type.

Remember that this information was set in map types. If a map type is created on Knowledge Tree it will be displayed on this list. In this example, the name of the folder is processmaker and its subfolder is the username, which in this case is “admin”:.

/2.X – KnowledgeTree Integration | [email protected]

The document can be downloaded directly from KnowledgeTree and it displays generic and general information about the file. To create other categories of Document Types, login to KnowledgeTree as the “admin” user and go to Admin. ProcessMaker cases will now be integrated into KnowledgeTree’s document management system.

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. Once the path is defined, click on Save and the complete path will display at the top of the KnowledgeTree configuration screen:. 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.


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. For example, a document type named Invoice can be created, which stores all documents related to invoices generated during the process. Installing KnowledgeTree Download the source code file for KnowledgeTree, which will have a filename like kt-src-oss The Community Edition can be found in knowleegetree page.

Checking the Generic Information: Dropdowns will list the ProcessMaker system and case variables. 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. Click on a folder to see its files and subfolders.

In this example, tree types of the Field Set named Credit Card Application are displayed at the bottom of the list:. The General Information contains the case variables which were created when the case was executed.

Installing pstotext Since a package is not available for pstotext program, it will need to be compiled from source. To understand manyal the integration works, it is a good practice to create an example. Checking the General Information: All KnowledgeTree folders to which the logged-in user has access are displayed. 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. Then, click on Save.