Hello,When I go to my profile and I go to My Activity Tabs , It has Many Subtabs Like Forum, Activities, Ideas, Yesterday I was  searching for one of my Post comment, but Exactly don't remember the date, So I have to Scroll it to then After Scrolling to bottom "Show More Appear", So I have to do it again and again and I have to read each title. If Input "Search by Title" and "Post Content text" would be added it will save time and will be easy to find the right thing by right keywords.Thanks

Customers that use Outsystems on top of existing external database(-application)s have the need for customisation of the way they connect to these databases. I have seen changes on the database connection for: change of machine/database, change of schema, connecting with a user other than the default user and connecting with a proxy-connection. I have also seen implementations for other initialisation actions in the external database like actions for context-, audit- or debugging-information.Please don’t start any discussion on the need for these solutions. This is not a discussion but a fact for some customers.It would be nice if these customers have a proper way to implement their specific needs.The current implementation of set database connection (and sometimes even more initialisation-code) before every database-action in Service-actions, Soap- & Rest-api's, OnBeginWebRequest & Fetch data from other sources creates a lot of duplicate code.And any of these actions can easily be forgotten.These solutions are sensitive to errors.Since the introduction of mobile and reactive within Outsystems the need for a proper solution is getting more urgent.I would suggest a similar solution on the usage of database connections as is implemented on consuming Rest-api's: OnRequest- and OnResponse-actions.In the OnRequest the connection can be defined and any further initialisation actions like context-, audit- or debugging-information can be done if necessary. If needed, in the OnRepsonse code closing actions like clear the context and audit-/debugging information can be done.These actions must take place on every begin and end of the session to the defined database connection.I think the best place to define these actions is where the database connection is defined and maintained: ServiceCenter.The code to be executed can be written as a public action in a module.  The module.action to be executed can be selected when OnRequest and/or OnResponse on the database connection is switched on. There is no need to do any coding from within ServiceCenter; coding is done at the place coding is to be done in ServiceStudio.Setting the actions on the connection can never be forgotten.The code will only be created once and in one place.Best of all: it will work for traditional, reactive, and mobile and will make the move to reactive simpler.As a consultant I have been allocated to different companies and most of these companies use Outsystems on top of an external database. All these companies will benefit from this solution for the challenge they have in integrating the existing database(-application)s and the challenge of migrating to responsive.

 If am writing a solution or I can say If I am replying to a post and in the middle of that due to some reason our connection is lost or we cant post it that time b so it can move to archive for some time. Later on after a day if I haven't  posted it or did not make any changes to it, so it will be removed from drafts. removing it from draft can have many scenarios.Thanks,Tousif Khan

Hi Team,It will be good if we can have Absolute timeout setting within our OutSystems Application or infrastructure.What is Absolute timeout?All sessions should implement an absolute timeout, regardless of session activity. This timeout defines the maximum amount of time a session can be active, closing and invalidating the session upon the defined absolute period since the given session was initially created by the web application. After invalidating the session, the user is forced to (re)authenticate again in the web application and establish a new session.The absolute session limits the amount of time an attacker can use a hijacked session and impersonate the victim user.Both the idle and absolute timeout values are highly dependent on how critical the web application and its data are. Common idle timeouts ranges are 2-5 minutes for high-value applications and 15-30 minutes for low risk applications. Absolute timeouts depend on how long a user usually uses the application. If the application is intended to be used by an office worker for a full day, an appropriate absolute timeout range could be between 4 and 8 hours.You can read more about this here in the below link:https://cheatsheetseries.owasp.org/cheatsheets/Session_Management_Cheat_Sheet.html

 if possible like a editor for assignment widget in expended viewex: variable="value";variable1="value1";...and so on.It will improve the visibility of all the assignments and easy to manage add and edit variable.Thanks,Balasubramanian

Currently in Lifetime, you can configure site settings of modules being deployed in the Deployment plan.However, this is not available in the Lifetime API, meaning if you are using Deployment automation, you cannot automate setting the site settings for the modules that are being deployed.I think that since this is available (as an option) in the Lifetime deployment plans UI, it should also be available through the API.

It would be great to be able to open service center inside service studio instead of opening it in a separate browser and needing to login again?Or a seamless integration of both tools to improve the experience of setting site property value, running timer, and other things a developer usually do after publishing a change.

This should be beneficial for using the local functions to calculate any complex expression that is used or displayed on the page. As an example of usage I can give an example:Link and Button Web Blocks have a "Confirmation message" field. I want to be able to calculate the value of this field dynamically in client action that is in the context of a web block or screen so I can use data from local aggregates. For example, if I click a button inside the table or list - I call client action which calculates the Confirmation Message if certain conditions are met and this message is shown or not based on this condition. Things like this are possible in Angular and React for components.

Hi, - Complex indexesIn a large factory it's common to have indexes created directly in the database (ex: indexes with included columns).These indexes should be listed in Entity indexes tab to allow a complete management of the code. - Primary key indexesOutsystems automatically creates an clustered index over the primary key, but that index is not shown in entity indexes tab. That index should also be shown. Pros:+ more visibility of entity indexes to all developers+ easier to troubleshoot performance issues because we can see analyze everything in service studio.

Please can you add better filters such as A-Z or Z-A.With the new Trusted components the filters only allow filtering by 'Downloaded' or 'My Assets'. But this PER current user, not environment making maintenance/reporting difficult. Can these filters be added into Service center and synced with our environment (as we have many developers downloading forge components).Thanks!