Sync the promo code data to Salesforce so that we can better report on promo codes, know when one that is scheduled goes live, know when one expires, and know if one was published.

Currently some courses have lots of people in the wait list. Some of these people are registered in the wait list months before the course starts. If there is an automated notification to remind them that they are still on the waitlist. And ask them to cancel from the waitlist if they already have some other plans. Hopefully we will end up only with those who are still interested in taking the course. So we can offer the course to those who are still interested and we don't waste time offering to those who are already have other plans.

We'd like to add some data from the activity, route/place and leader along with a few new questions to better analyze incidents that are reported. See Incident Report Form Updates, https://docs.google.com/document/d/1nJ23xjbb4sbU_lUvTBj36yVHcXaRfcNd3OMROdGp1Ns/edit.

As safety@mountaineers.org, I get an email when a participant answers "yes" to a "was there a safety concern or incident" question on a feedback survey about whether there was a safety concern on the activity, course or event. The participant's comments along with some meta data about the activity, course or event and the participant along with the participant's comments will be included in the email.

As an activity participant, I can report an incident, so that I can better communicate the details of an incident to the Safety Committee like the leader does.

When an Incident Report is submitted, we gather information from the activity, route/place, contact (leader), etc. to send by email and store in the data file. We also store the individual responses as content items and want the "autopopulated" info from the activity, route/place, etc. to be stored with each submission.

When checking whether to send an email to the Safety Committee (for all feedback forms) and whether to direct the user to the Incident Report Form (for activity-related feedback forms only) after submitting a Feedback Survey Form, in addition to checking if the answer to "Were there any safety incidents or near-misses on this trip? " is "yes," also check to see if the "Describe the incident or near-miss." response in NOT empty, If either is true send the Safety Committee and email and redirect the user to the Incident Report.

In Revise Save Data Adapter View, http://feedback.mountaineers.org/forums/273688-general-feedback/suggestions/37329700-revise-save-data-adapter-view-gh2941, we made it more difficult to empty the saved form data file, but for the Incident Report Form, we want to make it so that only Site Managers (the highest level of site admins) can delete this form or any per of it and hide the "Clear saved input" link from everyone but them.

The PFG "Save to Data" adapter view (see attached) make it seem to easy to delete the entire data set, because the "Clear Saved Input" button is too prominent. I think it would be best is the big blue button were changed to be "Download Saved Data" and we add a "Clear saved data" link at the right of the page.

Allow Safety Officer ability to submit an Incident Report tied to an activity, course or event on another person's behalf (e.g. from a phone interview).

(1) Change "Feedback" at the top of the page to the title of the feedback survey.
(2) Make the title of the course, activity, event or lodge stay a link to that item's details page.
(3) Add the leader's name and activity date(s) below the title.
(4) Add the title of the course template if the item is a course activity.

Add a feature or features that better handles misspellings and typos in text search strings. Two possibilities are: (1) a way to show potential spelling errors or typos like the red squiggly lines under such words, and/or (2) a feature like Google's "Showing results for {your corrected search string}. Search with {your original search string} instead."

As a site visitor give when I submit a search with text search terms, give me search results that are "fuzzy" so that I get a better and more comprehensive list of items that meet my search criteria.

By "fuzzy" we're thinking of things like singular vs. plural (e.g. leader vs. leaders) and first names (e.g. Ben vs. Benjamin).

It would help if when the leader enters a Routes and Places title that was previously a designated trail in planning a future trip if it clearly shows this trail is still included under a different route/place name

In order to make application processes simple for the applicants, we need to be able to allow the applicant to hyperlink other documents into an application, which we use a rich text field for. these rich text fields are not accessible (or even visible) on mobile, so we're getting applications with blank answers, and the applicant didn't even know there were questions they missed.

When importing books, use only the "Imprint" field from the Product Marketing object in Acumen. It appears that we are combing the Publisher and Imprint fields to make "Publisher/Print" and it's looking a bit messy:

For course template team rosters that have a slow initial load time, display the message, "Gathering roster data. This may take a up to a minute." until the roster data is displayed.