Sorry, not parentheses.  I meant quotation marks.

 

Shirley Hammack

I.T.  Financial Analyst

Duncan Regional Hospital

580-251-8939

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Shirley Hammack
Sent: Friday, January 04, 2008 11:35 AM
To: [email protected]
Subject: RE: [Talk] MeditechNUI connections

 

Thom, I have a question about the "@_DIALOG:text".  Since the whole
thing is in parentheses what kind of stuff can be used where "text" is.
Can variable names be put there or only free text that would normally be
surrounded by quotation marks?

 

Shirley Hammack

I.T.  Financial Analyst

Duncan Regional Hospital

580-251-8939

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thom C. Blackwell
Sent: Friday, January 04, 2008 11:28 AM
To: [email protected]
Subject: RE: [Talk] MeditechNUI connections

 

Greetings,
Is all the text in the dialog "common" (not just the title?) If not,
you'd be able to change the Title condition to use something on another
row - not just Row 1 (the "actual" title") to differentiate between
different error messages. The AutoPause Title condition is really "text
on the screen" - it defaults to looking at Row 1 because that's where
Meditech (and many other systems) have their screen title.

A few things with NUI:

1.       Be sure you're not accidently (or on purpose) using: Connect
"", stMeditech - this will happily launch  and even script NUI  - BUT it
cannot see the dialog boxes. You MUST use the Meditech NUI Server  /
Connect "MeditechNUI", stStream to script NUI

2.       As for the NUI dialogs... - be sure to use "@_DIALOG:text" to
send the key directly to the dialog - no need to use a separate
connection - the dialogs are seen by the MeditechNUI Server and passed
to BWS via the Stream connection.  

3.       We've got a "direct" NUI connect that doesn't need the use of
@_DIALOG (although it is harmless for supporting existing scripts) - it
can also script Meditech 3.x as well...

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] On Behalf Of Lori Kent
Sent: Friday, January 04, 2008 11:29 AM
To: '[email protected]'
Subject: Re: [Talk] MeditechNUI connections

 

Those overly used dialog boxes in NUI cause me problems sometimes.  

 

I'm finding myself using many more steps than I needed in the 3.x
version of Meditech.  It's because all of the error messages have the
same conditions.  At least, that is what I have found.  So, I have to
check to for one condition, move to a step, then check another
condition, move to another step.   

 

I have complained to Meditech about their unnamed windows, and too many
dialog boxes.  

 

 

 

 

 

Lori S Kent, Database Analyst
Catawba Valley Medical Center
810 Fairgrove Church Road SE
Hickory, NC 28602

phone:  828.326.2024
  email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 

 

 

Catawba Valley Medical Center 

810 Fairgrove Church Rd 

Hickory NC 28602 

828-326-3000 

"This electronic message may contain information that is confidential
and/or legally privileged. It is intended only for the use of the
individual(s) and/or entity named as recipients in the message. Please
notify the sender immediately and delete the material from your computer
if you have received this message in error. Do not deliver, distribute,
or copy this message, and do not disclose its contents or take any
action as a result of the information it contains. Thank you." 



>>> "Bennett, Brian" <[EMAIL PROTECTED]> 01/04/2008 11:03 AM
>>>
If any one uses MeditechNUI are you having a problem where a rule
refuses to
acknowledge the condition?  I'm working on changing some of my VBA
scripts
to Rules based since it seems that Rules are so much more robust, but
the
rules advance so far and then act as if the screen condition is never
met
and will not execute the rule.  I'm using BWS 9.611 and Magic
workstation
4.20e.   Do I need to drop back a few magic versions?  I have the same
problem with the VB scripts, but using a Connect ("MeditechNUI"),
stStream
command after each function forces it to work.  

Thanks.

Brian Bennett
Affinity Health Systems
PBS\Clinic Billing
(920)628-9055
[EMAIL PROTECTED]


-- 
This message has been scanned for viruses and
dangerous content, and is
believed to be clean.


-- 
This message has been scanned for viruses and 
dangerous content by, and is 
believed to be clean. 

 


"CONFIDENTIALITY NOTICE: This e-mail and any files transmitted with it
are the property of DRH and/or its affiliates, are confidential, and are
intended solely for the use of the individual or entity to whom this
e-mail is addressed. If you are not one of the named recipient(s) or
otherwise have reason to believe that you have received this message in
error, please notify 580.251.8773 and delete this message immediately
from your computer. Any other use, retention, dissemination, forwarding,
printing, or copying of this e-mail is strictly prohibited."

 

"CONFIDENTIALITY NOTICE: This e-mail and any files transmitted with it are the 
property of DRH and/or its affiliates, are confidential, and are intended 
solely for the use of the individual or entity to whom this e-mail is 
addressed. If you are not one of the named recipient(s) or otherwise have 
reason to believe that you have received this message in error, please notify 
580.251.8773 and delete this message immediately from your computer. Any other 
use, retention, dissemination, forwarding, printing, or copying of this e-mail 
is strictly prohibited."

Reply via email to