You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run ph-cmd : Now verify that the sky-ph/atlas package has 3 document models, 3 editors, an analytics processor and an import script and Verify that the sky-ph/rwa-reporting package has 1 document model and an editor
Run ph connect and open up the browser window
Showcase that the drives are now available on the home screen
Showcase that the drives can be opened by clicking their icon
Showcase that the icon of the opened drive is highlighted in the new sidebar
Showcase that it's still possible to create local and remote drives
3) Navigate tot the reactor settings screen and view the installed packages
Click on the settings icon & go to the package manager screen.
Showcase that the same information seen in the command line is visible here
Showcase that the sky-ph/atlas package has 3 document models, editors & an analytics processor and an import script
Showcase that the sky-ph/rwa-reporting package has 1 document model and an editor
4) Install the Powerhouse Contributor Billing package through the UI
Enter "@powerhousedao/contributor-billing" as the package name and click install
Wait for the package manager list to update with the new package
Inspect the contents of this new Package with the invoice document model and editor
Confirm that it's now possible to create an invoice document in the drive(s)
4) Verify that Connect can deal with missing document models
Go back to the package manager and remove the contributor billing package
Go back to the drive where the new invoice document was created
Verify that Connect is now unable to open the document
Verify that Connect is showing the appropriate error message to the user
The text was updated successfully, but these errors were encountered:
CallmeT-ty
changed the title
DEMO Scenario: New Connect UI
DEMO Scenario: Connect UI Update
Jan 20, 2025
Original Demo Scenario
https://docs.google.com/spreadsheets/d/1sgDOm1Sorr14yCwQm6BNQI3YYkaY2h2KuEuAbNqgy7g/edit?gid=543136969#gid=543136969
Demo introduction Video Recording! https://drive.google.com/file/d/1rCsKtbB0I5Uc4QZfBq5pNJKpUvgTZ98u/view
1) Inspect the installed packages and their modules by running
ph list
Run ph-cmd : Now verify that the sky-ph/atlas package has 3 document models, 3 editors, an analytics processor and an import script and Verify that the sky-ph/rwa-reporting package has 1 document model and an editor
2) Open Up Connect & View the new home screen
Run ph connect and open up the browser window
Showcase that the drives are now available on the home screen
Showcase that the drives can be opened by clicking their icon
Showcase that the icon of the opened drive is highlighted in the new sidebar
Showcase that it's still possible to create local and remote drives
3) Navigate tot the reactor settings screen and view the installed packages
Click on the settings icon & go to the package manager screen.
Showcase that the same information seen in the command line is visible here
Showcase that the sky-ph/atlas package has 3 document models, editors & an analytics processor and an import script
Showcase that the sky-ph/rwa-reporting package has 1 document model and an editor
4) Install the Powerhouse Contributor Billing package through the UI
Enter "@powerhousedao/contributor-billing" as the package name and click install
Wait for the package manager list to update with the new package
Inspect the contents of this new Package with the invoice document model and editor
Confirm that it's now possible to create an invoice document in the drive(s)
4) Verify that Connect can deal with missing document models
Go back to the package manager and remove the contributor billing package
Go back to the drive where the new invoice document was created
Verify that Connect is now unable to open the document
Verify that Connect is showing the appropriate error message to the user
The text was updated successfully, but these errors were encountered: