I'll keep the list posted on whether there is something that can be done to fix this, based on what BMC support finds out. I'll definitely push to create a defect if nothing can be done at present. This issue does hamper developer productivity.
-----Original Message----- From: Action Request System discussion list(ARSList) on behalf of LJ Longwing Sent: Thu 10/29/09 10:19 AM To: [email protected] Subject: [SPAM] Re: Developer Studio issue - auto grouping of qualification criteria Not that I condone the practice, but I understand how it's doing it...this goes back to the discussion regarding how to parse a qualification. The 'dev studio way' is how ARInside has always parsed the qualification. It takes the left and right operand and puts brackets around them, then it parses again, and puts brackets around left and right again, over and over till it hits the individual qualifications. it's significantly 'easier' from a programming standpoint to do that than it is to do it the way Admin tool used to do it....but I agree it makes it significantly harder to read. I would say we need to open defects against the DevStudio and get it fixed. _____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Guillaume Rheault Sent: Thursday, October 29, 2009 8:03 AM To: [email protected] Subject: Developer Studio issue - auto grouping of qualification criteria ** DevStudio is a great revolutionary tool compared to the good ol' Admin tool, but there is something that the Admin Tool is better at, by not doing it: the automatic grouping of qualification statements. Let me explain. When setting a qualification, whether for an active link , filter or table field qualification, or any qualification, DevStudio "over" groups the statements to the point where it is harder to see what it is. So for instance in the Admin tool, you can have this qualification: (('Field 1' != $NULL$) AND ('Field 2' != $NULL$) AND ('Field 3' != $NULL$) AND ('Field 4' != $NULL$)) OR ('Field 5' != $NULL$) In DevStudio, this becomes: (((('Field 1' != $NULL$) AND ('Field 2' != $NULL$)) AND ('Field 3' != $NULL$)) AND ('Field 4' != $NULL$)) OR ('Field 5' != $NULL$) Notice the extra brackets. This qualification is very simple, but as you can see it is more difficult to figure it out in DevStudio than the Admin tool because of the extra brackets. With complex qualifications, this becomes a real annoyance that really gets in the way of the developer, specially because the auto-grouping is done even before saving the active link, filter, table field, etc. This problem is magnified when dealing with the ITSM workflow, to the point that I find myself copying and pasting qualifications in Notepad to strip the extra brackets to be able to understand the qualification.... this is not good. This problem really needs to be fixed, or at least provide the end user with the option to turn this "feature" on or off. IMO, it should be off, so DevStudio behaves the same way As the Admin tool by default. So far it seems there is no option to turn this off, but if somebody knows a way, please let us know Guillaume _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
