This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Bring back the Cache checkbox for Input tools. It's cool that we can cache individual tools in 2018.4.
The catch is that for every cache point I have to run the entire workflow. With large workflows that can take a considerable amount of time and hinders development. Because I have to run the workflow over and over just to cache all my data.
Add the cache checkbox back for input tools to make the software more user friendly.
I'm just submitting @neilgallen's idea from here. The labels in the results window are still white, which is no longer visible. You can barely see that they're indeed still there when you hover over them.
I've had several of my users complaining about the Visual Query Builder view after the last couple of releases. When you maximize the window, half of the screen is taken up by blank gray space and there is no way to adjust it and it's very difficult for those who do not know SQL to build their queries in this very small white space. Need to be able to adjust the gray space.
Typically I drag tools from the tool pallet to my workflow. Sometimes, when I need to insert a tool into my workflow, I will right click to get the Insert tool dialog to find the tool I want to insert between two existing tools. With the new UI, it is hard to see the tool categories as these were redesigned for the darker back ground. The preparation category is sandwiched between 3 other categories that start with "P" and I typically lean on the color/shape of the tool icon to find what I'm looking for. Now I have to read the text to really know for sure.
Perhaps you could lightly shade the middle of the tool category icons to make them easier to see or perhaps make the background behind the tool categories match the new toolbar color.
Tool categories icons are hard to distinguish since they are now just light colored outlines on a light background.
When saving a workflow to the gallery, the manage assets box is a fixed size. Due to the length of our file paths, the full path name is cut off. This makes it difficult when trying to package macros to select the correct box. I understand you can group assets by tool, however with the more complicated workflows this can still present it's challenges. I'd like to see this box to be re-sizeable.
The join tool currently does not allow case-insensitive joins, but the find/replace tool does. Additionally- even if both sides are identical, the join tool will not join "Sean's house" to "Sean's house" because of the non-letter character in the middle. Finally - if one side is a string(2), and the other is a vString(200) - even if you have a single identical character on both sides you get uncertain outcomes unless you force the type
Please could you consider amending the join tool to include 3 new options or capabilities:
- Case insensitive join
- Allow full Unicode character set in join
- Full match across text types (irrespective of string size) - this would allow a string(2) value to match to a string(100) value as long as the string(100) value only has the same 2 characters in it as the string(2) value
That would remove a load of work from every text-join that's being done on every canvas we do.
When developing a module, I generally BROWSE the final data until I'm ultimately ready to generate output. Then I need to add or replace a browse tool with an output tool. Perhaps a general purpose output tool could save time for developers where the output tool functions as a browse tool until the output is actually checked on the tool configuration.
Taking this a step further, if an output is defined and the module is executed one could have a row limit on the read of data into the browse function of an output tool and see the first N records within a browse/output tool.
When running an app on your desktop, nested radio buttons work wonderfully. You can collapse groups and drill down to your heart's content. If you promote the app to the gallery, it doesn't work. I reported this as a bug to Client Services. Their response leads me to believe that they designed it this way. I'd like nested buttons to work both as a local app and as a gallery app.
Please star this idea if you agree...
This email has been sent to confirm that your technical support ticket has been closed. Please contact us if you need any further assistance.
Case #: 00095540
Case Subject: Radio buttons- different functionality between Gallery and local version
when using radio button to activate a sub set of questions that also use radio buttons then entire group has to be unselected then reselected to make additional change either activate/deactivate selectoins.