This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
I built my own. One issue I run into is that there is no such thing, in our business, as a 'standard signup' system; nearly every event has a slightly different set of rules, for example:
Signup is limited to x for an event
Signup is unlimited for an event.
Event does or does not allow guests
If signup is limited and guests are allowed, then the system has to compute if any give user's signup with guests will push the total signed up over the limit and abort if that's the case. (web querySave agent)
Max signup quantity changes during the signup period.
Managing concurrent signups; the system should at least attempt to detect concurrence and prevent the 2nd (or third) person from completing the signup if that pushes the total over the limit. (web querySave agent does the heavy lifting)
Removing 'oops' signups (typically double signups by the same person)
Managing 'changed my mind' issues.
Web without authentication but still need to auto-input the user's OS login name. (hint, use JS to grab the user's OS name).
'Food' style signups are totally different.
I am not at liberty to share the apps I've developed as they 'belong' to my company but hopefully these few ideas will get you started on a dev path that will work for you.
This is an interesting problem and non-trivial. It's a good exercise in requirements management and flexible design practices.
Feedback response number WEBB9LTG7G created by ~Martha Lopjipyskioden on 07/08/2014