Allow creating an action from the selected section of a flow. The action would get the required inputs and outputs, and the flow from where it was extracted should automatically fill the action parameters with the local variables it was using

Title says it all. :)J.Ja

when you upgraded or install a new platform server..- you have to install .net framework manually- configure iis manually- use the configuration tool- do a commandline command updatedb- start services- do a commandline scinstall- update recheck licence.why can't we have this all in 1 wizard and/or unattended install with a config-script.

I suggest adding an arrow to collapse or expand code ranges in the JavaScript Editor, similar to the functionality already available in the CSS Editor. It would improve the usability when working with large blocks of code.

When a developer opens an aggregate window or popup in Service Studio, the platform automatically enables the 'Publish' button, even if no changes have been made to the code or other application elements. This can be confusing, as developers might assume they have unknowingly modified something, prompting them to publish the application unnecessarily. I propose that the 'Publish' button should only be enabled when actual changes have been made to the application—whether in logic, UI, data models, or any other relevant components.

When we add non-mandatory attributes to structures (for example input/output structure of a Service Action), there will be no impact on the consumer modules ONLY if the added attribute is a basic type. You can read this in the documentation Handle Changes in Exposed Functionality , 'The following changes made in the producer do not have impact on the consumer modules: ' Add an optional Attribute (basic data types only) Structure In my perspective, there should also be no impact on consumers when adding non-mandatory composite/complex attributes like adding a record, or a list, or list record... Here is a scenario we are facing right now. We use Service Actions instead of internal REST API's to promote a loosely coupled architecture. There is benefit in using Service Actions as the platform handles the security and findability of Service Actions, whereas with REST API's, you have to do it yourself. All our Service Actions communicate with input/output Structures. When we want to add a non-mandatory structure to the output structure of the service action, then the consumers are impacted. Now both applications have to be deployed together, which complicates loosely coupled deployment strategies. Here is an screenshot to describe the issue.

It would be nice if we could maintain in the Architecture configuration a "whitelist" of self-explanatory names  that don't need a description.This list could have default already have the most common names like:*IdNameLabelDescriptionCreatedByUpdatedByCreatedOnUpdatedOnThe code analysis pattern Missing description on public element",  should then use this list and exclude reporting elements with names that are on this list.

Hi!The idea is:Set a module as Internal/Private relative to its application so that its public elements can only be consumed by other modules in the same application.When an element is set to public in a module it becomes available to be consumed by all other modules (with the exception of some rules that relate to the type of modules).But sometimes the public elements of a module should only be consumed by other modules in the same application because that module is just a supporting/internal module; its public elements should not be consumed by other modules external to its application.Being able to set a module as "Internal" or "Private" to its application to achieve the goal above would allow better control on the dependencies, improve on the architecture, and prevent incorrect consumption of public elements. I give two examples to support this idea:1) Integration Builder produces per integration two modules: An "IS" module and a "DRV".To use the integration you should only consume actions from the "IS" module and not from the "DRV" module, even though the "DRV" exposes public actions.This is even explicitly documented in Integration Builder.2) The Forge component "Human Readable Change History" contains two modules: an extension AutoEntityDiff and a module DiffEntityDataToText.Although of the extension AutoEntityDiff  exposes public actions they are only meant to be consumed by the module DiffEntityDataToText which in fact implements the intended functionality, but by mistake any developer can consume directly from the extension.For the possibility of modules being moved from one application to another application, consumer modules would become with outdated dependencies and when republished they would be broken if they consumed public elements from an Internal/Private module that did not belong to its application.--Tiago Bernardo

There should be a method where I can read html template with the data. So I can show it to the user before sending a email and user can edit if he wants. GetEmailHtml(templateScreenId, data) it will return rendered html so we can use it to edit and then pass it to sendemail method

When developing mobile app, you can use static entitities.However they are not available if your application is running offline.Most mobile apps we develop are based on offline first principal, making usage of static entitities useless.