You are viewing limited content. For full access, please sign in.

Discussion

Discussion

Laserfiche as Case Management System

Version 10 Laserfiche Ideas
Updated February 2, 2021
posted on January 26, 2021

Hi All,

has there been any movement on Laserfiche as a case management system? I know we have a number of examples in my organization where it could be utilized, but because it's not "out of the box" we're using other tools (but which don't have retention, cross-searching, and other great features LF has). 

If anyone has examples, that would also be appreciated.

Robyn

0 0
replied on January 27, 2021

I have been interested in developing a CRM framework for sometime in response to tenders that request CRM solution.  Laserfiche is not an "Out of the Box" CRM solution.

I some thoughts that I can contribute.  So my approach is to redefine CRM by asking the question if I was buying a CRM solution today, what does it look like and I how do I convince my boss that I have found the best one. So what are the features that should I focus on? I then found an article by Samantha Bonanno  10 Best Features of a CRM

This article tells the reader what the features should be considered in buying a good CRM. 

Core Features

1. Contact management  
2. Interaction tracking 
3. Lead management

Common Features
4. Email integration
5. Document management

6. Quotes/proposal management

7. Pipeline management
8. Workflow automation

Optional Features
9. Reporting/analytics
10. Forecasting
 

The article describes the 10 Best features in detail from the point of the buyer hence you get a better understanding of CRM market and then you can start match the features of Laserfiche that can be applied. One point, its not what "Laserfiche will do", its what you can design and do after "Laserfiche does"

Features 1-3 and 6-7 should be analysed and designed with the help in Laserfiche Solution Exchanges or Process Library.  Features 9 -10 are the features that are both interesting and other more challenges because they are always evolving, as Laserfiche is always evolving here.

The key to design in Laserfiche is use of the external database models,with good Taxonomy and onology design (SETH EARLEY The AI-POWERED ENTERPRISE) using this approach you can design a CRM or a Case Management System or Risk Management System and much more and realize the true promise of AI

For example, tools like MSPower BI will work on data in your external database "after Laserfiche does" in CRM model.

As a community we continue to buy and apply Laserfiche and will support, some will strive to develop work processes to meet new challenges or reduce costs. I recommend Seth Earley work as I belief that the understanding of taxonomy and onology and its application will bring an organisation great sustainable benefits overtime.

I am open for further discussion.

 

 

0 0
View 1 previous reply
replied on January 27, 2021

Hi David,

great points. I suppose when I think about a case management system, I imagine field values that are applied to the "case" as a whole, rather than fields applied to every document. 

For example, whether a case is open/closed can be created with a drop down field value with open and closed as options. however, the way fields work in LF, is that they're applied to all documents, rather than to a "bucket" of documents belonging to a specific case (that could include multiple documents). 

I'm not sure if there is an efficient alternative for this example?

0 0
replied on January 27, 2021

In Laserfiche a field is available to all documents to be applied but they inherit their meaning from the entry.  For example a field called NAME Text 40 can be included the Suppliers Template and Customer Template when you search Name="David" and Template = Suppliers you will a Supplier name is "David" hence same field different usage.

A multi-valued text field called "Closed" List contains "Yes, No" Default value No

It can be assigned to Case Record Template and/or a Contract Review Template.

Is the case Closed? Is the Contract Review Closed? Same field but different templates and as such different purposes.

 

A field can be assigned to a case as a whole because a case itself is a record which is an entry in the repository. That entry is assigned an Entry Id and assigned metadata (Fields - Templates, Signatures,Tags,Relationships) by laserfiche. In addition, the case could have one system generated identifier(Last Case Number + 1) assigned to it by workflow add to metadata eg. Case Identifier No.  Since a case is a collection of documents entries with Metadata Field Case Identifier No. The case documents would be located in Folders with same Field Case Identifier No. 

The Case Entry contains a template of fields focused on case management. eg Field Case Identifier No, Date opened, Description, Closed, Date Closed  

Hence the importance of Taxonomies and onology so that fields mean makes sense to the business and future uses and leads to efficiency of human and machine learning.

 

0 0
replied on February 1, 2021

Hi David,

In your example, a field for a case number would exist in the template of the folder (case) and the documents in the folder (associated with the case). If you have workflow auto-generate a new case number for each instance of the template, what prevents the workflow from creating a new case number for each new document as opposed to the desired outcome of a new case number for each new case?

Following that logic, if I have a field for Closed with a list of "yes/no", default "no", and I'm ready to close the case to "yes", I understand that I would have to change each document's field value to "yes" as opposed to just the case's/folder's field value. I suppose one could build a workflow to auto-change the folder content's field values, but is that the only solution?

Robyn

0 0
replied on February 2, 2021

You design a process whether in Forms or in the workflow to apply a unique Identifier to the Case folder entry with template field "Case Id" the repository and all folders and documents below that entry in that folder will have Case Id field "Case Id" with default value (%Parent Field) so they will inherit that Case Id. Each Folder can have separate lower identifier at Folder or Document level.

Three Metadata templates Case - Folders - Documents they share the same fields but their values are not the same.

The Field called Closed will only appear at Case Folder in metadata template. The current value of that field is at LF Entry level. eg ABC case "CaseId" = 888288 LF EntryId =23222 Closed = Yes   By design all Sub Folders and documents are treat as belonging a Closed case as their Case Id Field  =23222 is Closed.

All Entries can be associated by Relationships in Metadata Field and Tags can be used  

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...