Skip to main content

Idea pipeline (top 25)

1816 Ideas

Use 'open lookup' as a start action for a process flowOpen

I would like to use the open lookup action (clicking the lookup icon) as a start action for a process flow.This would allow us to guide user actions when they click this icon.We often find that users click this icon while editing or adding a row because the lookup column did not display the object they needed. So they open the lookup and often need to disable a prefilter to see the rows they needed. Our users complain that this is hard to understand and to much of a hassle.With a process flow we would be able to automatically disable prefilters when they open the lookup, making the entire process more intuitive. Using a process flow for this allows us to configure which prefilters should be disabled and which may remain active.Implementing this also opens up all kind of nice features since so many things are already possible using process flows. We could also configure it to send a user to a form in edit mode so they can immediately add a missing row without any extra clicks for example.To illustrate how this feature could help, I have an example we are all very familiar with:Lets say I’ve been asked to review code in a branch that currently isn’t active for me. The ‘Branch’ lookup column doesn’t contain my colleagues’ branch so I open the lookup:It’s still hidden by the prefilter, which I need to disable to find the branch. This particular lookup is quite slow for us so this entire process is slightly infuriating.It would be very nice to immediately have the prefilter be disabled by a process flow so I only have to wait once and to save me a click. 

Freddy
FreddyThinkwise Local Partner Brasil

Making export/import of model(parts) smarter and increase productivityOpen

The good part about working the the Thinkwise platform for quite some years now is that you build up a lof of reusable parts. However it is very difficult to extract reusable parts from a model, export it and import it as a reusable base model. Two main ideas:Most basic, export model for environment A and import in into environment B, if the base models are not available in the new environment import fails. Also when a base model has a different name. In this case in both environments the date_helper was downloaded, however in one it had a different name.  More powerful, and if you really want to become a 10x developer ( ​@Arie V ) is to have the ability to export a part of an existing model to reuse in a different model or even better create a base model of it. Now it's pure manual labor to or remodel the things you want in a new model, or copy the whole model and clean up the parts you don't want. All manually.  Being model and relation driven, a nifty solution to pick a table, a menu item or starting point as such, and determine everything you need to export everything that relates to it. Another thing I would love to see is to have a function/procedure repository. The overhead of the Thinkstore model download is too large. You end up with 50 base models, all with 1 or 2 functions/procedures etc.. that do generic stuff.  Would be great if for example the functionality/subroutine parts could talk with a type of github repository that could be forked. No need to import full models, just reusable pieces of SQL code.