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
Export CSV files of the overall service-doc data for further manual processing. There should be a column for each field in the service-doc. Pay attention to lists and come up with a good concept of how to present them. Extension fields should also be supported.
The text was updated successfully, but these errors were encountered:
In our meeting, we have discussed that a mockup (or some kind of sketch or design suggestion) should be provided before actually implementing this feature. Simply so that we can discuss beforehand where the user will be able to find this particular feature. The sketch doesn't have to be high-fidelity - some drawing would probably suffice.
In our meeting, we had 2 ideas where to place this new feature:
Create a new page where such feaures can be found
Add a Hamburger menu button somewhere
I have a third option: When viewing the "Root Group" as shown in the screenshot below [1], you get a list of "cards" on the right. You could add a new card called "Actions" or the like. In this card, there would currently only be one button called "Export as CSV" or similar. Similar to our "Danger Zone" [2]. The interesting side effect of this implementation is: You can use the Filter to exclude some of the Service Docs. Thus, if you only want to export the Service Docs that, for instance, match "the name contains 'foo' and they have tag 'bar'", then you can do that easily with this. Also, in a future PR, we could add this feature to sub-groups or even on a per-service level.
But that is just another design suggestion. I am definitely open for other suggestions! 😃
Export CSV files of the overall
service-doc
data for further manual processing. There should be a column for each field in theservice-doc
. Pay attention to lists and come up with a good concept of how to present them. Extension fields should also be supported.The text was updated successfully, but these errors were encountered: