Greetings,
I am assuming the error message is something that happened based on an
action the script took.

A script can't actually "ignore" such a thing because the error message
is where the screen is at that point- so the script needs to detect and
deal with the message, probably by closing the error message first. What
happens afterwards depends on the nature of the error- is it
"ignorable"- keep going with the record the script is typing? Or is it
fatal to the record.
Either way the basics of this are your script needs to be looking for
different possible screen conditions at this point in the workflow -
the good (where the screen goes if no error occurs) - and the bad- (the
errors).
And at this point in the workflow, the script needs to be continue
looking for the until it finds one or the other. If there are more
possible errors, it needs to be looking for those too. And the script
may want to look for a timeout condition as well - what should it do if
none of the above happen.

The Rules format does this for you so you would have Rules within a Step
that say:
...
Condition - Action that may cause error 
Condition if no error - Action X
Error Condition - Action Z

So to paraphrase add a Rule that could detect the error in the Step that
has the Rule that could cause the error.

Now the action performed by the error rule depends entirely on your
application \ situation. 

What I would suggest doing is to have BWS connected to your screen - and
cause the error manually. Then close it manually and pay close attention
to where the screen goes afterwards - is it in the same field as the
data that caused the error? Does it move to another field? If it's the
same field do you want to re-type in the same data you just did
(doubtful), or type in something else, or clear the field? If it is a
different field - is this a field you script can fill in?
 
If you are using Rules - keep in mind that a Step means all the Rules
inside it are "in play" that means when the script is in a Step- it is
looking to see if ANY of the Rules in the Step are true. That's really
handy for the error message detection as I described earlier- but also
means you have to pay close attention to where the script goes after the
error message is cleared. If it goes right back to the same field - then
the script would key the exact same data back in again, likely not what
you want(but it may be)! So you may want the Error Rule to Goto a
different Step that has Rules to do what is necessary to process the
error. 

Hope this helps!

Regards,
Thom

Thom C. Blackwell
Product Manager
Boston Software Systems
(866) 653-5105 ex 807
www.bossoft.com

Visit us at MUSE Internationl Booth 629

Sign up for my weekly webinar!

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.


-----Original Message-----
From: [email protected] [mailto:[email protected]] 
Sent: Tuesday, April 28, 2009 1:59 PM
To: Talk
Subject: [talkbws] Ignoring error message

How do I tell my script that, if a certain message pops up on the screen
while the script is running, ignore the message and continue processing
the current file. In other words, I do NOT want it to pass over the file
- I want it to continue processing the file despite the message.

Tom Krupa
CPAT
Patient Accounts Analyst
309.672.4810


NOTICE: This message is a PRIVATE communication. This e-mail may contain
confidential or proprietary information that may be considered legally
privileged. It is intended only for the named recipient(s). If an
addressing or transmission error has misdirected the e-mail, please
notify the author by replying to this message. If you are not the named
recipient, you are not authorized to use, disclose, distribute, copy,
print, or rely on this e-mail, and should immediately delete it from
your computer system.

Thank you for your assistance with this matter.

---
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

Reply via email to