Greetings, I'd suggest also looking for the text inside the box as well as Confirmation - that way you can differentiate between different Confirmation windows.
I concur on the below - I don't put in the cursor locations for these windows - they are based on what button is currently selected. Regards, Thom Thom C. Blackwell Product Manager Boston Software Systems (866) 653-5105 ex 807 www.bossoft.com <http://www.bossoft.com/> Sign up for my weekly webinar! <http://www.bostonworkstation.com/customer_center/special_events.aspx> LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your trash. From: [email protected] [mailto:[email protected]] Sent: Monday, May 03, 2010 3:51 PM To: Talk Subject: RE:[talkbws] Meditech behavior... What I have done on occasion was to look for the "Confirmation" part and not tell BWS where the cursor ought to be. Then when the length changes for whatever reason the cursor position does not hang things up. From: [email protected] [mailto:[email protected]] Sent: Monday, May 03, 2010 2:47 PM To: [email protected] Subject: [talkbws] Meditech behavior... I've got an odd behavior that I'm not certain where it comes from or how best to handle it....I have a script that works in the BAR module and just to save time let's just say there are a number of points (as with anything in Meditech) where a confirmation screen is presented (Answer Yes or No). When I originally built the screen these always had the condition settings of confirmat...@1,1&@3,1 ..... The following has happened a couple of times to me with this particular script....After a good deal of testing with no issues the script was put into production and was doing just fine....Then one night it failed and upon further investigation I noticed that BWS was now seeing these confirmation screens with a cursor location of @6,2 so while a little puzzled I went ahead and made the changes to the script and it worked fine....Then for whatever reason the BWS script started showing the original confirmation location so I changed it back and as with before it was fine for a while....Now I'm back to where it all started with the script failing because the confirmation is being listed as @6,2... Has anyone seen this and if so any idea what I need/can do? I know I can create additional rules to "see" the alternate location but I've never seen this before so I'm thinking there has to be more to it.. Thanks, Travis D. Hanson, Applications Analyst Anderson Hospital IS Department 6800 State Route 162 Maryville, IL 62062 phone-618.391.5862 fax-618.288.8985 pager-681.338.7698 email- [email protected] --- To post a message to this list, send mail to: [email protected] You are currently subscribed as: [email protected] Unsubscribe in the customer center on our website: http://www.bostonworkstation.com/customer_center/virtual_user_group_talk .aspx --- To post a message to this list, send mail to: [email protected] You are currently subscribed as: [email protected] Unsubscribe in the customer center on our website: http://www.bostonworkstation.com/customer_center/virtual_user_group_talk .aspx --- To post a message to this list, send mail to: [email protected] You are currently subscribed as: [email protected] Unsubscribe in the customer center on our website: http://www.bostonworkstation.com/customer_center/virtual_user_group_talk.aspx
