FYI, Option #2 would very likely be interpreted by BMC Legal as an attempt to circumvent the EULA, so I would not recommend doing it. I understand that the spirit of the idea is to address the issue with the Overview Console which will itself be addressed in a later version. However, the general suggestion outside of a specific issue would very likely lead to a breach of the license agreement.
-David J. Easter Manager of Product Management, AR System BSM & Atrium Solutions Management BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Misi Mladoniczky Sent: Friday, November 23, 2012 2:25 AM To: arslist@ARSLIST.ORG Subject: Re: When is a Floating Application License "Consumed" Hi, I have a couple of ideas... 1. The Overview Console that consumes licenses across all applications, if the user has a Floating license to these same applications. Suggestion: Make the forms searched customizable per user. The user can then hit a special "button" to show a list of tickets across All applications if needed. This would require BMC to change their Overview Console plugin... 2. Remove the Floating Application licenses from your users each night. When a user actually open the application form, you can have workflow that assigns the Floating Application license at that time. Would this be a breach of the license agreement? My initial thought on this would be NO, but I don't really know. Any comments? Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11): * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > Everyone, > > One more follow-up to my previous message that was explaining when > licenses are obtained to try and > address some questions that have come up. > > The model of licensing > > A user is assigned the potential for a particular type of license - Read, > Restricted Read, Floating Write or Fixed > Write. Each of these types of licenses have specific capabilities and > restrictions. > > When a user accesses the system WITHOUT accessing data, they will get a > Read license assigned to them > and their "potential" license is still potential because they have done > nothing on the system yet. > > When a user performs any data access within the scope of their license > (any form for AR System licenses and > forms licensed for the application for Application licenses), their > potential license is obtained for this session. > Now, if their potential license is a Read, Restricted Read, or Fixed > license, this is not really an event because > those types of licenses are ALWAYS available. If their potential license > is a Floating Write license, this act > of obtaining is significant because a token from a limited pool is > obtained. > > Yes, the license is obtained at ANY data access. That is because you have > started work and you are licensed > for that type of license so one is obtained for you so that you have no > restrictions working within that type > of license (otherwise you could for example fill out a bunch of data to > modify something and then be > refused at the "save" point because you could not obtain a token). > > The concept of no license needed for read is actually a rather unusual > one. Most products require that a > user have a license to be able to enter the application at all. For the > AR System and BMC applications, you > do not need a license to read or submit if that is all you are going to > do. Only if you are going to open and > change and save something created by someone else do you need a write > license. > > But, if you have a write license of some form, you will obtain that write > license whenever you do any data > access - including read - within the system. > > > Overview console > > I tried to be very clear in my previous message. It describes how > obtaining a license works within the system > and it details the specifics about what is happening. It describes the > issue with the Overview console and > why a license is obtained. This is true up through and including the > current shipping product (8.0 as of this > note). > > Now, I did call out that BMC has recognized that the fact that a broad > group of application licenses are > obtained on accessing the Overview console is not really what the broader > intention and an overall best > practice should be. So, this is acknowledgement that BMC understands the > issue that is being mentioned > and that there is attention being paid about whether this behavior is > appropriate. > > I also called out that the history has been that when BMC has uncovered a > situation where the obtaining of > licenses is not really what was intended or considered best practice that > there is a tendency to change the > behavior in future release so that the issue no longer occurs. I gave a > couple of examples of this that have > occurred in the past. This does not guarantee change; it just shows a > trend. > > > Home page and overview console > > As has been noted, these are really the same thing. The home page is just > a copy of the overview console > shown in a window on the home page. Same data, same tables being > accessed. > > So, any issues around obtaining licenses are the same. > > > Change Management license obtaining > > One question that comes up is how many people within the org really need > change management licenses? > > Approving changes does not require a change management license. > Working tasks does not require a change management license. > > People who work the change PROCESS need Change Management licenses. We > tend to find that in many > customer sites, there are many people assigned floating licenses for > change management who actually > never change a change request ticket itself. These users can work fine > with a read license to the > application (and you don't actually need to assign someone an application > read license to allow them to read > the data for the application). > > > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of Jason Miller > Sent: Wednesday, November 14, 2012 7:05 AM > To: arslist@ARSLIST.ORG > Subject: Re: When is a Floating Application License "Consumed" > > ** > > Hi Shawn, > > It has not changed for the Overview Console (yet). That is what we are > looking to address in this thread. > > One point of clarification, there is not a different Overview Console for > the Customizable Home Page. The CHP uses inline forms to display the > actual Overview Console. > > Either way were have been told by BMC staff that a license is only used > when saving (create/modify). Like Tony I am going to have to explain that > is not completely accurate (I've started but since mgmt is still in shock > from having to think about paying for CM licensing to cover ~300 people > because it was "free" when CM was homegrown, I get that shutup look each > time I mention this issue). > > Jason > > On Nov 14, 2012 6:18 AM, "Pierson, Shawn" > <shawn.pier...@sug.com<mailto:shawn.pier...@sug.com>> wrote: >> >> I want to jump in and ask a question on this specific to the example of >> the Overview Console, and the area I'm specifically most interested in >> is the customizable Home Page version of it, rather than the standalone >> Overview Console. You said, >> >> "As BMC has uncovered areas where licenses were being obtained where we >> did not think it was appropriate (see the previous two examples), >> changes have been made in later releases to make sure that adjustments >> were made to not grab license tokens earlier than was intended." >> >> Can you specify what version of ITSM the behavior was changed in to not >> grab licenses from the Overview Console? >> >> Thanks, >> >> Shawn Pierson >> Remedy Developer | Energy Transfer >> >> -----Original Message----- >> From: Action Request System discussion list(ARSList) >> [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of >> Mueller, Doug >> Sent: Tuesday, November 13, 2012 2:33 PM >> To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> >> Subject: Re: When is a Floating Application License "Consumed" >> >> Claire, >> >> Remember, you asked..... >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at >> www.arslist.org<http://www.arslist.org> >> attend wwrug12 www.wwrug12.com<http://www.wwrug12.com> ARSList: "Where >> the Answers Are" > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
