Yeah, except using rows/columns in C/S 5.6 is useless. It's all testing for prompts.
The problem I'm having is trying to do individual account discharge summaries out of PCS There is no "prompt" to test for in the screen, as the header is actually above where the account number is entered. Since the rows shift depending upon which machine is running the script, I can't use the normal testing for a specific row. I can do a test for "is the current row one greater than the row in which the account number was entered?" and if that condition is true send an F6 to go to the next section. Can't seem to get this stupid thing to recognize my condition. Thank you, Mitch Lawrence Lead Applications Analyst Enterprise Data Standards - NPR/Automation CHRISTUS Information Management *: [email protected] <mailto:[email protected]> ________________________________ From: [email protected] [mailto:[email protected]] Sent: Wednesday, March 17, 2010 11:26 AM To: [email protected] Subject: RE: [talkbws] Checking for "non rules" in a rules script Greetings, The issue here is that the Rules UI can only build Rule commands using static text it does not know how to build something that evaluates a property such as Row. I have an incomplete picture of what needs done - so the below may just be interesting but not helpful. There is a static value that "means" Row - the Row property returns the current row you are on, and in a condition- you can use 0 to indicate current row (can use 0 for a column to indicate current column. This works for the existence of text as well" t...@0,15 says the text is on the same row as the cursor and starts at column 15 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: Wednesday, March 17, 2010 11:44 AM To: Talk Subject: [talkbws] Checking for "non rules" in a rules script If I place the following statement in the Data box: F("Next Row") = Row and then right click a step and tell it to "Insert Rule with Condition..." >>> "When it is true that: F("Next Row") = Row" It inserts the following (with an action of Key "{F6}"): F("Next Row") = Row...Key "{F6}" However, the rule never actually fires. If I break the script run when I know that the condition is true and go to the immediate box I get the following: ? F("Next Row") = Row True ? Rule("F(""Next Row"") = Row") False So...What is the trick to get this working? Thank you, Mitch Lawrence Lead Applications Analyst Enterprise Data Standards - NPR/Automation CHRISTUS Information Management *: [email protected] <mailto:[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
<<image002.jpg>>
<<image001.jpg>>
