I submitted a bug SW00250776 for this problem. That a user cannot use submitter mode locked to change the tickets they submitted without using a license because the server issues the license after login.
I think it's basically issueing the Floating(write) is issued at the time of an ARGetMenu API call Thanks, -Geoff -----Original Message----- >From: "Lucero, Michelle - IST contractor" <[EMAIL PROTECTED]> >Sent: Sep 27, 2006 5:38 PM >To: arslist@ARSLIST.ORG >Subject: Re: Read (floating) license > >Hi, Misi: > >Hope you're doing OK. > >Is the operative word here "should" instead of "NOT"? > >I just performed a very simple test on the SHR:ConsolidatedList form, by >opening it in submit mode. There is no active link workflow on this >form. There is a single filter that fires on Submit, Modify and Merge. >Wouldn't opening a form qualify as accessing the server? > >Bottom line, as soon as I logged in, my test account showed up as >Floating in both the Admin tool AND the User Log. I have performed no >actions other than placing the URL to the form in the browser, pressed >enter and logged in. > >To the other point that was made. I've also let the same form sit idle >for over 10 minutes. It is sitting idle as I type. It still displays >as Floating. It has not been released according to the User Log. If >accounts were released after sitting idle for 5 - 10 minutes (gosh I >wish; imagine the reduction in cost), there wouldn't be a Float License >Timeout minimum setting of one hour. > >Maybe we should get Criss Angel from Mind Freak (US TV Reference) to >figure this out for us. > >All that said, the behavior in your environment could be different. >Here's mine: > >Win2003/IIS/6.0/Mid-Tier 7.0 P1 >Win2003/SQL Server 2000/ARS 6.3 P11 >WinXP Pro/Admin Tool 6.3 Special Support patch 12 > >My two cents worth and minor test, >Michelle > >-----Original Message----- >From: Action Request System discussion list(ARSList) >[mailto:[EMAIL PROTECTED] On Behalf Of Misi Mladoniczky >Sent: Wednesday, September 27, 2006 3:52 PM >To: arslist@ARSLIST.ORG >Subject: Re: Read (floating) license > >Aaron, > >I have recently had some communication with Doug Mueller, and you are >almost right. > >Opening a form in Submit or Search mode should NOT grab a license, >unless >there is workflow that somehow contacts the server when the form is >opened. > >There is a difference concerning the user log file, where users does not >show up at all until they try to grab a licenses (i.e. by performing a >search, triggering workflow that does a set-fields, etc.). > > Best Regards - Misi, RRR AB, http://www.rrr.se > >> As always with licensing it's somewhat vague, but my experience has >been >> this: >> >> >> >> When a user with a Floating license assigned to them logs in, they >show >> up in the User License list as Read(floating) immediately. >> >> -If they sit there without doing anything, they disappear from the >User >> License list after a short time (5-10 min) >> >> -If they open a form (in ANY mode), they are then listed as Floating. >> >> -If they log out, they disappear from the User License (no matter how >> they were listed before) >> >> -If they are listed as floating and don't take any action for 1 hour, >> they revert to Read(floating), and shortly thereafter disappear from >the >> list. >> >> >> >> As far as floating license token allocation, I tested our system with >10 >> licenses, and found: >> >> -There could be more than 10 users marked as Read(floating) with no >> problems. >> >> -When users opened any form, in query or submit mode, they changed to >> Floating (and took a floating token) >> >> -Once there were 10 users marked Floating, then other users remained >> marked as Read(floating) when quering or submitting. >> >> -Users marked as Read(floating) could not Modify while there were 10 >> others marked Floating. >> >> -When someone logged out, the next Read(floating) user to perform an >> action (query, submit, or modify) was changed to Floating. >> >> >> >> >> >> -Aaron >> >> * Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >> >> ________________________________ >> >> From: Action Request System discussion list(ARSList) >> [mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) >> Sent: Monday, September 25, 2006 11:40 AM >> To: arslist@ARSLIST.ORG >> Subject: Read (floating) license >> >> >> >> Hi All, >> >> We're using ARServer 6.3, Patch 17. >> >> I'm using Manage User Licenses from the Admin Tool, with the following >> options: >> License Category: Server >> Category: Current Licenses >> License Type: Floating >> >> I was seeing the following: >> Floating - 10 users >> Read (floating) - 2 users >> >> Another user who is assigned a Floating license just logged in, and I >am >> now seeing >> Floating - 10 users >> Read (floating) - 3 users >> >> I've double-checked our server licensing, and we have 25 AR User >> Floating Licenses. >> >> I have the feeling I should know this, but it's a Monday, and I'm not >> seeing it in the help file or my Admin Guide. >> >> Does anyone know why 3 of the users are showing a "Read (floating)" >> instead of "Floating", when we should have 15 unused AR User Floating >> licenses remaining? >> >> Eric Cleereman >> >> __20060125_______________________This posting was submitted with HTML >in >> it___ >> >> >> SunCom is the wireless company that's committed to doing things >> differently. >> >> Things we want you to know. >> >> This e-mail and any files transmitted with it are confidential and are >> intended solely for the use of the individual or entity to whom they >are >> addressed. This communication may contain material protected by the >> attorney-client privilege. If you are not the intended recipient or >the >> person responsible for delivering the e-mail to the intended >recipient, be >> advised that you have received this e-mail in error and that any use, >> dissemination, forwarding, printing or copying of this e-mail is >strictly >> prohibited. >> >> >> >________________________________________________________________________ >_______ >> UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org >> > >________________________________________________________________________ >_______ >UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org > >_______________________________________________________________________________ >UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
