As Owner of an application I would like to ensure that no one could promote it above a certain environment (example above QA environment).

 Current State: To link a deployment key obtained from the Lifetime API with the Lifetime user interface, it is currently necessary to map the platform entity osltm_staging to retrieve the staging id. This id is then used as a parameter in the Lifetime URL, as shown below: /lifetime/Staging_Progress.aspx?StagingId= Suggestion for Improvement: I propose two possible enhancements to facilitate the process: Option A: Allow the Lifetime deployment screen to accept the deployment key directly as an input parameter. Option B: Modify the Lifetime API to include the StagingId in its response. Implementing either of these options would simplify accessing deployment information, for companies utilizing the LifetimeAPI in their internal deployment processes. While acknowledging that a fully automated CI/CD pipeline takes away the need for the Lifetime interface, integrating these features would still benefit cases where the Lifetime API is used to enhance rather than fully automate deployment processes.

At an OnPremise OutSystems infrastructure we can schedule OSPTool to publish complete factory. OSPTool.com /Publish {<osp_file>|<oap_file>} <hostname> <username> <password>    | /PublishFactory <hostname> <username> <password>In a Cloud OutSystems infrastructure this is not easily possible.It would be nice if we could schedule the publish of a complete factory or a solution.

 ProblemIn Outsystems 11, and previous versions too, everytime we build a widget that has a higher z-index relative to the page we struggle on editing the content of the page since we have another element above the normal content of that page. Today's solutionWe can wrap up each of that widgets inside an if and toggle them whenever we need to only see the page content, or other widget content. Today's solution problemWrapping each widget with an if it's a solution for that problem, but everytime we have more than one element it could be a little unproductive to toggle each of them so we could change the view. Possible future solutionSo as a possible future solution I purpouse a multilayer view builder inside Service Studio. Whenever we place an element/widget inside a page that has a different z-index or a fixed position,  it could appear an option to select which layer we want to see at that time.This way we improve the usability while building complex pages.Thank you.

As like LinkedIn and X link options in profile section. It will be better to have our OS User Group Profile link in our profile page. Regards Murali

When installing a new machine it would be useful to select and install multiple forge components at the same time.

In ServiceCenter  Error Log and General Log change the ID number by the eSpace Name :

More often than not forum posts have been successfully answered but the original poster never bothered to mark the answer that helped solve their problem as the solution. A post marked as solution is very useful for others looking for ways to address the same problem.A lot of people in the community can identify the correct answer, but cannot do it unless they are the Original Poster (OP) or a Moderator.The idea would be anyone other than the OP could mark a post on an Unsolved topic as a "Possible Solution", subject to be reviewed by a moderator . If validated by a moderator, after a certain threshold of time, and if the OP still hasn't marked any post as the Solution, this possible solution would become the definite Solution (and credited to the person that answered it).In order to gameify this/make it more enticing for people to mark (potential) solutions, some small amount of points could be awarded to the person that initially marked the possible solution too.

As a reviewer, I often need to compare the current version with old ones and I need to check every single change reported by the Merge and Compare tool.  So I don't spend time checking nodes that just changed position I would like that the tool highlight those in a different color.Example:

Add an option to the Message widget to enable or disable auto-close. If enabled, allow configuration of auto-close duration in seconds.