We have a requirement to redirect support requests from Zendesk to Salesforce for the URL: Contact edX Support. Most of the relevant code is currently in the lms/djangoapps/support app in edx-platform
We can implement this change directly in the edX platform but since it’s a 2U-specific change, we’re considering moving this page to another MFE as well.
Do you have any recommendations on where we should move this support page to handle this change, or any best practices for implementing this type of redirection and transition?
Hi @aakbar If I understand this correctly, it sounds like specifically the thing you want to have more control over is the https://github.com/openedx/edx-platform/blob/master/lms/djangoapps/support/views/contact_us.py response?
If that’s the case, I think this is a good use-case for adding a new filter to the edx-platform repo. I can imagine that most operators would want to configure their support responses for the platform.
The default code in edx-platform should probably be simplified to just have a mailto: link or simple contact form and then if people want to do something more complex, they could change the response via a filter.
@mgmdi@Felipe does this sounds like a reasonable new filter to add to the platform?
Hi there, thanks for your response.
If I understand this correctly, I think it’s something like having the ability to send the form data from this page to a place like Zendesk, Salesforces or any other third party service that keeps track of such info and the search results can be fetched from the respective services. This can be a great addition to keep the contact_us form generic and makes this component more openedx-like.
Absolutely yes. That would be an excellent use case for filters.
2U could use a pattern that we have used before where there is a basic implementation, such as a simple contact form or a mailto link and adding a custom response exception so that advanced operators can do complex pages as well.