Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PersonalSiteContactInfo: Broken Link If Volunteer Shift Added to Field Set #470

Open
jesslopez-sf opened this issue Jan 2, 2020 · 3 comments

Comments

@jesslopez-sf
Copy link

jesslopez-sf commented Jan 2, 2020

Use Case

If a customer adds the Volunteer Shift field to the PersonalSiteContactInfoHistory Volunteer Jobs Field Set, it shows up as a clickable link for volunteers. However, when they click on it, they are directed to a PageNotFound error.

This is happening because it is a standard "view" link in Salesforce and resolves to the Id of the record vs. how we handle a coded button on the scheduled shift component that directs volunteers to the GW_Volunteers__PersonalSiteJobListing Visualforce page with specific parameters.

Steps to Replicate

  1. In a V4S org, create a volunteer campaign, job.
  2. For that job, create one shift in the past and one in the future.
  3. Create a new contact
  4. Add that new contact to each of the newly created shifts.
  5. For the shift in the past, change the volunteer hours record status to Completed.
  6. For the shift in the future, set the volunteer hours record status to Confirmed.
  7. Ensure/Create the Volunteers Site and follow any config steps to get the site up and running.
  8. Update the Volunteer Hours field set PersonalSiteContactInfoHistory to include the Volunteer Shift
  9. Copy the contactID of the contact you've assigned to these shifts
  10. Navigate to the /GW_Volunteers__PersonalSiteContactInfo?contactid=
  11. Click on the link for the shift in the Your Recent Volunteer History - you should be rerouted to the PageNotFound page.
@jesslopez-sf
Copy link
Author

**lurch: add

@jesslopez-sf
Copy link
Author

This issue was split from its original Issue: #438

@LurchTheButler
Copy link

Tracking W-038420

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants