These existing feature of Service Studio CSS Tags is a very nice feature to use when making custom components. Example Service Studio CSS Tags: ``` css .component-wrapper { color: black; -servicestudio-color: red; } ``` My idea is expand on the Service Studio CSS Tags for CSS Selectors such that an entire selector can be conditional shown in ServiceStudio using just one -servicestudio- prefix. Example Service Studio CSS Selectors : ``` css .component-wrapper { color: black; } -servicestudio-component-wrapper { color: red; } ``` Ideally anything using the -servicestudio prefix should removed from the runtime CSS at compile/deployment time.

Continuing on the good pattern of Service Studio warning about unused elements, also address the unused private web blocks.

Hi, My idea is to have more AI assistance on the logic side. For example, when we text or speak to an AI assistant with a command like "Hi, create a wrapper action for the User table," it should generate the corresponding action automatically. Thanks, Prasath P

Add column on TrueChange tab to show the location (web page, action) of the error that is being shown.

In Service Studio, Allow double-click to toggle entity attribute property values. e.g., "Is Mandatory" = "No" (by default). Double-click the "No" to toggle it to "Yes". Double-clicking the wide "yes" bar background is faster and easier than locating the drop-down arrow, and then selecting the other value. Also, when navigating via tab, consider allowing the "space" key to toggle the value. This is also faster than having to find the Y or N key. For property values with more than two options, just iterate through the options. PS: As a new user to Service Studio, double-click and space were the first options I tried in both navigation scenarios.

The AI Mentor currently provides visibility into 'Unused Actions in Modules' and 'Unused Aggregates or SQL Queries'. Similarly, introducing a feature to identify 'Unused APIs' would greatly benefit developers by enabling them to efficiently manage their APIs, thereby mitigating potential security risks.

Hi everyone!We use cloning modules for developing features that after get merged into the original module.When publishing a cloned module, Service Studio publishes it to the application "Independent Modules". We then need to go there and move it to the correct application.It would be helpful that when publishing a cloned module, Service Studio would ask in which application the cloned module should be placed.--Tiago Bernardo

I have the need to organize applications and modules in multiple ways and want to be able to add multiple labels to the application. So that I can filter by label(s).E.g. label Orders to identify all modules that are in the Orders domain. Another label could identify the module layer and jet another one to identify the team responsible for the module.I would be great if there was a link to Discovery for these labels so that the architecture is defined inside service studio.

If you copy a variable from a screen and try to create a client variable just by pasting it is not created.This copy paste mechanism is very handy in the platform, and it would be very helpful to have it.Real examples:1.I have a screen in traditional I'm converting to reactive.This screen has 15 session variables, I'm able to copy them and paste them from one module to the other and paste them as variables but not as client variable. In reality SS only allows us to paste cliente variables to client variables folder.

For improving WCAG compatibility we need OS to include a couple of additions when it generates an error message. For a screenreader to pick up the warnings/exception messages the platform should include a ARIA role like: role="alert". I see no reason why these shouldn't always be included. ( also when de accessibility feature is disabled ) Additionally, it should be possible to tab to the message so that it can be dismissed; currently the keyboard-focussable is off, but it should be on. We are now reverting to popups as these are requirements for a successful implementation of WCAG compatibility.