Open kinjalagarwal1810 opened 4 months ago
We have intentionally decided not to implement another field to store the related profiles because it is not scalable. For example, if the employee has 100 related suppliers, there would be the 100 names listed in the field, which can be messy, hard to navigate and hard to pinpoint the profiles that the user wants to locate. Having unrelate and showrelated commands offer a far cleaner way when scaling up relations between contacts.
In addition, we have stated under planned enhancements in the DG that we plan to make the relate
and unrelate
command success message more friendly (under points 2 and 7). We were prevented from doing so due to the feature freeze, which includes making commands more user friendly.
Thanks!
Team chose [response.Rejected
]
Reason for disagreement: Yes, a UI might cut off the relations if there are too many, however did you consider other options like a separate section on your GUI. You can have your main page which is the format of ab3 and add a new right section where if you click on the person you can see all the relations they have on the right side as a list or graphical formats. This would improve the user friendliness of your function greatly.
I am not commenting on the success messages.
I understand you want to use this command to show who is related to one another. However, the UI does not show this relation anywhere which makes it very difficult to test/use/remember for the user. Perhaps you could add another field that shows the relations someone has so the only way to find the relations is not just with the command
showrelated
.