Everytime when changing a role name in SF, we need to assign it to User Groups back again in IAM. Probably because of User Group <> Role matching is done based on their names instead of unique ID's?This brings a risk of forgetting to re-assign it completely to all relevant User Groups. Renaming Roles should not require re-assigning at all in my opinion.
Related to push-notifications topic, I have an idea which is verry common in modern applications and that is mentioning other users with @user1 @user2 @usergroupA so that you can actively interact with other users or even user groups related to a specific record.For example to ask questions, or give important updates, or to request additional actions (review) or whatever it might be.
Context:As a citizen developer, I want to be able to hide BADGE icons for certain users, so that it attract unnecessary attention. Menu with BadgesThese badge icons are currently being shown to EVERYBODY who has rights on this menu item. But the BADGE icon is ONLY introduced for the roles Billing address validator and Payment detail validator in order to attract them to these unverified items.
ContextWhen opening a Lookup screen, this object could have multiple detail tabs. In attached GIF you can see there is a lot of detail tabs for ‘Vessel table’.The user wants to easily navigate to the relevant detail tab, so instead of clicking 3 or 4 times to the right which triggers moving detail tabs, it should be much easier and user friendly when clicking on the arrow (>) opens up a dropdown of all available detail tabs from which one detail tab could be chosen. This feature/concept could also be applied to regular screens, not only lookup screens!
Currently users are allowed to pick any date from the date picker and try to save a record. Whether the chosen date is allowed or not is being validated upon saving the record and a ‘warning’ below will let you know that it is not allowed to select this date. Users are forced to cancel the record and find out what would be allowed as input. It would be much better when we could block dates which are not allowed to be chosen. For example: Startdate of a new contract could not be in the past. How nice if we simply block these dates for the users in date picker. Just like booking a flight ticket (if there is no flight, you can't select these dates)
Just like in Windows Explorer (left bottom of your screen), it would be nice to see how many rows are selected in the grid + total rows. This will help users to identify the number of (selected) records without the need of counting it 1-by-1.
When modeling roles, you can easily verify this using Role Simulation in SF.It is very valuable to have Role Simulation function after IAM (No matter which GUI), just like the User simulation option we have now. In addition, it would be useful to have ‘User Group Simulation’ option. This enables our testers to efficiently test Role settings on Test Environment. Otherwise you are forced to use User Simulation and when there are multiple user groups or roles linked to a Test_user, you’ll need to assign / revoke user groups and roles repeatedly in order to test just one Role or one User Group.
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.