For now, you can only manipulate the message, not the severity.You can do this by adding a hidden parameter to the task and show this parameter in the confirmation message translation. The hidden parameter of the task then can be set by the default procedure.
Hey Nathan,Thanks for your explanation. I see lots of people voted for this, so that helps a lot with getting this on the backlog.
Great example with the phone numbers. You convinced me that it could be very useful in that way.
Hey Michael,What do you think of my Inspiration Room suggestion? Is this what you need? Please like that item if you do :)
Updated idea status Planned → Next release
In 2021.2 made some caching-improvements to make the synchronization less heavy. This leads to big performance improvement when synchronizing an existing project version. We think that this will solve the problem behind the idea without implementing the suggested solution.When you are working with 2021.2 and find that this is not the case, please let us know so we can re-open this idea.
Hello Bas (and voters),To implement this idea, I want to put this US on the backlog:As a deployment specialist, I want to be notified when the previous version in my deployment package does not comply with the previous version of my database. We are thinking about adding the from-version to the upgrade script and making the upgrade script or deployer check on the previous version. I was wondering if you would see the need to store the previous version in sf_product_info, or that maybe our solution is enough to complete for your idea.
Hey Freddy,For your first point, I think you mean the code overview screen? That could be a cool feature to go from subject and from data model to this screen.I also really like the option to automatically do a code search on a table name. I did not think about that one.Thanks for your suggestions!
Hello Erwin, I've worked on a prototype to show a visual representation using the blog of Robert Jan as inspiration. This looks something like this:Next sprint we are going to try and merge this prototype into our DEVELOP, so we can hopefully deploy it with the 2023.2.
Hello everybody,Thanks for all the input!For the 2023.2 release, we have removed the “functionality” detail (not the main screen) and made it possible to jump to the code overview screen from:Process actions Process flows Tasks Reports Subroutines Data model (tables)We also made it possible to jump:From code overview to the control procedure and template. From control procedure - Result to other control procedures or templates. From data model (tables) to User interface - Subjects. From code search to control procedure, template or program object.We really like this feature ourself, but are also interested to see how this is received. Once you are working with it and notice that you are missing it on specific places, please feel free to add new ideas about those places.For now, we are going to close this topic.
Open→On the backlog
I get what you want, but I see one major disadvantage to this idea. When you use IAM to store which emails need to be sent (and as a log/archive which are sent), the data security lies with IAM. All system administrators can view the emails that were sent, including personal information. From a privacy point of view (GDPR or AVG in Dutch) this might undesirable. That is why I would recommend keeping a separate table to store and send emails from your system. Additionally, carefully consider which users or roles have access to specific data.I would love to have a Thinkstore (base) model that gives you a standard solution for this while keeping it in your own model/database.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.