Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X
We are looking at the requirement of managing large number of Products (in hundreds).
The requirement is to change the team members assigned to different roles easily without having to edit the team in each product. The Shared teams provides this functionality.
I want to understand if there are any downsides of using shared teams across large number of projects.
For example - Performance issues, ACL related challenges etc.
Thanks.
Ravi
Solved! Go to Solution.
The top cons Ones you use a shared teams in a context , you can't roll back or change to another shared team.
for the performance refer to https://www.ptc.com/en/support/article/CS143292
The top cons Ones you use a shared teams in a context , you can't roll back or change to another shared team.
for the performance refer to https://www.ptc.com/en/support/article/CS143292
Very good information.
Thank you
Ravi
Hope to hear some more possible constraints or cons or Shared Teams.
Hello Fedel,
Thanks for the information and the cons mentioned by you about not being able to change to another team.
Additionally, the article (https://www.ptc.com/en/support/article/CS143292) shared by you mentions that it is not advisable to modify the Shared teams locally. Local modification will result in loss of performance when very large number of Product contexts are used.
I am still not able to decide whether we should use shared teams when our customer will be having large number of products (1000+)
Hi @RaviM,
It looks like you have some responses from some community members. If any of these replies helped you solve your question please mark the appropriate reply as the Accepted Solution.
Of course, if you have more to share on your issue, please let the Community know so other community members can continue to help you.
Thanks,
Community Moderation Team.
Hi,
I have accepted this as solution.