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

Investigation: EDA Settings > Course Connections: Enable Course Connections #894

Open
jacebryan opened this issue Aug 15, 2019 · 2 comments
Labels
accepted Internal SFDO WI has been created Investigation Needs more information before work can begin and/or continue

Comments

@jacebryan
Copy link

Note: FOR INTERNAL USE ONLY. For support questions, please use the EDA Chatter group in The Power of Us Hub.
For feature requests, please use the Ideas tab in The Power of Us Hub.

  • Do you want to request a feature or report a bug?

Investigation

  • What is the current behavior?

EDA Documentation states: "If you created a trial org with version 1.16 or later, Course Connections are enabled by default and you can skip these steps".

Currently - a Course Connection can be created that links to a Student or Faculty record type without needing to set Enable Course Connections = true.

This behavior is happening in the EDA Trial, EDA scratch orgs and EDA production orgs.

@jstvz confirmed that the automation/installer doesn't enable the custom setting value by default.

  • What is the expected behavior?

TBD

  • If Course Connections are enabled by default for EDA trial orgs using version 1.16 or later why is the setting currently unchecked for those orgs? It would be less confusing to see it checked by default.

  • Since our EDA Trial version is beyond version 1.16 is there a need to keep this functionality? Same goes for needing to set a Default Active Record Type for both Student and Faculty (as it pertains to the batch process).

  • What is the motivation / use case for changing the behavior?

The behavior of the functionality seems to be a legacy solution that is no longer needed and may lead to confusion by our community of users.

@jacebryan jacebryan added accepted Internal SFDO WI has been created Investigation Needs more information before work can begin and/or continue labels Aug 15, 2019
@jacebryan
Copy link
Author

**lurch: add

@LurchTheButler
Copy link

Tracking W-035384

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted Internal SFDO WI has been created Investigation Needs more information before work can begin and/or continue
Projects
None yet
Development

No branches or pull requests

2 participants