Feature to allow RSVP for events

Scoutbook New Scoutbook Feature Requests
1

I would like a feature that when you create an event and you can invite people and they can RSVP to that event yes no or maybe once RSVPed we should be able to export a list a.k.a. rosterthat are going. I would also like us to be able to assign dollar amounts to the events as well as allowing the users to RSVP without having to login via some sort of authentication token embedded in the link.

If we can get this, I believe our troop will be able to migrate away from TroopTrack and use just scouting.org

2

This can already be done.

I’m not 100% sure this can be done, but I thought it could. Depends a bit on what you mean by export. What format?

I think national has rejected this request via SUAC previously, but maybe I misunderstood what was said by the SUAC. It was a while ago.

I’m not clear what the desired function is here. If it’s just a “listing”, that can already be done in the event description. If it’s having the amount automatically “billed” to the scout’s payment logs using the state of the RSVP, that’s a different animal. Would there be a cutoff after which it “bills”, or does it “bill” as soon as RSVP toggles to yes? What if they toggle back to no or maybe?

The more details you can provide about the desired functionality, the higher the chances of getting something that resembles what you actually want. Otherwise, the SUAC and developers are guessing when trying to write the user story for the feature.

3

There are too many features/functionality to summarize in very detailed ways via email or a forum post. I’m not a documentation kinda guy.

I would be willing to meet with someone to share my screen and show them what I’m looking for and they can either confirm it can be done an alternate way or they can ask questions, take screenshots and document it a way they can understand.

Export pdf in a table format that has all rsvpd yes members, with their amount due on the line with their name. Have a total line at bottom that automatically adds number of youth scouts, adult scouts and guests if enabled along with a total event cost to collect.

Even better keep track of if they volunteer to drive and how many other people can they take in their vehicle. Include this on the event roster pdf export.

Costs for events… be allowed to set costs in a field for each type of member. Scouts, Adults at a minimum and ideally non-registered guests. This allows youth to be subsidized at different rates than adult members and differently again for guests that aren’t registered. An RSVP deadline would be needed so that people can’t join last minute and not pay or get billed. But there should be admin overrides.

The above list of items would allow for easy planning of events, collecting money based on an actual roster going and prevent users from making changes after billing/rsvp deadline.

Someone replied to your post.

| Charley Hamilton CharleyHamilton
June 4 |

  • | - |

KenBerry:

I would like a feature that when you create an event and you can invite people and they can RSVP to that event yes no or maybe

This can already be done.

KenBerry:

once RSVPed we should be able to export a list a.k.a. rosterthat are going.

I’m not 100% sure this can be done, but I thought it could. Depends a bit on what you mean by export. What format?

KenBerry:

allowing the users to RSVP without having to login via some sort of authentication token embedded in the link.

I think national has rejected this request via SUAC previously, but maybe I misunderstood what was said by the SUAC. It was a while ago.

KenBerry:

I would also like us to be able to assign dollar amounts to the events

I’m not clear what the desired function is here. If it’s just a “listing”, that can already be done in the event description. If it’s having the amount automatically “billed” to the scout’s payment logs using the state of the RSVP, that’s a different animal. Would there be a cutoff after which it “bills”, or does it “bill” as soon as RSVP toggles to yes? What if they toggle back to no or maybe?

The more details you can provide about the desired functionality, the higher the chances of getting something that resembles what you actually want. Otherwise, the SUAC and developers are guessing when trying to write the user story for the feature.