Feature Requests: UI enhancements

OL Connect Professional Designer
1

May I please request consideration of the following UI enhancements?

  • Sort scripts by name, by type

  • Extend search to include scripts

  • Extend search to include multiple sections

  • Identify scripts which are redundant, because the ID or class selector is no longer present in the sections (Extend pre-flight checks and script panel). Note: this is different to evaluation per record, which currently already exists.

  • Add command-line utility to evaluate pre-flight checks using a source data mapper, so that it can be included in CI/CD processes

Thanks for the consideration

2

Hi iwest,

Thanks for reaching out, it is very much appreciated. I’ll discuss your suggestions with our team. Which version of OL Connect are you currently using?

Erik

3

2022.1.2, currently. I’ll review the release notes to make sure we are not doubling up here.

We have in excess of 30 sections and 200 scripts in our main template file. Currently this version of Designer its hard to manage the different parts and work out what is ready to be removed once it is no longer required.

4

Would it be possible to share the template with some sample data with me? It is always very helpful to observe what our users are doing. I suggest to do that using a direct message :wink:

5

Hi @iwest,

I’m not the product manager and haven’t seen your template, but I wanted to offer some thoughts anyway:

  • Sorting scripts is a bit sensitive because the order of the entries in the Scripts panel matters. Scripts run from top to bottom, changing the order may affect the output. We would have to make it clear somehow that after sorting the entries the order no longer represents how scripts behave.

  • There is a filter control at the top of the Scripts panel. You may have discounted it because you thought it would only filter by name, but it also searches through content.

  • As of 2022.1 there is a filter control at the top of the Resources panel that allows you to search through content, including the HTML source of all sections.

Of course we can still consider extending the Ctrl+F dialog, which also involves collating the search results somewhere. That way all search functionality is in the same place, and perhaps easier to find.

  • Good idea. We could extend the preflight to generate an error if a script is redundant across all records and resources.

  • That makes sense to me.