When editing translations in Service Center and defining which strings should be translated and which should not, Text found in Style Classes is also added to this list. Translating CSS adds unnecessary risk and complexity to the application. Ideally Text used in Style Classes is either ignored or default behavior is "Don't Translate". it's generally not a common or recommended practice in web development when working with i10n or l18n. Current list of Text used for translations.

It would be nice if we can remove all teams roles from a user in Lifetime instead of pick them one by one. This will be more efecient in factories with large number of teams. Thank you

On SS give a warning to user after clicking 1-Click-Publish with an option to cancel it when the espace being published belongs to a currently publishing solution

Sustainability and green IT is becoming more and more important for our customers and it's our responsibility as a company to help them build more sustainable applications and reduce the carbon footprint of the applications.According to this Forrester report "It’s 2020, and the industrial sector can no longer ignore the mandate for environmental sustainability. This is especially true for technology."There are many ways to do that but one possibility is to detect and report bad practices (or areas of improvement) in Architecture Studio. Several articles describe how to improve the carbon footprint of the app: https://gr491.isit-europe.org/en/ https://greensoftware.foundation/articles/10-recommendations-for-green-software-developmentEven though a lot of recommendations are pertaining to the organization, methodology, specification, etc. there are several elements we could try to detect:size of the images, videos, too big compared to the actual size of the area where they are displayed on the screenunused pieces of logicdetect unused screens of featuresdetect unused data (aggregate that retrieves data that are not displayed)etc.

In Mobile and Reactive apps we can "Fetch Data" from the Database, Local Storage and Server Action. This allows to retrieve data asynchronously. What I'm currently missing is doing the same async action but then with a Client Action. WhyI can use this, for example, by some data from the database, parse it and/or verify it and return the needed data (for example the number of items that can be send to the backend based on certain criteria). Current - bad- SolutionCurrently I need to "hack" my way around it by defining a few local entity that will never store data. "Fetch Data" from that entity and then call my Client Action in the "On After Fetch" action. This not really developer friendly and hides some important stuff in not readily visible screen actions. I'm also not sure if the "On After Fetch" action will be handled by another thread and not blocking the UI. All in all, a bad alternative.

Hi,We're using templates with reminders to guide our developers however we are limited by what can be done with reminders.It should be possible to order the reminders so they can be shown in the order on which the activities must be performed.A very good nice to have would be to have the possibility to filter reminders from warnings in the true change tab.Cheers,Guilherme

I want to be able to view the whole content of a variable,,, especialy usefull when processing Files (Export a BinaryData PDF or a large string XML).

Hi Team, I have checked the iOS Info.plist file, and by default, the property NSAllowsArbitraryLoads is set to true. Currently, this value cannot be overridden. While I understand that we can configure and enforce HTTPS connections at the server level, this property setting goes against iOS’s default security best practices. Moreover, when publishing the app to the App Store, we need to provide justification for having NSAllowsArbitraryLoads = true. I would like to suggest the following: Provide an option in the Extensibility Configurations to set NSAllowsArbitraryLoads to false, or Set this property to false by default, allowing developers to define their own approved domains (as explained in the documentation). This will help align the app with Apple’s recommended security standards and simplify the App Store review process. Reference: 🔗 https://developer.apple.com/documentation/bundleresources/information-property-list/nsapptransportsecurity/nsallowsarbitraryloads

In an exception handler, it should be possible to re-raise the original exception if it could not be appropriately handled using the same Exception type for processing further down the line.Currently we have access to the ExceptionMessage but NOT the Exception (type) meaning that if we re-raise the exception we have to choose a type (which we typically don't know).  I end up having to create an "UnknownException" type even though the original may have been a standard type so it may not be appropriately caught later down the chain.

Every plugin should have basic steps to use plugin.Like GIT website