That new functionality is an awesome addition that I am already using to speed up this process.  What I am hoping to gain is in this scenario (although I have tons of other similar scenarios I would use it in):

Customer has an HR folder structure where they have 2 folders depending on the employee's status:

• Active Employees
  • A
    • Adams, Mary (12345)
  • B
• Inactive Employees
  • A
    • Mark Anderson (45678)
  • B

These customers are wanting nightly jobs that do 2 things:

• Move employees back and forth between Active & Inactive depending on their status in the HR system
• Update any employees who have information that has changed including but not limited to:
  • First Name
  • Last Name
  • Department
  • Position

Their HR system does not have a flag or date field that says when a record is updated so I am having to check every employee every night to verify their status and template data.  That means running a query for every document that has an employee id which requires me to loop through them one by one.  I am not wanting the document itself, all I am wanting is template data associated with the template so I can query the HR system to see if something has changed.  For small organizations this is no big deal but if we are talking a company that has 5000+ active employees and 100,000+ inactive employees then that is a ton of looping just to get a list of distinct employee id's in Laserfiche.  I understand that the queries to verify the data accuracy will take awhile no matter what but it shouldn't take long to get a distinct list of data from Laserfiche.  In SQL I can query a database with this many records and get back a distinct list in a matter of seconds.

Other customers are wanting a list of which employees have not filled out a form.  I then have to run a search for everyone who has turned in that form, get the employee id associated with it, and then query that against their HR system to determine who is missing.  Once again, I understand this will not speed up the query process against the HR system but it would greatly reduce processing time and server Workload if we could query the data in Laserfiche directly instead of via it's associated document.  I have requests for massive queries for Student Records, Invoice Processing, and a variety of other needs that could be sped up considerably with this built-in functionality.  Laserfiche is a goldmine of data and often times customers are wanting to work with the data itself and not the document it's related to.  It just seems odd that we can query all sorts of databases and that Laserfiche has its own query language (LFQL) but we do not have access to it without having to write custom scripts.  I understand I can write a custom SQL query against the database (with a ton of Joins) or I could write a custom SDK script but those queries take forever to write (& are hard for the customer to support) and most customers do not want custom SDK scripts.