Hey @Zach Bacon - as requested, I'm cross-posting my Health Cloud/DX question from today's Office Hours call into the community. Look forward to working with you to investigate this one!
Do you know of any reasons why three Developer Edition scratch orgs with the Health Cloud package installed at the same time, and the same config steps taken to set up Health Cloud, would behave in three different ways?
Here is what I have observed across the three scratch orgs:
- Org 1) Worked perfectly from the start
- Org 2) No Health Cloud Visualforce pages were accessible even with the right permissions in place. This seemed to rectify itself after ~24 hours with no further changes made by me.
- Org 3) All Health Cloud Visualforce pages were accessible, apart from one, which would not load even with the right permissions in place. This seemed to rectify itself after ~24 hours with no further changes made by me.
I was wondering if there is some delayed process which needs to happen on the Salesforce side to 'activate' the permissions or the package or the org or something? Support have told me (via case #20957766) that this is not the case, so did you have any other thoughts about why this may be happening? It seems inconsistent and is therefore a bit of a mystery.
When I read a Developer Guider for Providers, When scrolling through, you have to scroll to the bottom to hit the next button. While I want to read the full pages for some pages, other pages I want to skip. Hoewver, you still have to skip to the bottom of the page, to click next. It is kind of annoying. Best practice would be to have the next and previous arrows at the both top and bottom instead of having to scroll. Thank you.
