When dragging and dropping widgets onto the screen in Service Studio, the platform currently gives generic names like Button1, Input1, TableRecords1, etc.

This idea proposes that OutSystems automatically generate meaningful names for UI widgets based on:

• The widget type (e.g. Button, Input, ListRecords, Dropdown)

• The label or placeholder text associated with the widget

• A convention/prefix per widget type (e.g. btn_, inp_, list_, ddl_, etc.)

💡 Example:

• A Button with label “Submit” → suggested name: btn_Submit

• An Input with placeholder “Email” → inp_Email

• A ListRecords showing products → list_Products

• A Checkbox labeled "Accept Terms" → chk_AcceptTerms

✅ Benefits:

• Saves time by reducing manual renaming

• Improves consistency and code readability

• Makes screen actions and widget references easier to understand and maintain

• Helps enforce naming conventions across teams

• Enhances developer productivity, especially in large teams or fast-paced projects

I am not sure about the necessity of this idea, as I do not usually need to name every element in the widget tree, and OutSystems do this to an extend with inputs for example, when binding the variable to it.

However, I think you should change your idea's category to "service studio", as it affects the developers while developing their application.

Hi @Mustafa Emad Shaker 

Thanks for the feedback!
You're right — this idea is more related to the developer experience inside Service Studio.
I agree the category would fit better under Service Studio, since the auto-naming convention directly impacts how developers work with widgets during application development.