Version 4 File Structure for RelationshipManagers
A relationship manager includes a form and table method (among others). Should the components of the form and table stay within the RelationshipManager or is there a best practice to extract those to their own files?
Solution:Jump to solution
It depends. I really try to not "over engineer" something just because. If the
form and table are two not too large functions returning things with complex validations rules and so on, I prefer to keep this components inside the relation manager file. Otherwise, for example, if the table of the relation manager has custom actions, show/hide columns based on a complex logic, etc. I think that it's time to refactor and move to their own files
In addition, you can read about these topics on the Filamanet docs. It doesn't gives you an opinionated answer, it shows you an approach to the "problem" that you are experimenting:
1. Sharing a resource’s form and table with a relation manager....3 Replies
Solution
It depends. I really try to not "over engineer" something just because. If the
form and table are two not too large functions returning things with complex validations rules and so on, I prefer to keep this components inside the relation manager file. Otherwise, for example, if the table of the relation manager has custom actions, show/hide columns based on a complex logic, etc. I think that it's time to refactor and move to their own files
In addition, you can read about these topics on the Filamanet docs. It doesn't gives you an opinionated answer, it shows you an approach to the "problem" that you are experimenting:
1. Sharing a resource’s form and table with a relation manager.
2. Code quality tips. In the "Using component classes" section you will find an approach about how to handle this situation. As you may notices, is not opinionated. Is what it is. A code quality tips.
Hope it helps!Great answer @Oscar Carvajal , its up to you @nathan
Thank you for the answer!