Strange Behavior with Queries (2 Items)
Developers in our organization have recently reported two issues that had arisen with Queries.
1. A user was unable to edit/author a query in RTC web client using Firefox 3.6.10. The user reported that the query parameters were just unavailable. There existed no problem with editing/authoring the queries in the RTC client. I advised the user to install Google Chrome and try to discern if the problem was with the Browser or users account/permission. User was able to edit and author queries using Chrome. That would have led me to believe that the issue was with FF 3.6.10. However, after successfully editing the query with Chrome, the user was also able to edit in FF subsequently.
What would cause this? Server side caching? Please advise.
2. In another instance a team lead created sub-teams in order to share and categorize queries. There are no users in those sub teams. Most users had no problem accessing those queries, except for three team members. This lack of visibility was also evident in the web client. We were able to resolve the issue of visibility for the users by disconnecting and reconnecting to the project areas.
I have a few questions regarding this.
Should the team members in the parent team be able to see the queries shared with the subteam (a subteam with no users. It exists only to address a categorization requirement for shared queries)?
Or is it that the team members that could not initially see the queries of the (empty) subteam were actually experiencing the expected funnctionality?
I tried to find information regarding the rules of object permission inheritance but have found none that seem to apply to this instance. Is this documented somewhere?
Is there a better way to group and organize queries, both owned and shared?
Is this again some sort of server side caching?
Are these known issues?
I have concerns as both of these issues arose about the same time.
1. A user was unable to edit/author a query in RTC web client using Firefox 3.6.10. The user reported that the query parameters were just unavailable. There existed no problem with editing/authoring the queries in the RTC client. I advised the user to install Google Chrome and try to discern if the problem was with the Browser or users account/permission. User was able to edit and author queries using Chrome. That would have led me to believe that the issue was with FF 3.6.10. However, after successfully editing the query with Chrome, the user was also able to edit in FF subsequently.
What would cause this? Server side caching? Please advise.
2. In another instance a team lead created sub-teams in order to share and categorize queries. There are no users in those sub teams. Most users had no problem accessing those queries, except for three team members. This lack of visibility was also evident in the web client. We were able to resolve the issue of visibility for the users by disconnecting and reconnecting to the project areas.
I have a few questions regarding this.
Should the team members in the parent team be able to see the queries shared with the subteam (a subteam with no users. It exists only to address a categorization requirement for shared queries)?
Or is it that the team members that could not initially see the queries of the (empty) subteam were actually experiencing the expected funnctionality?
I tried to find information regarding the rules of object permission inheritance but have found none that seem to apply to this instance. Is this documented somewhere?
Is there a better way to group and organize queries, both owned and shared?
Is this again some sort of server side caching?
Are these known issues?
I have concerns as both of these issues arose about the same time.