Is there a way to show users their saved and shared module states for the modules that we include in our carbon page? Otherwise users create bookmarks and bypass the carbon page completely, then they miss announcements about updates and bug fixes that are posted on the carbon page, and they miss other updates.
When you copy a saved state URL while in Carbon, it should copy a link that includes the carbon Workspace.
There is no way to force a particular saved state to open in a chosen Carbon Workspace if that is what you are asking.
hi evanj,
thank you for your reply. yes, the URLs are great, except then no one uses our carbon landing page. and we post announcements and updates there.
so instead of having users jump to their URLs and miss the content posted on the carbon page, I would rather that they go to the carbon page and then navigate to their saved state urls from there.
it would be awesome if I could add a section to the carbon page that shows the users their saved module states so that they do not have to manage bookmarks in chrome, and so that they do not bypass the carbon page.
thanks,
Mike
You could possibly do something with the following:
- Workshop backed Carbon home page
- Configure saved states to save into a chosen folder, and disable the “Any compass location” option
- Resource list widget in Workshop configured to show the folder where saved states are saved
Although you may have the following issue. Saved states are just compass resources that respect normal folder permissions. So if saved into a public folder, everyone will have access to every saved state in that folder. Alternatively you could configure saved states to save into a user’s home folder, but then lack the ability to display this to users since the folder selection in the resource list widget is a static configuration.
I see we have some growing signal for the ability to make the resource list configuration dynamic so I will add this signal to our internal ticket. Specifically in your case you may wish to display a user’s home folder on the Carbon landing page, and it may also be helpful if you could configure the resource list widget to filter down and only show saved state resource types.
For now, you could consider creating your updates and announcements as Ontology data that is displayed in a Workshop embedded module that can be displayed from all relevant modules, possibly keeping track in your Ontology which users have seen which updates to be able to conditionally show new updates. A lower lift solution could be something like a banner that suggests checking out the home page for updates.