Salesforce Facts by Abhishek

There are times when we need to add a particular user to multiple public groups and queues. Now, based on the OOTB option, we can do that by going to each and every public group or queue. We can create a screen flow as well to assign a particular user to multiple public group or queue at once to ease the work for users. Attached are the screenshots.

There is an option 'Apply to Child Territories' while setting up a territory assignment rule. Let's see how it works. Suppose we have two territories 'Test Territory2' and 'Test Territory4', Test Territory4 is the child of Test Territory2. We have setup two rules for each of the territory as below: 1) for territory2, Account Industry equals 'Agriculture', Apply to Child Territories option checked. 2) for Territory4, Account Type equals 'Prospect', Apply to child territories option unchecked. Now, if an account only meets the first criteria, it is assigned to territory2. If an account only meets the second criteria, it is assigned to no territory. If an account meets both the criteria, it is assigned to territory4. So, if the Apply to Child Territories checkbox is checked, the rule condition of the child territory is checked in conjunction with the rule condition of the parent territory. Attached are the screenshots.

There is an Activity Setting 'Enable User Control over Task Assignment Notifications'. If it is enabled, A section named 'Email Settings' appears in the User Settings page under Activity Reminders. With this option, the user can opt in to receive task assignment notifications. Reference:  https://help.salesforce.com/s/articleView?id=sf.tasks_enable_task_email_notifications.htm&type=5 Attached are the screenshots.

In order to use an apex class for filter-based opportunity territory assignment, the apex class needs to implement the  TerritoryMgmt.OpportunityTerritory2AssignmentFilter interface and it needs to implement the getOpportunityTerritory2Assignments() method. Reference:  https://help.salesforce.com/s/articleView?id=sf.tm2_enable_ota.htm&type=5

If we try to assign any permission set to any inactive user by mistake, we get the below error: INACTIVE_OWNER_OR_USER, owner or user is inactive. Org Id:<orgid> However, we can remove permission sets from inactive users.