I was unable to find a recommendation of a suggested max number of Record Tags for a news post.
I have a primary concern of performance, as evaluating the visibility for the records must be done for each tag. Depending on how many posts are loaded when hitting News, the system could experience heavy load. I know it's an extreme example
I feel from a UX perspective 3 is about the most record tags you want, beyond that and the post gets cluttered.
Does anyone have any metrics or suggestions around the performance concern? For UX, have you found 3 to be about right, more, less?
Also, if there is a clear recommendation in the documentation, can you please point me to it?
Discussion posts and replies are publicly visible
I don't have any metrics to support this, but my method is to only provide one record tag in any news post. The way that I approach it from a usability perspective is to ask the question: What record provides the most relevant context? Generally, if you have designed your system well, that record will provide links to the other relevant records that are the "actors" in the context of the first record. For example, if the news post is about a new purchase request in an inventory system, the most relevant record would be the request record. From that record, the system could link to other records that indicate who made the request or what product was requested.
In the end, though, it is all about the use case and what makes the most sense for the business users. If the user finds the extra context in the news post to be relevant, then I would include the additional record links. This is just my perspective on the matter, I hope that helps!