Snowfakery-Recipe-Templates icon indicating copy to clipboard operation
Snowfakery-Recipe-Templates copied to clipboard

EDA Success Hub Recipe

Open acrosman opened this issue 3 years ago • 3 comments

Create a recipe for the product formerly known as advisor link (now Student Success Hub).

It should include at least:

  • [x] Advising Pools
  • [x] Alerts
  • [x] Appointments
  • [x] Appointment Attendees
  • [x] Appointment Locations
  • [x] Availabilities
  • [x] Availability Locations
  • [x] Availability Topics
  • [x] Cases
  • [x] Case Teams (a.k.a. Success Teams)
  • [x] Notes (Case Comments)
  • [x] Predictions
  • [x] Queue Topic Settings
  • [x] Queue Waiting Room Resources
  • [x] Role Topic Settings
  • [x] Success Plans
  • [x] Success Plan Templates
  • [x] Success Plan Template Tasks
  • [x] Tasks
  • [x] Topics
  • [x] User Topic Settings

There may be useful ideas about what's really needed and how to build that in the SAL-CumulusCi repository.

acrosman avatar Oct 11 '21 21:10 acrosman

I got excited with all the commits!!! you guys are awesome!! @aaronwinters The recipe loaded beautifully though wondering with we want to assign a fake string to sfal__Topic__c's name field that the default is not the record id.

Screen Shot 2021-10-21 at 5 38 01 PM

@acrosman @prescod In order to support EDA Salesforce Advisory Topic recipe, we will need to add SAL repo to the sources in cumulusci.yml and execute additional flow to set up the dependencies.

like this:

sources:
    eda:
        github: https://github.com/SalesforceFoundation/EDA
    npsp:
        github: https://github.com/SalesforceFoundation/NPSP
    sal:
        github: https://github.com/SalesforceFoundation/SAL-CumulusCI.git

On the EDA instruction cci flow run sal:install_base --org dev

eehjunggnujhee avatar Oct 22 '21 00:10 eehjunggnujhee

Thanks for catching that @eehjunggnujhee! I updated the Topic object to populate more meaningful text in the name field.

aaronwinters avatar Oct 24 '21 07:10 aaronwinters

I removed the links to the two PRs because there is still work to do on this issue, but #70 is a great step forward. I'll review that, and likely merge it, with the expectation that we'll add to it either through this issue or new sub-issues.

acrosman avatar Oct 24 '21 15:10 acrosman