The AI Mentor Studio is already very powerful but we always look for new ways to make it even more helpful. Currently, alerts are assigned to the last person who modified an element. However, in some cases, the alert is triggered due to changes made by someone else. Adding an option to manually reassign alerts would help ensure they are directed to the most relevant person. Hopefully these suggestions will be taken into consideration :) Cheers, Vanessa Espírito Santo

Certification exam for each type of course is difficult one, sometimes we know the answer but due to lack of sample questions practice we choose wrong answers during exam. Since exam is associate with some cost, so it will not be worthy for candidate to loss the Exam in any category.We can put some validation condition to have the access of Question Bank, like: Training videos should be mark as completed, Sample APP should be created and submitted by candidate's personal environment and candidate should have attended Boot camp related to it.This will increase the chance of clearing the exam as well as boost the confidence in candidate. We can also associate some price to these question bank.

It would be really good to have a list of all unconsumed public elements from a producer module.This would be of great help in 2 scenarios:- while review code from other developers- while working on an application that was developed by other teamsIt is very common that code gets developed with a purpose in mind, but somewhere down the line it becomes obsolete or ends up not being needed. If teams are not methodic, a lot of unused public elements end-up bloating up the module. I am currently working on a project developed during 2 years by another company. I constantly find unused public elements all over the place. They obviously are obsolete, and if my team needs some of that functionality, most likely we will develop from scratch rather than have to search if some code exists for the purpose we need. Hence, unconsumed elements are as pure trash on the application. But there is no way to make a bulk clean up. It would be great to be all to see a full list without having to go one by one.

If I have applications installed from Forge like "SilkUI Framework" or "Google Maps", Service Center and\or Service Studio could notify me if there are newer versions available.This way Forge would work like a real App Store and notify the users each time a new version of an app is available, and with a click we could instantly update those apps.This option should be configurable from Service Center \ LifeTime.

Provide the ability to set the extended properties on reactive emails in the same way they are available in traditional. There is currently no way to set extended properties on reactive emails, this currently means we will have technical debt in maintaining an secondary application purely to send emails to enable setting importance, out of office suppression, expiry etcThe following is an example of the traditional extended properties in a traditional emailThe above is used to suppress out of office messages for mailings and prevents a deluge of out of office responses when a number of emails are sent.Importance is set on some emails based on the business process being followed e.g. high risk/value the importance can be set to High and the email client shows the importance of the email.The extended properties on the email has solved a number of issues with email visibility in a users inbox by adding the relevant property e.g. importance, sensitivity and also expiry has meant that processes that do rely on an email get the relevant attention required.

Allow "Dark mode" on New Service Center

Just like in Traditional Web, it would be nice to have a simple way of translation prompts/text/static entities.

It would be very useful to have a system event similar to OnApplicationReady but like OnSessionEnd or OnSessionExpire. The idea would be that whenever the user's session expires, the event is triggered and the necessary actions can be taken when the session ends.

When working on a large project it is common to do fairly much the same deployment each sprint into our QA environments. It would be great if we could setup the deployment in lifetime, give it a name and save for future deployments. We can sort of do this at the moment but you can only have one saved plus it saves the current versions of everything so if espaces are updated in the source environment you don't get those updates when you finally go back in and deploy the saved plan. It will still need to run all the normal validation checks each time and allow us to add additional applications before hitting the deploy but would at least save time adding all the same common ones each time. Yes we could do this by creating a solution and deploying via servicecenter but then it is a multi step process and we don't get all the additional reference checks and auto including from the validation step.

It would be nice to have Service Studio in a linux machine without the need of a vmware or VirtualBox. Even if it was with wine. I've heard about Mono. Is it true that with Mono you can run Service Studio in linux?