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

Question

Question

How to read Audit Trail Data for Search String

asked on January 20, 2015

Hi all, 

I have recently been running a lot of reports trying to figure out which users have been searching, creating records, etc. I am able to understand the data for most of the data columns, but there have been some information in the "search string" column that have bewildered me. 

Without providing details on the searches that people have carried out on our system, is there a table or key available that would explain these elements (ie: a table of information type and description)? 

I have tried looking in the Administrative Guide, but the section on "Information Logged About Each Event" does not go into detail about this particular column information. 

Appreciate any help. 

Thanks!

0 0

Answer

SELECTED ANSWER
replied on January 21, 2015

The Laserfiche Server also supports a SQL-like internal query language, known as LFQL (Laserfiche Query Language). Some of the searches may be translated by the search processor to LFQL rather than the search syntax for better performance.

I don't think we document LFQL syntax outside of the SDK documentation, which is not publicly available. The snippet you pasted above refers to retrieving fields.

1 0

Replies

replied on January 20, 2015

All searches are translated from the data entered by the user into the advanced search syntax the server uses internally. See the help file for more information on all the options.

1 0
replied on January 21, 2015

Thank you very much Miruna, that page helps quite a bit. However, there are some elements that I am still unsure about. The following is an example of a part of search string data: select prop_id 

I do not see this mentioned in the explanations of the advanced search syntax help files. 

 

0 0
SELECTED ANSWER
replied on January 21, 2015

The Laserfiche Server also supports a SQL-like internal query language, known as LFQL (Laserfiche Query Language). Some of the searches may be translated by the search processor to LFQL rather than the search syntax for better performance.

I don't think we document LFQL syntax outside of the SDK documentation, which is not publicly available. The snippet you pasted above refers to retrieving fields.

1 0
replied on January 21, 2015

Appreciate your quick responses. Thanks for your help. 

 

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

Sign in to reply to this post.