duksta.org :: Blagh

Hide solved ArcSight support tickets with GreaseMonkey

Since I work for an MSSP managing ArcSight devices for our clients, I open a lot of support tickets with ArcSight. Their support website leaves much to be desired, especially the fact that you can't filter out closed tickets from your view of your support cases. The following GreaseMonkey script does just that.

// ==UserScript==
// @name           Hide ArcSight Solved Tickets
// @namespace      http://duksta.org/userscripts/hideArcSightSolvedTickets
// @include        https://arcsight.custhelp.com/
// ==/UserScript==

// Instructions: 
//
// Install GreaseMonkey - https://addons.mozilla.org/en-US/firefox/addon/748/
// Install this script
// Apply it to "https://arcsight.custhelp.com/cgi-bin/arcsight.cfg/php/enduser/myq_ilp.php*"
//


tdc = document.evaluate('./descendant::tr/td[5][contains(.,"Solved")]', document, null, 7, null);

for (I=0; I<tdc.snapshotLength; I++) {
    tdc.snapshotItem(I).parentNode.style.display = "none";
}

Posted by John on July 8, 2010

Firefox 3.6 - Opening new tabs where they should be

[Oops. Looks like I drafted this back in February and forgot to post it. Here it is now.]

If any of you have upgraded to Firefox 3.6, you may have noticed an annoying change to how new tabs get opened. Instead of opening as the rightmost tab in your tab bar, they get opened just to the right of the page you're on. If this new feature annoys the hell out of you like it does me you can restore the old behavior like this:

Enter 'about:config' in your location bar.
Accept the warning about possibly breaking stuff
Filter for 'browser.tabs.insertRelatedAfterCurrent'
Double click that entry to set it to 'false'

Done. Tab open where you've come to expect them to open, all the way on the right.

Posted by John on February 23, 2010

Nokia e71 Bug Report - Phonebook match fail

Dear Nokia:
I filed this report via the 'email support' page on your website. Hopefully you'll fix this. I can, of course, work around it with judicious data entry sanitization, but I shouldn't have to.

Bug Report: 
Phone book match fails for incoming calls and SMS 
messages if phone book entry contains dashes

Version Info:
300.21.012
18-06-2009
RM-346
Nokia E71-1 (27)

Details:
When a phone book phone number entry contains dashes 
(and possibly when it starts with a +), the calling (or texting) 
party name from the phone book is not matched properly. 
It seems that there's a regex failure.

Steps to reproduce:
Enter phone book entry in the form +1-NPA-NXX-NNNN. 
Receive call and text from that number. Observe that the 
entry is not matched properly.

Desired Behavior:
The lookup algorithm should strip out the dashes before 
matching to the phone book entries.

Other Notes:
This worked properly on my E61i. You might want to check 
that code tree to see what changed between releases.

Posted by John on September 5, 2009