We have had several problems since upgrading to Laserfiche 9.1. We were on 9.0.3 but after hearing about some of the “great features” of 9.1 at empower we decided to upgrade. What a huge mistake that was. I posted about 2 of these issues earlier but I did not get anything useful and have since opened a service ticket with our VAR. We have basically been holding out hope that 9.1.1 would fix the problems unfortunately that was not the case. So I am turning here for help one again in hopes that someone takes this seriously. Below are the list of bugs we have found so far.

1. After upgrading from 9.03 to 9.1 and 9.1.1 the laserfiche client became unusable when logged in as a windows user with multiple folder level restrictions. Just navigating around the client would cause it to lock up or crash. This was not the case when logged on as an admin level user that has permissions to see all folders.
   1. Our VAR suggested that we delete all user attributes and have them try to log back in. This did resolve the issue but, it did not seem right. As simple upgrade should not require something lack that.
2. After upgrading from 9.03 to 9.1 or 9.1.1 we were no longer able to print to laserfiche. I discovered that if we had any users that had not saved a default snapshot profile they were able to print to laserfiche without issue.
   1. After the VAR was finally able to tell us where the default profile is saved (it’s in the registry for those that are curious) I deleted the registry key and printing to laserfiche worked just fine. Once again a solution yes, but is still not right.
3. After upgrading workflow all logic decisions were reversed. For example if a decision based on a filename in the workflow editor said do this if the file name contained “something” when the workflow ran it did not perform as expected. Upon investigating the workflow activities we realized that the workflow was processing with the decision to run if the filename did not contain “something”.
   1. Once we got over the initial confusion of the logic being listed one way in the designer yet processing in the opposite way, we accidentally discovered that all you to do is go through and republish each workflow and it would fix the problem. We still have now idea why but it worked.
4. The other and much more serious problem is very, very bad search performance for users with restrictive folder level permissions. The biggest problem with this is that it renders the integration between laserfiche and Junxure useless. This is a huge problem for us because it kills the functionality of or document management system and our CRM.
   1. A simple folder search for a folder with a specific metadata field (exact syntax {LF:Name="*", Type="F"} & {[]:[id]="945"} takes anywhere between 10 minutes and 44 seconds to 18 minutes and 46 seconds to run when logged in as a standard user with restrictive folder level permissions. If I log in to laserfiche as the admin user or a user that is allowed to see more folders the search will run in 1 second. That’s an 18 minute and 45 second difference! WTF!
   2. For testing purposes our VAR suggested that we enable bypass browse permissions for one of the standard users with all of the folder level restrictions. With bypass browse the same 18 minute search takes 46.3 seconds. However, this is not a viable solution for us. Our entire laserfiche security structure is designed around bypass browse being disabled. Not only that but worked in 9.0.3. Why the drastic difference in security behavior? You should not have to redesign your entire structure when performing a simple version upgrade!