Jul 31 2019 06:29 PM
We are implementing a greenfield modern SharePoint structure using a hub and team sites. It seems to me that functions like content types, workflows and to some extent the term store are slowly being superseded. To what extent should we be using these “classic” options?
The challenge is that some users may expect, what appears to be, the more granular\customisable functionality of the classic.
Jul 31 2019 10:47 PM
SolutionAug 01 2019 12:27 AM
Aug 01 2019 02:31 PM
@Juan Carlos González Martín @Paul Pascha
Thanks for the advice - it does confirm my thinking. I'm not a SharePoint person so there is no exposure to the classic world other than what I've read on sites like SharePoint Maven etc but as I work through some of the "how to" on these sites from time to time the traditional seems to be in conflict with the new. For example: using the term-store to define meta-data for a documents approval status may not be the best option when a user can use MS Flow directly request sign-off and the status is automagically shown via the built-in sign-off status column. There are other similar examples I could give but I guess this about moving the power to the end user (who like me) isn't a SharePoint native. So I have one further question does (or will) the auto-magic extend to things like Search and so therefore we are best to leave these "as is" and let the magic do its thing?
Jul 31 2019 10:47 PM
Solution