Here’s the use case: there’s an update on an R360 that needs to be specifically related to the R360 for the R CSM to easily see and historically look back on.
The C360 CSM also needs to be able to easily see and historically look back at this. This use case does not apply across the board, meaning the global setting to roll up R360 updates to the C360 is not ideal.
Instead, we would like the ability to select on the particular R360 update whether to push it to the C360 also.
More than ideal situation: Same thing backwards, with, of course, the ability to specifically select which R360 since that’s a 1:many relationship.
The workaround of just posting it twice is not a possibility due to the tracking of activity load then getting inflated, and also the confusion of where the commentary for internal discussion should live.