Assuming you have
Users > Public Groups
, not Chatter Groups, Not any of the generic groups like "All Internal Users) with at least 1 user in itAssign the object to members of the group, sequentially ("round-robin") the object via Process Builder
Assign Objects
from the apex classesIt's automatically creating a custom setting for each combination of object/field/group and tracking which group member received the last assignment.
There should be no reason to touch this setting unless you feel like deleting something no longer in use.
I used the dreaded without sharing
keyword because I ran into a scenario where process builder was triggered by an action in a customer community (whose users don't have groupMember object access) and so an error was being thrown
Because of how I'm creating a unique tracker for each setting (using object/field/group) if you have some really long descriptive names it's possible to overflow the allowed length for a custom setting name (40), so that's capped at 40 char. This may result in truncation in the custom settings name.
That doesn't impact the functionality but might make it harder for an admin to look through the custom settings and know which one is which
It's a developer controlled package. Use the 04t...
from the latest version in sfdx-project.json.
put that in your url like /packagingSetupUI/ipLanding.app?apvId=04t6A000002HkBGQA0
where 04t6A000002HkBGQA0 is that 04t
core sfdx
sfdx force:package:install -r -p 20 -w 20 -i [get the versionId from the sfdx-project.json file] -u [orgAlias/username]
alternatively, if you're using my sfdx plugin it's just
sfdx shane:github:package:install -g mshanemc -r roundRobinAssigner -u [orgAlias/username]
Log an issue here in github. Not an officially supported Salesforce product, just sharing to be a nice person.