Himanshu, I think I see what one pitfall might be here that has not been discussed.
The user has a preference that will effect some of this logic too. They can decide that a Submit (CREATE) screen need to set default values, or not set default values. They can even have custom default values in the User Tool. Which means that your statements of: " No everything is on the Help Desk form and we have 'HD' as a Prefix to our Case ID's so the default parameter for the two different scenario's become Create Screen / When a User will Press F2 ===> Operation = CREATE , Case ID+ = HD and Status = New " Is only partially true. It might be true if the users preference are set to "On New --> Set to Defaults". However, if the user has their preference set to "On New --> Clear all fields" then the prefix for the Case ID field is not in the field! And beyond that I think there is an easier way to do what I think your after anyway... So... let us get to the real heart of what I think your trying to do. What you said was: " 1) On Query when he has no Case Id selected or searched (i.e. Case ID = Null ) 2) On Create when his Case ID has a default value ( Case ID = HD) " But I think what you mean is... There are some specific conditions that I want the user to be able to run the If actions of an active link attached to a button. If those conditions are not met then I want to throw an error back to the user. I think the root POSITIVE test condition for when you want the If actions to be run are the following: 1) The user is looking at a data record that has been committed to the database already. (Are there any other requirements that should be met?) If the above is all then I would think the Run If needs to be this: ($OPERATION$ = "SET") If you also want the If actions to fire from a "CREATE" window or a "QUERY" window then we should define what should be TRUE for those conditions too. But I have the impression that you really only want the error for the CREATE and QUERY operations. Does that help? What I am unsure of, at this point is that you seam to indicated that the active link has an Execute on conditions of : "Button ... and runs for both CREATE & QUERY operations" Do you mean that the ACTL fires on Submit, Search and Button? (Three "Execute On:" conditions?) It might be that your trying to do to much with a single active link. [ Or I am still a bit confused about all of what your trying to accomplish is also a real possibility. ] Since you have two active links that "work correctly" maybe you can post the details of the two active links and we can talk through how they might be combined? Maybe supply details like the following for each active link. Active link name: ? Execution order: ? Execute on condition(s): ? If button, interval, or other fields are referenced then also list them too. Run If: ? If actions: Action 0 : Window Open ? Else actions: Action 0 : Message --> Error "You can not do that" -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 9/14/06, Kohli, Himanshu <[EMAIL PROTECTED]> wrote:
No James Even the one ($OPERATION$ = "QUERY" AND 'Case ID+' = $NULL$ ) OR ($OPERATION$ = "CREATE" AND 'Case ID+' = "HD") you mentioned has failed to get my desired error msg which was defined in Else If tab as it goes into the If tab and opens up my Window. No everything is on the Help Desk form and we have 'HD' as a Prefix to our Case ID's so the default parameter for the two different scenario's become :- Create Screen / When a User will Press F2 ===> Operation = CREATE , Case ID+ = HD and Status = New Search Screen / When a User will Press F3 ===> Operation = QUERY , Case ID+ = Null and Status = Null now I just want both of these two conditions to be checked in a single ACTL .... even though I have managed to do the needful with two ACTL's with a different Logic but now this has become a Puzzle to be sorted out as well... So just give me a Run If condition which will make my Else tab in action and not If tab into Action..... Thanks for trying to help me Thanks & Regards Himanshu Kohli Remedy Developer / Administrator
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kohli, Himanshu Sent: Thursday, September 14, 2006 1:11 PM To: [email protected] Subject: Re: Two different Condition 's in Run If James It so simple but making me really crazy about it ... ok let me try to explain you briefly I want to block a user action on a Button Click to open a new Window and to include both the condition's in a single ACTL's Run If 1) On Query when he has no Case Id selected or searched (i.e. Case ID = Null ) 2) On Create when his Case ID has a default value ( Case ID = HD) Now I am trying that Run If ==> ('Case ID' != $NULL$) OR ('Case ID' != "HD") If Action ==> Open the Window Else If ==> Error Msg Result : If I use only one of each condition in the Run If ..it works as desired but fails when I try to use both with "OR" I beleive its somthing to relate with the execution of an ACTL at two different Operation's CREATE & QUERY on Help Desk form. I am having ARS 6.3 , Windows 2k with MS SQL 2K I hope you will be able to pull me out of this ... Thanks & Regards Himanshu Kohli Remedy Developer / Administrator PS : It looks so simple but has made me sound like ....
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kohli, Himanshu Sent: Thursday, September 14, 2006 12:06 PM To: [email protected] Subject: Re: Two different Condition 's in Run If ** Eric No even this is not working ... Frederick My ACTL executes on a Button on Help Desk form and runs for both CREATE & QUERY operations but only Status field is a Required Field so idealy this should not make my Run If condition fail.. Once again If I am using just one of the condition without using 'OR' all works as desired... plz help me to get out of this puzzel... List : plz excuse me for not using a new subject in my initial post ..... that was a mistake :( Thanks & Regards Himanshu Kohli Remedy Developer / Administrator ________________________________ From: Eric Roys [mailto:[EMAIL PROTECTED] Sent: Thu 9/14/2006 11:21 AM To: Kohli, Himanshu Subject: RE: Mid-Tier 7.0 Installation Problem Try: (( 'Status' != "New") AND ('Case ID+' != "HD" )) OR (('Status' != $NULL$) AND ('Case ID+' != $NULL$)) The additional parenthesis are needed to distinguish one OR from the other. Eric Roys Sr. Software Engineer Verizon Business Email: [EMAIL PROTECTED] CONFIDENTIALITY: The information contained in this message and any attachment may be proprietary, confidential, and privileged or subject to the work product doctrine and thus protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to this message and deleting it and all copies and backups thereof. Thank you. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kohli, Himanshu Sent: Thursday, September 14, 2006 10:15 AM To: [email protected] Subject: Re: Mid-Tier 7.0 Installation Problem Hey List I know its going to be very simple but now since I have tried all my combination (i.e. using braces ) I would like to seek your help. I want my ACTL to execute its 'Else Action' for the below mentioned 'Run If ' condition ( 'Status' != "New" AND 'Case ID+' != "HD" ) OR ('Status' != $NULL$ AND 'Case ID+' != $NULL$) every things works as desired when I use just one of them but with an OR when try to have both the condition in my Run If ... I fail Note : I do not want to make use of any other parameter other than the Status & 'Case ID Thanks for your quick help Himanshu Kohli Remedy Developer / Administrator __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org <http://www.wwrug.org/> __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
