Currently, it is only possible to have a 1 to 1 relationship between Activities and Events meaning that when you have an Event (as an example, a weather delay) that impacts many Activities a user is required to create many Events.
This change would allow many Activities to be associated with a single Event which would reduce the administration burden of having to create many Events.
Hello Duncan,
Thanks for raising this Idea.
I've marked it as "Will Not Implement" as, although I can see the benefit from an administration point of view, this change would have a fundamental impact on the Perform data model which would have repercussions throughout the system and the effort to make this change now would not be feasible.
Kind regards,
Luke