How can we help you today? Enter your search term here KnowledgeTree for Salesforce Quickstart Guide. Onboarding Guide for KnowledgeTree for Salesforce. Installing KnowledgeTree for Salesforce. Users, Roles, Access Groups 7.
|Published (Last):||25 March 2017|
|PDF File Size:||5.27 Mb|
|ePub File Size:||19.98 Mb|
|Price:||Free* [*Free Regsitration Required]|
Plugin Version: 1. Warning: KnowledgeTree is no longer open source in any meaningful sense. KnowledgeTree was an open source Document Management System DMS , which offered a simple web-based interface to provide access to documents for specified users in an organization. X, so that Input Documents and Output Documents which are used in ProcessMaker cases can be stored and managed in a centralized manner. Storage in KnowledgeTree allows ProcessMaker documents to be easily accessed by external applications and seamlessly integrated into an organization's wider operations.
ProcessMaker Enterprise Edition 2. To obtain the plugin, please contact the ProcessMaker sales department. Free trials of the plugin are available. The ProcessMaker plugin uses web services to connect to KnowledgeTree and automatically login as a KnowledgeTree user. Input and Output Documents which are configured to be managed by KnowledgeTree are automatically stored in KnowledgeTree when created during a case.
These documents are place inside of folders whose names can be configured when designing a process. All KnowledgeTree folders to which the logged-in user has access are displayed. Click on a folder to see its files and subfolders. Installing required programs Install the KnowledgeTree requirements as the root user :. Installing pstotext Since a package is not available for pstotext program, it will need to be compiled from source.
First, install gcc if it isn't already installed :. 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 this page.
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. In the configuration dialog box, enter the connection information to access a KnowledgeTree server:. Then, click on Save. By default, all documents managed by KnowledgeTree are placed in the "Default" category of Document Type.
To create other categories of Document Types, login to KnowledgeTree as the "admin" user and go to Admin. On the second menu-option, next to Case Scheduler option, DMS configuration option will be enable as the image below:. 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:. 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.
By clicking on Assign Documents the list of Output and Input Documents created during the process will be listed. All assigned documents will be displayed below the list of documents:. 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 in knowledge tree to display specific information of an uploaded document depending on the case variables chosen.
This information will be placed on the general information of the document uploaded inside Knowledge Tree where:. Note: If a map type is created on Knowledge Tree it will be displayed on this list. 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.
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:. To understand how the integration works, it is a good practice to create an example.
Click on Assigned Documents , which is the default for Document Types. In the dropdown select the Identification Input Document and click on assign to add the Input Document to the list below:. 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 Destination path to specify a path where the document will be stored.
Once the path is defined, click on Save and the complete path will display at the top of the KnowledgeTree configuration screen:.
Once the DMS configuration is set, close the window and start a case. 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.
Go to Browse Documents and look for the name of the folder defined in Destination Path. In this example, the name of the folder is processmaker and its subfolder is the username, which in this case is "admin":. The document can be downloaded directly from KnowledgeTree and it displays generic and general information about the file.
Remember that this information was set in map types. Adding metadata about documents creates a high-level storage structure for both KnowledgeTree and ProcessMaker. This helps to organize documents uploaded to ProcessMaker according to the document type. For example, a document type named Invoice can be created, which stores all documents related to invoices generated during the process.
Configuring the metadata layer involves adding the document types, fieldsets and fields, so that ProcessMaker variables can be displayed next to each fieldset. The Existing document fieldsets will be listed:. Once the Fieldset is created, new fields can be added. 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.
In this example, two fields will be created, named Application Date and Place of Employment. 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.
Defining Map Fields where ProcessMaker variables will be used to show some specific information about the document s stored in KnowledgeTree. In this example, tree types of the Field Set named Credit Card Application are displayed at the bottom of the list:.
Field names will be created once the Fieldset is created. Dropdowns will list the ProcessMaker system and case variables. Assign a variable from the process to fieldset:.
Checking the Generic Information: Once a case is running and a document is attached Input Document or generated Output Document , open KnowledgeTree and go to destination path for the document to see its Generic Information :. 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.
Checking the General Information : In this case a Field Set named Credit Card Application was created, so information created as field names will be displayed in the General Information section:. The General Information contains the case variables which were created when the case was executed. The Input Documents and Output Documents which are configured to be managed by KnowledgeTree will now appear in folders.
ProcessMaker cases will now be integrated into KnowledgeTree's document management system. To download or view one of the documents, click on its Get button.
Depending upon how the web browser is configured, the document may be displayed in a browser plugin or a stand-alone application. Alternatively, it may be downloaded and stored on the local computer. All rights reserved. Please rate how useful you found this document:. Select rating Give 2. Download our app. Contact us. ProcessMaker 3.
2.0/2.X - KnowledgeTree Integration