"( Maybe a new thread should have been started, but why do we need more 
threads? )"

A higher thread count makes for more comfortable sheets so we can all 
sleep better.  :-)

Thad Esser
Remedy Developer
"Argue for your limitations, and sure enough, they're yours."-- Richard 
Bach



"Carey Matthew Black" <[EMAIL PROTECTED]> 
Sent by: "Action Request System discussion list(ARSList)" 
<[email protected]>
06/13/2007 10:14 AM
Please respond to
[email protected]


To
[email protected]
cc

Subject
Re: BMC Rant






I really hate to air "dirty laundry" ... but while we are all in rant 
mode...

I know this is just one "incident", but if all the ARSListers were to
list "just one" then I wonder how many we could list?

Note I did not pick this incident due to its relative importance in my
stack. Rather it is just the first _shocking thing_, and also the
first thing I found today.

I think there are also an few interesting implications to this
specific incident. So I think the merit of the content is important
and thus I post it. I just choose to add it to this thread due to the
applicability to the thread as well. ( Maybe a new thread should have
been started, but why do we need more threads? )


Maybe some of you have heard about this too? (This was news to me.)

**** History ****

I created an RFE (SW00254884) as:
"
improve Admin Tool "Related Workflow" tab display performance by
adding indexes to object_search_ref form after sync process.
"

Details:
"
This is an RFE idea...

Development Performance gains can be made by adding two indexes to the
object_search_ref from.
Specifically:
Index one:
  Target Identifier (Field ID 9001)
AND
Index two:
   Target Form (Field ID 9012)

If these indexes could be removed at the beginning of a resync and
re-establish at the end then that would be even better. (But adding
them in general would be a good thing IMHO.)
"

I just came across the "response" for this RFE. ( I do not think I
received it in email. And based on who it was addressed to I doubt
that I did see it.)

BMC RFE Response:
"
Hi lesquibe,

The "Related Workflow" tab was deprecated in 7.0 so this should no
longer be an issue. Replacement of this feature is being considered in
the future releases.

Please don't hesitate to contact us should you have further questions
on this RFE.

Thanks,
<Info_removed_to_protect_the_confused />
Product Manager
<Info_removed_to_protect_the_confused />@bmc.com
"


My Summary:

1) I have no idea who "lesquibe" is, but I know that is not a name
that I have ever used with Remedy/[EMAIL PROTECTED]@/BMC. ( Maybe a Level 1
Support person who did not inform me of the response from the "Product
Manager" ? )

2) Has anyone else been told that:

    a) "The "Related Workflow" tab was deprecated in 7.0"
OR
    b) That features will be removed (ok.. the feature is there but
they are not going to fix it and I have doubts about its accuracy in
v6.3 much less v7.) and "replacements" will be "considered" sometime
in the future?

3) I also should add that I have no access to know WHEN the
update/status happened on this RFE. All I appear to be able to see is
that the incident was "Resolved at" "11/29/2006 2:27:18 PM" with a
solution code of "Defect Submitted". So it was some time after that,
but when... who knows? And the RFE is status is currently "Resolved"
and classified as "As Designed".

-- 
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where 
the Answers Are"



***IMPORTANT NOTICE: This communication, including any attachment, contains 
information that may be confidential or privileged, and is intended solely for 
the entity or individual to whom it is addressed.  If you are not the intended 
recipient, you should delete this message and are hereby notified that any 
disclosure, copying, or distribution of this message is strictly prohibited.  
Nothing in this email, including any attachment, is intended to be a legally 
binding signature.***

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to