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

Question

Question

Why is Search Repository taking so long

asked on August 7, 2014

 

Why would this Search Repository workflow be taking so long.  There are only 627 documents in the folder it is to be searching?  It's been trying for two hours.  I've seen this before and have had to give up what I was trying to do (luckily found another way with that one).

0 0

Replies

replied on August 7, 2014 • Show version history

{LF:Name="*"} is inefficient when combined with a path search in large repositories because the server has to calculate access rights for all the results. If you are using Workflow 9.1, make sure you are on 9.1.1 with the latest hotfix. There was an additional inefficiency in how Workflows was getting the search results that was addressed through hotfixes.

 

Are these documents in subfolders of "RECORD SERIES - (a) Incoming Scans"? If they're directly in the folder, it is more efficient to use Find Entries instead of a search.

 

Side note: your search only returns documents and shortcuts, you don't need the conditions on whether the entry type is folder in the Routing Decision. You can also remove the shortcut condition (the type parameter in the search tells it to return Documents, Batches and Shortcuts. If you remove B and S, it would return only documents).

1 0
replied on August 11, 2014

Thanks, Miruna.  Lots of good information in there.

 

I did try the WF first with only a condition for return Documents (not mentioning folders/shortcuts).  The WF didn't do what I expected, but the one thing it did do was just move the entire Folder and all contents to the new location outlined.  I hadn't wanted the folder moved.  That's why I threw in the extra conditions.

 

I've now rebuilt the WF based on your second paragraph, since (1) I don't have VS 9.2 only 9.1, and (2) all the documents are directly in the incoming scans folder and not in any subfolders.  How does it look now ? ...

 

0 0
replied on August 11, 2014

Correction:  I have WF Version 9.1.0.3.28

0 0
replied on August 11, 2014

Ok, then you definitely want to get your IT department or Laserfiche Reseller to update to the latest hotfix.

 

If I'm understanding this correctly, you want to route based on the template on the documents not on the "RECORD SERIES - (a) Incoming Scans" folder? If that's the case, you should run the Routing Decision inside the For Each Entry and check on fields on the documents rather than the starting entry.

 

0 0
replied on August 11, 2014

Miruna, I've rebuilt as you suggested.  I certainly see results, but it still didn't complete.  It found the 625 docs in the right folder, but didn't move them.  The error report says "Routing Decision" "The selected entry could not be found."  Can you tell why?

 

0 0
replied on August 12, 2014

Did you set the Routing Decision to process the For Each Entry current entry?

0 0
replied on August 13, 2014

The only option it allows me to choose under For Each Entry activity is the Output Entries and there's no configuration choices under Routing Decision activity.

0 0
replied on August 13, 2014

Bert meant the Route to Folder activity. Your screenshot covered the radio buttons on the Entry to Route panel in its properties.

0 0
replied on August 13, 2014

Oh, then yes, the Route to Folder was set for Entry:  Current Entry.

 

0 0
replied on August 15, 2014

Hi Connie, 

 

If your question has been answered, please let us know by clicking the "This answered my question" button on the response.

 

If you still need assistance with this matter, just update this thread. Thanks!

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

Sign in to reply to this post.