@ajthumma Thank you for submitting your question to our community!

As I am thinking, my first instinct would be to utilize Custom Fields within the event submission form and rules that would trigger based on that custom field. How many different locations does your district have? This would potentially be a ton of rules! 

@Kathryn Carter ,

We have 13 locations.  The other problem with this is there’s no way to ensure the end user selects all locations that they are selecting a corresponding “room” for in the event.  Ideally, it would be much simpler if I was able to have the rules create multiple tickets when multiple locations are selected in the event registration ticket, but that’s not currently an option.  The other problem with the custom field is then the end user has to select the location twice which is tedious and puts even more steps on the end user in an already somewhat complex process.  Though if that’s the only way to do it we may have to look at that route.

@ajthumma 13 locations is actually not too bad. It would be a rule per field. Additionally, you could add the field as a subtask or subticket added by the agent working the ticket. Does that sound doable to add? 

@Kathryn Carter,

I’m not sure what you are referring to when you say to add the field as subtask or subticket.  Probably my biggest concern is that if someone has to manually add something, especially that’s already been added somewhere else, there’s a lot of room for human error to be missed.  I’m really looking for a way to programmatically solve this so human error is removed.  If I use a rule for event accepted with a condition of event location and then create one rule for each location telling it to continue processing if there is more than one location in the event will multiple rules process or will it only process the rule that matches the primary location?

@ajthumma If you add the rule, you will need to have a separate rule per location for the additional locations. The key would be to have the rule say it will continue to the additional rules. 

Does this make sense? 

Within rules, you will need to have a ticket template per location (built-in IT Ticketing) for each location. When the user submits the event, are they adding it within the location field, or are there additional fields they are working with? 

Do you have a screenshot of an example? Just trying to visualize your process here. 

ok, that’s what I was thinking would be required, just wasn’t sure if there were any other/better options or if it would actually work.  I did test it, and it does work, just requires extra rules and ticket templates.

Glad you were able to get it set! Please let me know if you have any other questions @ajthumma