My question pertains to the add-on settings. I am building a webhook feature that requires a subscribedUsers settings field. It is a multi-select field that displays all available users. I also created an accessGroup field to allow for group selection.
I would like to connect the two fields, such that: if I select the supervisor access group, the subscribedUsers field is updated with the list of users that have this attribute.
My use case would require re-evaluating the subscribedUsers enum options whenever accessGroup changes. I am unsure whether the settings schema mechanism allows this kind of dependency, or whether I should instead:
• Precompute all relations server-side and expose a static dictionary {group: [users…]}, or
• Move the logic entirely inside the add-on logic (resolve user lists at runtime instead of in the settings UI).
If you think of any solution I’d gladly take them ! If there is none then I’ll consider a simpler configuration.
I’ve spent the day exploring Dynamic enums, and it looks really promising.
I really liked the idea behind the example-addon repository, I wish it was updated with the new features you shipped since it’s a good source of truth for quickly building settings, and helps circumventing the lack of up-to-date documentation.
Personally, I depend on our addons + ayon-backend repos and if there’s a setting or some feature like web actions, I’ll start finding the closest example to my idea and then stealing getting inspired.
It’s called inline documentation which is an additional source of information.
