One thing that I have been happy to see in the past few months is more interaction from support in 'non official' channels...BMC has been responding directly to the list, on communities, etc...in general, as you guys said....more responsive...very nice to see.
On Thu, Sep 12, 2013 at 12:40 PM, Jason Miller <jason.mil...@gmail.com>wrote: > ** > Absolutely! I have seen a very noticeable effort by Support to be > proactive in providing information to customers so they can address issues > on their own and being more interactive with customers. I too have been > very pleasantly surprised to find relevant KB articles and attached > hotfixes in recent months. > > > On Thu, Sep 12, 2013 at 11:30 AM, Pierson, Shawn < > shawn.pier...@energytransfer.com> wrote: > >> ** >> >> For another issue, I had an issue with 7.6.4 earlier this week where >> Escalations wouldn’t run against a View Form. When I searched the BMC >> Support knowledge base, the first result was useful, concise, and had an >> attached hotfix for the issue. I’m not saying that this is the result of >> privatization or anything like that, but lately they have been more >> responsive than they have been in several years and I think they deserve >> some credit for that.**** >> >> ** ** >> >> Thanks,**** >> >> * * >> >> *Shawn Pierson * >> >> Remedy Developer | Energy Transfer**** >> >> ** ** >> >> *From:* Action Request System discussion list(ARSList) [mailto: >> arslist@ARSLIST.ORG] *On Behalf Of *Jason Miller >> *Sent:* Thursday, September 12, 2013 1:07 PM >> >> *To:* arslist@ARSLIST.ORG >> *Subject:* Re: Annoying Developer Studio Bug**** >> >> ** ** >> >> ** **** >> >> Look at that. BMC is now private and we are seeing issues since the >> first release of Dev Studio being fixed. It is like magic. Wait, it isn't >> Friday yet?**** >> >> ** ** >> >> On Wed, Sep 11, 2013 at 11:47 PM, Kumar, Amit (Remedy-Dev Studio R&D) < >> amit_ku...@bmc.com> wrote:**** >> >> ** **** >> >> This defect (SW00458142 ) is fixed. This will be available in the next >> patch of Remedy Developer Studio.**** >> >> **** >> >> Regards,**** >> >> Amit Kumar**** >> >> **** >> >> *From:* Kumar, Amit (Remedy-Dev Studio R&D) >> [mailto:amit_ku...@bmc.com<amit_ku...@bmc.com>] >> >> *Sent:* Sunday, September 01, 2013 9:08 PM >> *Subject:* Re: Annoying Developer Studio Bug**** >> >> **** >> >> ** **** >> >> We will look into and get back on this. I can understand the annoyance.** >> ** >> >> **** >> >> Regards,**** >> >> Amit Kumar**** >> >> **** >> >> *From:* Action Request System discussion list(ARSList) [ >> mailto:arslist@ARSLIST.ORG <arslist@ARSLIST.ORG>] *On Behalf Of *Longwing, >> Lj >> *Sent:* 02 September 2013 07:05 >> *To:* arslist@ARSLIST.ORG >> *Subject:* Re: Annoying Developer Studio Bug**** >> >> **** >> >> ** Sorry Ray, all I can do is join in with you on the annoyance, if you >> log a bug or communities idea on this, let me know and I'll vote for it out >> John into the chorus >> >> On Sunday, September 1, 2013, Ray Gellenbeck <raygellenb...@yahoo.com> >> wrote: >> > I have a big pet peeve that was not corrected in 8.1 of Dev Studio. >> > >> > Situation: >> > 1. Building an Active Link >> > 2. Add a "Set Fields" action >> > 3. Begin building your list of fields to set (for example, initialize >> a display-only form after a previous record finished processing) >> > >> > Annoying Bug: >> > 4. Once the list gets longer than the field list window can display, >> the scroll bar kicks in, as expected, but everytime you select a field or >> the field value, the view keeps resetting to the top of the list. So for >> each subsequent field you want to set the value for, you must... >> > a. Click the next blank field line, after which the view resets to the >> top of the field list >> > b. Scroll back down and click the ... so you can actually select the >> field to be set., after which the view resets again >> > c. Scroll back down AGAIN and select the value to be put in that >> field. When you go to click the next line down, the whole annoying process >> repeats again. >> > >> > If there a developer studio flag or workaround to tell the stupid UI to >> quit resetting to the top of the list. If I have a LONG list of fields to >> set, this is pretty darn time-costly with all the clicking and scrolling >> back and forth. >> > >> > I suspect there is not, so thanks in advance for anyone who can prove >> me wrong! >> > >> > Ray Gellenbeck >> > >> > >> _______________________________________________________________________________ >> > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> > "Where the Answers Are, and have been for 20 years" >> > _ARSlist: "Where the Answers Are" and have been for 20 years_ **** >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ **** >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ **** >> >> ** ** >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ **** >> Private and confidential as detailed >> here<http://www.energytransfer.com/mail_disclaimer.aspx>. >> If you cannot access hyperlink, please e-mail sender. >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
