Currently, it appears that separate policysets would need to be created for "On Run" and "On Save" events. However, since the same policy logic applies to pipeline scenarios regardless of whether it's triggered on run or save. multi-select functionality for event triggers within a single policyset would be quite helpful.

This would eliminate the need to create and maintain duplicate policysets for the same policy logic

Reduces administrative overhead and potential configuration drift

Improves user experience by simplifying policyset management