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

Question

Question

LF 12 and Tyler Permitting Integration

Laserfiche Integrations Version 12 Solution Marketplace
Updated February 25
asked on February 13

Good morning all!

 

We are implementing the Tyler Enterprise Permitting & Licensing (Tyler EP&L, formerly Energov) and Laserfiche integration that ECS Imaging develops (it's the one in the Solutions Marketplace) and are planning on upgrading to LF 12 soon. Does anyone on here have both the integration and the LF12 upgrade? Have you noticed any issues with the integration or things to consider that you wouldn't mind passing on? I did try asking our integration partner but they haven't tested the integration with LF12 yet so I figured I would try asking here.

 

Thanks!

0 0

Answer

SELECTED ANSWER
replied on February 18

Hi Hannah,

The Tyler EnerGov Integration by ECS Imaging page states under Features:

  • Direct integration using the EnerGov API and the Laserfiche API
    • A direct integration reduces issues with compatibility and long term stability upgrading either EnerGov or Laserfiche systems.

It doesn't explicitly say if "Laserfiche API" means the Laserfiche SDK libraries or the Laserfiche Repository (Web) API. As the integration says it supports Laserfiche 9, I strongly suspect it's an SDK library as the Repository API didn't exist at that time. Either way, both the SDK and API are compatible with Laserfiche Repository Server 12.

For feature:

  • Ability to access related documents in Laserfiche from Tyler EnerGov

Their video demonstrating this part shows opening a document from Tyler triggering opening the document in Laserfiche WebLink. The latest released version of WebLink is 11 Update 4. There is not yet a WebLink 12, and it's not schedule for the Spring 2025 Laserfiche 12 release. If this part of the integration works with WebLink 11 by generating WebLink URLs, there are no changes.

If you have Laserfiche and Tyler test environments, I'd personally be comfortable doing the Laserfiche 12 upgrade there and validating the Tyler integration still worked as expected. 

All that said, the above is educated speculation based on publicly available information about the integration. We can't officially certify specific version support for an integration ECS developed. I'd advise asking them to raise the priority of completing testing the integration with Laserfiche 12. It's not great to still have that as a potential upgrade blocker a few months after the Laserfiche 12 release.

0 0
replied on February 25

Hi Samuel,

Thank you for your thoughtful and nuanced response, I really appreciate the information you've provided.

As far as I am aware, the integration does use the Web API (because we have to install it as part of this Tyler integration set up, and are also configuring a DMZ, since we didn't have one prior). We don't use Weblink yet, so I think in this instance the integration generally involves workflows, metadata and hyperlink creation.

I did ask if they had plans to test with LF 12 when speaking with them last month and that didn't seem to be on their agenda for a while, but I will definitely try requesting that it be prioritized, because I agree that it's unfortunate there's no awareness yet given the release date of LF 12 last year and where we are now.

0 0
replied on February 25

If the parts of the integration you're using exclusively go through the Repository Web API hosted by Laserfiche API Server, you should have no issues. The latest release of Laserfiche API Server is still version 11, and like all version 11 client applications, it's fully compatible with Laserfiche Repository Server 12. 

Even when Laserfiche API Server 12 releases later this year, the "v1" API specification they must be using (v2 isn't currently available self-hosted) doesn't change.

1 0

Replies

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

Sign in to reply to this post.

Details
Related Posts
Loading ...