This is, and always has been, how it works I believe. A write license is assigned when a query is performed because there is an assumption that the user may then modify the record returned and try to save it. If the license was not assigned until this point you would run the risk of not being able to get a license and being unable to save your changes.
Mark I work for BMC, I don't speak for them. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Conny Martin Sent: 25 March 2011 11:26 To: arslist@ARSLIST.ORG Subject: Floating users get a floating write token on read operations ** Hello All, I searched the list but found no answer. I have an issue where floating users are granted a write token on read operations. I verified this with driver to eliminate workflow that could trigger this behaviour. On the first GetListEntry the user is granted a write token, although this is not neccessary in my opinion. So every user who logs into the system only to check if there are tickets assigned to him is blocking a floating write token for at least one hour. Has anyone else experienced this behaviour? Kind Regards Conny _attend WWRUG11 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
