When i said lock out a session i mean the RDP session from too many failed logon attempts because the password is old because the user did not hit F5 to get the new RDM session credential updates.
We are using the MSSQL data source. I do have the force refresh before edit but that only refreshes for the person making the edits. All other users do not refresh their data sources until they hit F5. Basically it does a personal refresh and not a global refresh. Each individual on the team has to hit F5 to refresh.
I am looking for a way that when a RDM session edit is made it forces a F5 refresh for all the users not just the user making the edits.
If the above was difficult I was suggesting an option that could force data source refreshes in a certain interval. So that users are always getting any recent changes in their list.
We are using the MSSQL data source. I do have the force refresh before edit but that only refreshes for the person making the edits. All other users do not refresh their data sources until they hit F5. Basically it does a personal refresh and not a global refresh. Each individual on the team has to hit F5 to refresh.
I am looking for a way that when a RDM session edit is made it forces a F5 refresh for all the users not just the user making the edits.
If the above was difficult I was suggesting an option that could force data source refreshes in a certain interval. So that users are always getting any recent changes in their list.