Hello everyone,

The option of being able to add a folder inside the client action and action server is useful.

On the other hand, within the interface, there is no such option.


What do you think ?

Greetings to all and many successes.

CP

I want to be able to group my local variables into different groups in one Web Block or page. This way when I have very large scale forms I can manage my variables better. Basically I want the local variables to be able to go into drop down folders.

Let's say I have a form for a car.

Form Variables

? InsideCar

-Aircon
-SteeringWheel

? OutsideCar

-Bonnet

-Wheels
-PetrolCap

How about creating structures based from those variables instead?

I already do that. I create a record variable and customize the structure. The alternativa way is like Emman said

For pages where we end up having several local variables, actions, gets/aggregates (on react) when you are looking for a specific variable or action it can be alot of scrolling.  Inside each page please put the actions, gets/aggregates and local variables into their own expandable/collapsible folders.  So that if I don't want to see one section I can collapse it.

I have been wondering if there is something wrong I have been doing designing pages with lot of actions and variables while developing reactive web apps. 

Sound like a good idea!

Was about to post this idea. 

We can create folders inside session variables so Outsystems must implement to allow user's to create folders for screen local variables.

Please find the following screenshots:

Regards,

Manthan Shah.

Hi Manthan,

In Service Studio 11, you can create folders almost everywhere on the Logic and Data tabs, not just in Session Variables.

Why do you need Screen Local Variables in folders as well? Do you create so many of them per Screen?

Hi Kilian Hekhuis,

As I have many variables on the screen and I have many input box for those variables so it would be nice to have folders so we can categorise the variables according to the input fields as well as different part of the page. Please have a look at the below sample screenshot of some of the variables in the web-screen there are even more because it is a complex application of calculating insurance premium :-

Regards,

Manthan Shah.

Right, that's indeed a lot of them :).

wouldn't it be possible to organize them in form of a structure ? 

Structure is like a Json Object right ?

I would for sure had organized them in structures, there seems to be a Applicant structure as wel as a Premium structure

Hi Daniël Kuhlmann,

Yes you are right. But for a local variable there must be a folder as there are folders for all other variables i.e. session variables.

Regards,

Manthan Shah.

There aren't "folders for all other variables". In fact, Session Variables can't have folders either.

Hi Killlan

In Outsystems 11 we can add folders in Session Variables. Please find the screenshot below:

Regards,

Manthan Shah

You are right, completly missed that, thanks.

To add folders inside WebScreen to group actions and variables

Sometimes the list of actions and variables is very long that it is hard to find the action or variable you need.

+1

Sometimes you end up with a pretty unwieldy amount of local variables and/or screen actions on web screens - espeically if you're using a tab view. It'd be very very nice to organize them into more relevant groups instead of having a horrendous mass list.

Would be great if we can add folders within screens just like we can for entities and logic so that we can organize all our actions. 

Hi, I have a feature suggestion:

- Make Folders for Screens Interface Organization

-- I suggest the base 3 groups to be Organized (Variables, DataBase Feetching and Screen Actions)

--- Interface suggestion displayed below:

Cheers

Will these folders be by default, or only hitting a certain amount? Or that you can create a folder yourself?

Just trying to understand your idea

Possibility to organize the variables and actions present in the screens in folders and subfolders

It would be quite nice to have some sort of grouping mechanism similar to folders that can be used within a screen or action to group variables. This would not change the scope of the variables but rather just make it more manageable. For instance, instead of having 30 variables listed below each other on a screen, you could create a folder for all boolean variables or a folder that holds all variables associated with a certain use case etc.

It comes down to it being more manageable to have many variables, similar to how server actions can be grouped with folders.

Hi Stefan,

One way of grouping variables, is to place them in structures. For common group of input, output of local parameters this also promotes reusability.

Regards,

Daniel

Folder structure would be really helpful to organize the actions and variables on the screen.

Like the same feature, we have in client and server actions to organize the related actions together.

From the readability purpose of the screen, this feature is really helpful. 

Hi Mayank,

That idea already exists, so I will merge yours into it.

Regards,

Daniel

It would be amazing if we could group variables and even actions into folders per Screen in Service Studio just so that they don't all seem cluttered and to make scrolling less when there are a lot of variables and actions on a single screen.

I agree with the idea, but I will prefer that the folder appears by default. 

In my opinion, if we can create many folders to accommodate the local variables, it will become more difficult to find them, at least if they are created by other developers

Regards

I agree with the idea, but I will prefer that the folder appears by default. 

In my opinion, if we can create many folders to accommodate the local variables, it will become more difficult to find them, at least if they are created by other developers

Regards

I agree with the idea, but I will prefer that the folder appears by default. 

In my opinion, if we can create many folders to accommodate the local variables, it will become more difficult to find them, at least if they are created by other developers

Regards

We often have a few client actions in a screen, as one does, and sometimes find it difficult to quickly scan through for a specific one. It would be great to group them by functionality/concept like you can with global client action, just within the scope of the screen.

I've seen some ideas around having folders in the interface tab of Service Studio, for categorising screen/block level variables, actions, events, aggregates. I agree this would be a great addition for improving navigational efficiency.

However, I'd also like to suggest maybe screens and blocks could be stored in their own folders. This might be somewhat controversial as some may say that this promotes bad practices by keeping everything in a single end-user module, rather than breaking screens and blocks down into separate modules. However, I have worked on projects where there have been many screens and blocks in a single module, and many variables/actions in a single screen/block. It would be nice to categorise these to make my way around a module quicker.

Let me know what you think, as I think this could be great for efficiency, as long as it's used sensibly.

(When I say folders, I mean entirely cosmetic folders - an aggregate outside a folder should still be able to access a variable inside the folder, within the same screen, for example.)

Hi Adam. I agree with your idea. After so many demands for organizing items in folders why not also for Screens and Blocks

Regards.

Hi Adam,

I am agree with your idea it give better understand and easier to find organized based on the particular flow.

Many applications are using lot of local variables in their screens and actions as unmanageable one.

Is it possible to have some accordion kind or grouping based on its data type?

like boolean will have its own variables defained.

Text etc.,

In this way it will be looking neat and easy to understand.

seem to be a good idea. My big screen has thousand of variables. It should be categorized by grouping.

1000 variables I couldn't even think about it.

Hi , could we have the ability to group screen actions on the interface level , example, if I have multiple dropdown handlers it could be much easier to find a specific one if grouped , similar example it could be if I have multiple After..Fetches it could be easier to find a specific one.

Add folders within the end user layer in the interface elements, just for organization and better code visibility.

Give the developer the ability to add folders in blocks & screen that can hold local variables, aggregates and client actions. Once complexity goes up the long list of these elements can become difficult to read & takes up a lot of space in the UI. Allowing the developer to add folders so that they can group them by the type of elements that they are, or even to group the elements of a specific piece of functionality would resolve this.

It's interesting that you mention it. When I see a screen with too many variables, aggregates or actions, I immediately try to split it into modules to organize by sections as some may be reusable later.

And your wording "piece of functionality" is exactly that. Any reason you're not using modules?

In any field that involves working with data—whether it's research, business, or daily decision-making—it’s important to group variables effectively. Grouping variables helps in organization, efficiency, and clarity, making information easier to analyze and interpret. 

Grouping variables effectively is crucial for organization, efficiency, and insight generation. Whether you categorize by type, relationships, time, importance, or hierarchy, choosing the right method depends on the context and purpose of your data. 

If I have many of  this, it is better to have grouping of the variable for efficiency and maintainability of the Application

Having the ability to create folders on a screen or web block to store vars and organize them better since some screens can have dozens of vars making them massive in length. Thanks for your time.