[nfbcs] JAWS scripting help requested for Remedy User client.

[Steve Jacobson]

There is a setting that you can put into the AR.INI file for Remedy that makes it a little more useable.  You add a section and a 
setting that looks like this:

[Accessibility]
AccessibleMode=2


A google search turned it up for me.  It was also in the Remedy Help, but the format was wrong there from what I could tell.  
There is also an option on the VIEW menu that causes a descriptive message about the current field with focus to be displayed on 
or above the Status Line.  I can't remember what it says, but the meaning is clear when you find it.  Unfortunately, I have not 
found a way to make the appearance of that information stay on by default.  Some fields work differently where you press ENTER on 
them to get a list of values and one just has to understand how some of these fields work.  

Maybe this will get you far enough to not need a script right away, or at least buy you some time.

Best regards,

Steve JacobsonS

On Fri, 10 May 2013 09:00:14 -0400, Tracy Carcione wrote:

>Hi Darrell.
>I don't have any hints, but, if you get something working, I'd sure like to 
>see what you've got.  I was able to use an old version of Remedy reasonably 
>well, but my company switched to the web-based client, and it's been 
>impossible.  I can find some things, and other things not at all. Luckily, 
>it's only a tiny part of my job, and I've been able to have someone else do 
>it for me when I need it.
>Tracy

>----- Original Message ----- 
>From: "Darrell Shandrow" <darrell.shandrow at gmail.com>
>To: <nfbcs at nfbnet.org>
>Sent: Thursday, May 09, 2013 7:02 PM
>Subject: [nfbcs] JAWS scripting help requested for Remedy User client.


>> Hello Everyone,
>>
>> I recently started a new job with a company that uses BMC's Remedy
>> User software, version 7.6.04, for processing technical support cases.
>> I have JAWS 14, which I am attempting to script to work with the
>> Windows client version of Remedy.
>>
>> When the Remedy application for this company was developed, custom
>> controls were used, thus making the mid-tier (web-based client) not an
>> option for my particular setup.
>>
>> When scripting JAWS, I am noticing a situation where the current
>> window, as defined by functions like GetCurrentWindow() seems to be
>> split into at least three separate areas. When I am in one of these
>> areas, I am unable to access information in other areas, even though
>> it is visible and I can locate it using the JAWS cursor.
>>
>> Most of my scripts rely on the FindString() function in conjunction
>> with GetCurrentWindow() to find information and read it, click
>> something or take some similar action.
>>
>> My primary purpose for scripting Remedy is to allow me to assign
>> keyboard commands to important fields, so I don't have to
>> inefficiently use tab or shift+tab to navigate the forms.
>>
>> Does anyone out here have any ideas how I can use FindString() in a
>> way that gets past this seemingly insurmountable screen boundary, or
>> any other scripting techniques I may be able to use to get the job
>> done?
>>
>> Thanks in advance for any help any of you can provide to point me in
>> the right direction.
>>
>> Regards,
>>
>> Darrell
>>
>> _______________________________________________
>> nfbcs mailing list
>> nfbcs at nfbnet.org
>> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>> To unsubscribe, change your list options or get your account info for 
>> nfbcs:
>> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/carcione%40access.net
>> 


>_______________________________________________
>nfbcs mailing list
>nfbcs at nfbnet.org
>http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>To unsubscribe, change your list options or get your account info for nfbcs:
>http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/steve.jacobson%40visi.com