Data Sources FAQs and Best Practices

Note: This page describes features that are currently part of a technical preview and not currently available to all users. For more information. contact your Laserfiche service provider.

FAQ

How is this different from Remote Agent data sources?

Unlike Remote Agent data sources, setting up a direct data source to a database in Laserfiche Cloud creates an immediate connection without any intermediary components. These direct connections use provided credentials to establish real-time communication between Laserfiche Cloud and your database. This approach delivers better performance by eliminating the middleware and queuing processes that Remote Agent requires. Here are the key differences:

  • Query Rules with direct connections can use raw SQL queries, while Remote Agent Query Rules are limited to the graphical user interface (GUI) query editor.
  • Query Rules with direct connections can be used in Forms Lookup Rules, unlike Remote Agent data sources

Can I update an existing Data Source to use a direct connection?

No, you can’t update existing Remote Agent data sources to use a direct connection instead.

How does security work?

To use data sources with direct connections, your database must be accessible from the internet. Laserfiche Cloud uses fixed originating IP addresses, allowing you to whitelist them in your inbound firewall rules. You'll also need to provide the required connection settings for your database, including appropriate authentication credentials.

Which databases are supported at launch?

At launch, we will support only Microsoft SQL Server, with potential support for other database vendors in the future. Please review the documentation for specific database requirements.

How can this improve my existing solutions?

Real-time, direct database queries can significantly simplify solutions in Laserfiche Cloud. For example, instead of synchronizing data from an external database into a Lookup Table, consider querying the data directly when needed. This approach can eliminate the need for data synchronization Workflows and reduce the number of Lookup Tables required. Evaluate your existing solutions to see if direct database queries could make your Workflows and Business Processes more efficient and performant.

Best Practices

**Understand Laserfiche System Limits**

When connecting to databases through Laserfiche data sources, be aware of system limits that may impact your solution. These important limits include:

  • Connection timeouts
  • Maximum returned rows
  • Workflow iteration limits

Note: A full list of limits is available here.

**Good security starts at the database**

When setting up a database account to use with Laserfiche, ensure the account has the minimum necessary access to perform the required tasks. For example, if you only need to select records from your database to display in a Laserfiche form, grant that database account only SELECT rights, and only to the necessary tables.

**Use appropriate security controls in Laserfiche**

Apply appropriate security to your data sources and query rules within Laserfiche to ensure only authorized users and groups have access. For example, you can restrict data source access to system administrators while limiting query rule usage to solution designers. You can also use Project Security to implement access separation where needed.

**Write efficient SQL queries**

When writing SQL queries, only return the data necessary for your solution. Avoid using wildcard SELECT statements, as they return unnecessary data and perform worse than queries that specifically select required fields.

**Adjust your approach based on the situation**

Understanding the context of your query is crucial. When using a query rule in a Form to populate a dropdown list, ensure your query returns an appropriate amount of data and consider the impact on the end user's experience. While backend Workflow processes may require more data, always aim to return only the minimum amount needed for optimal performance.