Nicasio Design - Felix Figuereo
My feedback
123 results found
-
1 vote
-
1 vote
-
1 vote
-
1 vote
-
1 vote
-
1 vote
-
1 vote
-
2 votes
-
1 vote
-
1 vote
-
1 vote
-
29 votes
-
1 vote
-
274 votes
Evgeny Zaritovskiy
responded
Please review results of our analysis and design:
https://docs.google.com/presentation/d/1aBh3RKOIAbC-YOkpQtRJ8kv9kH3ZlXSID7Ezl1bCAlg/pub?start=false&loop=false&delayms=3000Post your comments/ideas right here. Until we see major disapproval, this is what we will develop in one of future releases.
-
225 votes
An error occurred while saving the comment -
9 votes
An error occurred while saving the comment Create event > publish it > in details add URL to 3rd party site?
-
369 votes
An error occurred while saving the comment long overdue
-
1 vote
-
1 vote
-
1 vote
Until this is a feature here is what we [at Nicasio Design] propose:
Client/Admin creates an event and adds a custom event registration field called "CEUs for Attendance" (or something similar).
-- this field would need to be the "Multiple Choice" option so the admin can preset the option of how many CEUs are awarded for the event, (1, 2, 3, etc.).
-- this is the only field type that allows this I believe (the radio option requires more than one option).
-- the admin would set the field & option be auto-checked and set to be required so a person is forced to leave it checked when registering.
Nicasio would create a process using the WA API and a CRON job (runs on a daily/nightly basis automatically) to check for events that have ended for the current day.
-- For events ended since the last CRON job ran, find those events' "Check-Ins" that the Client/Admin would need to be selecting at the event. (An admin can check-in attendees using the website's admin interface and/or the WA app I believe).
-- Once we find the persons checked-in we would grab their email address (provided via event registration form) to lookup their account info via the API.
-- For persons checked-in who are also members, we would then save the "CEUs for Attendance" amount from the event registration form to a field we would have already added to the Membership fields called "Obtained CEUs" or something similar.
-- The "Obtained CEUs" field would be a basic multiline "textarea" field that is treated much like the "Notes" field in the admin.
-- We'd add the data needed in a one event per line format, each time we need to update it for a member, something similar to:
2016/09/13, Event Name Here, 3 CEUs
2016/11/27, Event Name Here, 2 CEUs
2017/01/08, Event Name Here, 4 CEUs
-- the data would continue to append itself to this single field (or prepend if you wanted the dates reversed in the example above)
To create the API/CRON job script and to provide support/training for setting up events/etc. I'd estimate this to take roughly 20 to 30 Hours. Please note this is only a rough estimate and all WA API involved work is billed at an hourly basis.