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

Question

Question

Enhancing our Search Repository Activity

Workflow Quick Fields Laserfiche Version 9
Updated February 12, 2015
asked on February 12, 2015

We have a bulk import process that leverages Quickfields to import and Workflow to find already existing documents and create links between them using a match by Account Number and a Date field. However, the Search Repository activity is taking a considerable amount of time to return values--on average 75% of the time, 6 seconds, to complete the entire workflow process, but with some taking over 20 seconds. Our investigation through the Workflow Stats indicates that the 'Account Number' field is pulling back as if it were a like search, and I wanted to turn that into a distinct parameter to see if that increased the search performance. I have included the search below, and I'd appreciate any feedback or insights into fine tuning it to help decrease the search time.

 

{[]:[Account Number]="%(RetrieveFieldValues_Account Number)"} & {[]:[Due Date]="%(RetrieveFieldValues_Due Date)"} & {LF:Name="*", Type="DB"} & {LF:LOOKIN="FolderPath"}

1 0

Replies

replied on February 12, 2015

Are you looking in the whole repository? If so are the documents only in a certain set of folders? If so I would narrow the search down to a set of folders rather tan the whole repository. It is kind of hard to tell exactly where you are looking for these documents.  

0 0
replied on February 12, 2015

No, we're looking in a particular group of folders which only contain the relevant documents, but we  had previously been looking in a larger grouping. Narrowing down the range of folders did help the performance, but not to the extent that we were looking to achieve.

0 0
replied on February 12, 2015

I'm not sure what you mean by "Our investigation through the Workflow Stats indicates that the 'Account Number' field is pulling back as if it were a like search"...

Unless you have the combination of account number and date also set on folders, you should take out the "{LF:Name="*", Type="DB"}" part of the search.

What version of Workflow are you running?

0 0
replied on February 12, 2015

When filtering the through the Workflow results, we noted that the search repository activity on accounts that had commonly shared number values was taking much longer than those with more unique entries. For example, the query on account 50 was taking unusually longer than accounts with a more unique value like 32545. My assumption, and please correct me if I am mistaken, was that it was filtering through any numeric with the '50' within it as if there were wildcards before and after the value. 

We are currently on version 9.0.1. I will remove that part of the search and give it another shot. I appreciate the feedback, Miruna! 

0 0
replied on February 12, 2015

Oh, i see. Is the account number a text or a number field?

0 0
replied on February 12, 2015

It is a number field.

0 0
replied on February 12, 2015

When filtering the through the Workflow results, we noted that the search repository activity on accounts that had commonly shared number values was taking much longer than those with more unique entries. For example, the query on account 50 was taking unusually longer than accounts with a more unique value like 32545. My assumption, and please correct me if I am mistaken, was that it was filtering through any numeric with the '50' within it as if there were wildcards before and after the value. 

We are currently on version 9.0.1. I will remove that part of the search and give it another shot. I appreciate the feedback, Miruna! 

You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...