It would be great to have "findable" default widgets:

In some cases during refactoring is needed to find all usages of 'Input' widget or 'TableRecords' and currently there is no way of doing it.

Hello,

I realized that we can't search for an element in the search bar inside a module. So if we name all the elements it's impossible to find them all at once.

It would be great if that feature could be done. Due to a big size eSpace, sometimes it gets hard to search on all screens.

Very good idea!

Hello Vânia,

Sorry i didn't understand your idea,  you are trying to search a element from is type? like input, check box, etc... by Id?

With the best regards,

Gonçalo

A very useful idea Vânia Marques.

Hello Gonçalo,

Yes, imagine you want to make some changes on an element (Combo box for example) style. But all your elements (Combo boxes) have names already (Customers, Clients...), you'll have to search manually in every screen for that element and that leads to easy mistakes.

The search bar doesn't assume element names that have a custom name.

I hope it was more clear now.

Best regards Gonçalo,

Vânia M.

Hello Vânia,

Thanks for the answer, i'm just trying to figure out the difference between what exists at the moment and your idea.

In the search field, you can search in the screen or Module, isn't that what you need?

Sorry if i'm not understanding your idea correctly.

With the best regards,

Gonçalo

Hey Gonçalo,

Sure thing. No problem :)

So, it's not about where I can search but what I can search.

When you have, imagine, 40 screens and in some of them you have Combo Boxes (CB). And all CB have names, like:

It would be really practical if we could search for "Combo Box" and find all instead of searching one at the time like "Teste1" ..... "Teste40". 

So, the element default name is Combo Box. And if you don't change it, it's easy to find, but when everything is labelled it becomes really hard to keep track of all.

Sorry if it isn't clear.

Best regards,

Vânia M.

The idea does not seem to be very difficult to supplement given what they have today, and it is very useful even.

Really a good idea.

Why would you want to search by element, instead of search just by the ID or the class? Can you provide a use case for it?

What i imagine is, you search for the combo box, it will appear 40, what now? Are you going one by one since the name of the element will be just combo box and not the ID?

Ignore my use case, after some testing its indeed a good idea. 

Search for all the elements and if the element has a name it will display the name (Its obvious but just want to point out). Good idea!

Hello Vitor,

No problem :)
My problem is that all elements have already customed names so I have to search one by one.

That's why the idea!

Thank you

This is good Idea. Really helpful when we have big number of screens. 

It would help in big projects to find the elements.

If it means also search for all "Advanced SQL" widgets etc, I am very much in favour :D

HI, in order to ease to work to implement Multilingual Mobile apps (and maybe more), it would be nice to be able to search all the instances of a widget.

Like, using the search to locate all the text, label or expression widgets, and have all of them lined up, ready to be selected and jumped to.

I imagine this by having all of them in a DB inside OS with key value, yet, I have no idea how OS works behind the curtains.

Maybe I didn't explain myself very well, but I think it's understandable, and useful for mostly everyone

Thanks for the attention

 I believe that we need a friendly system to implement Multilingual in Mobile. But I did not sure about how !!

+1 

There should be an option to find usage of basic widgets in toolbox.

For example, there are  widgets like Form, Link  and many more present in the toolbox. We can find usage of server & client actions, local & input parameters, structures & entities. But we can't find usage of all the widgets in toolbox. If a user wants to know where I have used 'Table Records' widget in my application, then user don't have any easy way for it.

It would be helpful for users  if Outsystems implements this functionality.

Regards,

Rashmi Hatwar