RTC client already loaded
We have a strange issue in that using the RTC 403 client - a user loads a sandbox from his repo.
If he logs out and back in and tried to reload the sand sandbox, it comes back saying that it is already loaded from a different location. You can continue and override this but its the same sandbox/repo/user etc.....!!!
Is there something amis in this behavior ????
One answer
Why does the user try to reload the sandbox after relogging in if it is already loaded? The sandbox is still loaded even though the user logged out and logged back in again?
It seems that you were expecting the load wizard to recognize that, not only is the content already loaded, but it is already loaded where you are asking it to be loaded. Is that what you were expecting? Currrently, the load wizard only checks whether it is already loaded but doesn't go deeper than that.
Michael
Comments
The problem originated when the user reversed a changeset. The Pending Patches in his stream could not be applied/accepted as it would complain that the files were "not shareable" or something to that effect. The files were already loaded in is sandbox. Only on reloading his sandbox could the Pending Patch be applied. We have have some other events in that only a reload would resolve.
As a test we tried it a logout/in/reload to see if the behavior was the same.
When trying to "re-load" a sandbox the default msg stating "already loaded elsewhere" is pretty meaningless and confusing.... Loaded from where? If its the same workspace/sandbox one would assume the load wizard should know it's source.
>msg stating "already loaded elsewhere" is pretty meaningless and confusing.... Loaded from where?
its not FROM, the message is saying its already loaded HERE on this sandbox (in some other folder)