What I mean is indeed what Michael says. Wwhen you create a view that the sf disables by default the crud buttons. If the view will be used as editable the developer must turn the crud buttons manually on.
Hi Jeroen,Every key user has acces to the test environment so they can test their processes but when we upgrade the test environment we don't want them to acces it until we send the mail that the upgrade is finished. After a upgrade we test a few different processes if they still work. So we need the application to be active. Sometimes a key user already starts testing while we are still working (testing) on the upgrade. So it would be nice if the application has a checkbox (for example test mode) so only certain specified users can acces the application without disabling and enabling the rights of every other user.
Hi @Mark Jongeling I would say inactive is not clicking or typing in the application. Only moving the mouse i wouldn't count as active. After the inactive period the user needs to be logout and the session in iam should be closed.A extra nice feature would be to be able to call a procedure when a user will we logged out due inactivity.
@Arie V unfortunately that is not sufficient enough. We also need the iam usr session to be closed.
@Arie V i mean it as a setting. So the developer can decide to show the task when it's a double click task or can hide it in the taskbar.
Planned→Working on it!
Open→Working on it!
Working on it!→Next release
Hi Guido,Unfortunately, it is currently not possible to influence the generated update statement by for example: excluding columns such as 'added_by' or 'added_on'. This would be a valuable addition. Could you create an idea for this?For now, the only solution is indeed to add an additional template (automatically) that first overwrites the new value for 'added_by' or 'added_on' with the old one before the update statement code is executed.You could also explore ensuring that the 'added_by' or 'added_on' is never updated via the default logic. This way, the handler initially does not receive the 'incorrect' data.Hope this helps.
Hi all,We have added in the upcoming release a way that you can exclude columns for the generated insert and update statement. These setting can be found via User Interface --> Subjects --> Columns --> tab: PerformanceThere you can uncheck if you don't want that column to be used in the auto generated statement. There are some restrictions for the insert handler checkbox. This can not be unchecked if the column is:Primary key Mandatory without default valueNote that it may break your dynamic model if you use select * into #cols from col. Please verify your dynamic model code and add the new columns if needed.
Updated idea statusWorking on it!→Next release
For the 2024.2 release we have introduced jump tasks to the main objects in the model rights screenTables Tasks Reports Process flows Subroutines
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.
