EDA Success Hub Recipe - Githubissues

SFDO-Community-Sprints / Snowfakery-Recipe-Templates

Repo for all contributed Snowfakery recipes, maintained by Data Gen Toolkit team.

BSD 3-Clause "New" or "Revised" License

27 stars 8 forks source link

EDA Success Hub Recipe #32

Open acrosman opened 3 years ago

acrosman commented 3 years ago

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.

eehjunggnujhee commented 3 years ago

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.

@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

aaronwinters commented 3 years ago

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

acrosman commented 3 years ago

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.