Hello,In version 11.53.28 there is a new export image function for UI, logic and processes. This is a great future, however I feel like the position of the 'export x to image' button for actions should be changed. I believe that many developers are used to quickly adding input-parameters, which now leads to saving images. My suggestion is to move the export function down in the list, below the variables.

Currently, we use Cordova plugins hosted in GitHub repositories and integrate them into our mobile applications to generate builds but this will expose the plugin code in public, As an alternative, we can include the plugins as ZIP files within our module to keep the code from being exposed. However, when the plugin size is large, including it as a ZIP file can lead to timeout issues during mobile app build generation. Hosting the plugin on GitHub resolves this issue, but it introduces another challenge: the repository must be public for the MABs to access it. To address security we would prefer to keep these repositories private. Since mobile builds are handled by MABS (Mobile Apps Build Service), there is currently no straightforward way to grant secure, controlled access to private repositories. Proposed Idea: Provide a mechanism to allow controlled and secure access to private repositories during mobile app build generation. For example: Support authentication methods (e.g., access tokens or SSH keys) Allow configuration of private repository credentials within the platform Thank you,

 Greetings !!We often use 'Configure Tenants To Test Queries' on service studio while developing or tracing data across tenants while test.It would be helpful for developers to quickly know the tenant configured via a label showing Selected Tenant on StatusBar in ServiceStudio.This way we don't have to go back to > menu > module > configure tenant for test queries; to see the selected tenant.Thanks

The other day, I dealt with the Send Email action and noticed where there is an improvement opportunity that could be tackled with a small tweak. Unlike the selected Email screen, which includes a description, the Send Email action does not have a Description property. With regard to indicating the purpose of the email, adding a description Property to the Send Email action would help make the logic more straightforward, and therefore easier to understand and maintain.

I just recently found a "behavior" when using Integration Studio that is:you create an action;edit the code;go back to the IS and rename the action;open the code againAt this point you will get a new snippet of code for the newly renamed action and the old code that you had initially is still thereIt would be awesome if renaming the action in IS would actually rename the code instead of creating new code and leaving the old code as "zombie"

On minor releases, like chrome does.

Most of the times, Aggregates that fall under this Indicator are actually pretty simple Queries that filter by an Id, mostly the Primary Key of an Entity. In which case, the Max. Records is really not needed, making this Indicator more annoying than helpful.

This idea was stumbled upon trying to generate a tree list from dynamic source (table/aggregate, JSON etc). Due to dynamic source, the depth of the list is unknown until run time, so hard-coded solution is not possible.Logically this leads to using nested web blocks, taking the current object and listing its children, recursively so that each child then also displays its children. So on, so forth.Despite the data source in this case always being finite (hence, recursivity will not form an infinite loop), it is still not possible to induce web block recursivity in this way. Proposal: Allow Web Blocks to be recursive, detecting whether infinite looping will occur or not.

Currently we don't have any strongly typed way to manipulate lists, and it would be a boost in productivity in many scenarious, if the platform supports these operations out of the box and strongly typed. To acheive this, it would be nice to have a "Green Aggregate" that receives a list, calculates automaticaly the source structures/attributes based on the input list, and allows to do operations like MAX, MIN, GROUP BY, Sorting and Filtering. This kind of aggregate wold behaviour just like the actual aggregate does for database entities, except that joins would not make sense in this case.

When opening service studio you see a screen with the list of the applications running on the factory. The applications are displayed in a "windows tile" pattern.  This screen is not usefull if you have a lot of applications in the factory. My sugestion is: OS should develop a service studio entry screen with display options like "windows explorer view options":-tiles (as is)-details-listThe other ideia is to allow search options in this screen