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

Discussion

Discussion

Will These Cloud Enhancement be Coming to Forms on Prem?

posted on April 9, 2024 Show version history

There are some really interesting things announced for release to Cloud, and I'm really hoping these are planned for on Prem release too.  Any chance that these particular items are planned?  And if so, any idea when we may see them?  I would love to have all of these...

  1. From the March 2024 release:  Web Request Rules in Forms
    Form Lookup Rules now natively support Web Requests, allowing forms layout designers to easily and more securely integrate any 3rd party API data source, as well as the Laserfiche API.
  2. From the April 2024 release:  HTML in Field Settings
    Designers can add simple html markup in labels, text below/above fields, and tooltips across all form fields. You can add simple break tags to break up labels, or even add button and input elements wherever you want. Leveraging this new HTML markup, along with HTML events, lets you create a highly customized interface within the Form Sandbox — no custom HTML fields required.
  3. From the April 2024 release:  Form Date Field Update
    We have enhanced date field configuration so users can set dates relevant to when they’re filling out the form. You can set minimum and maximum valid date ranges using options like the current date, day after current date (tomorrow), or relative dates. Additionally, you have control over which dates are selectable within the calendar picker, including specific dates, weekdays only, or custom criteria based on JavaScript functions. Explore our documentation for practical examples and creative ideas.
  4. From the April 2024 release:  Form Signature Field Enhancement
    Signature fields within the new form designer can now be marked as read-only if they were signed in a previous step in a process. This means a single form can be used across multiple steps while displaying previously signed fields, and without having to render the entire form read-only
4 0
replied on April 9, 2024

I appreciate the excitement around these features. I know they are needed! Items 2,3,4 are definitely coming to LF in the next release. Item 1 is less portable because of the difference between lookup rules in cloud vs self hosted. I will relay this to the rest of the product team though!

3 0
replied on April 9, 2024

I'm excited to see 2,3, and 4 come to self-hosted. #1 though is becoming more and more important for us as quite a few data sources are now hosted by 3rd parties and not in house. Having to kick a Forms instance to a workflow is not the best end user experience since they have to submit it and have it come back to them.

2 0
replied on April 9, 2024

Agreed, APIs are much more pleasant to work with once you figure out the authentication haha. Maybe this feature could get you to cloud 👀

In all seriousness, your input has been noted. I would love to see this and other Process Automation features supported in self-hosted

0 0
replied on April 10, 2024

I totally agree with Blake.  I've been asking for the ability to work with APIs (and in a similar vein the ability to call a Workflow and receive a response within the form) for years.

Blake is right that a Workflow needing to run in-between tasks is less than ideal, which is why I mention being able to deal with the Workflow on the in-progress form.

I know Blake and I have both worked with APIs via JQuery code within the Classic Designer, and within Workflows too, but having low-code or no-code built-in functionality within the Form would open so many doors for us and other users.

2 0
replied on April 10, 2024

Adding my votes for these features as well - #4 is a serious deficiency with the Forms Designer right now and is causing us to not use the signature field.

 

 

2 0
replied on April 10, 2024

I agree @████████ - I had to do a complicated workaround on a process to handle that signature issue.  I had to have secondary signature fields that were always read-only and a Workflow to copy the signatures from the editable fields to the read-only fields, and then Field Rules to decide which to show and which to hide.  It would be drastically better to just have the single fields with Field Rules to choose when they are editable and when they are read-only.

 

0 0
replied on April 10, 2024

I agree, especially about the Web Request/API functionality. With more and more products using APIs and many being hosted in ways that don't allow for direct database access it would be incredibly beneficial for us to be able to perform API lookups without using workflow or exposing credentials in the JavaScript.

4 0
replied on June 13, 2024

Adding in my vote for the API functionality!!!

 

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

Sign in to reply to this post.