Andrey, Are you sure....
If the window is opened in Modify mode, yes, I would expect this to fire. But not if it is opened in New mode. Why would I expect it in Modify mode? Well, how did you get to modify mode? The window opened in query mode, put in the qualification, did a search, and then opened the details in Modify mode. So, you did transition through Query mode along the way toward the open. I would not expect it to fire for opening in new mode directly since it never transitions through Query mode. Firing on all those execute conditions is odd. Display is when the window is opened in Modify or Display mode (yes, there is a display mode which is a read only Modify mode). You want only the search window so this condition is a waste of effort. Window Open and Window Loaded both being set is redundant since the query window opens and does on open and then on loaded. So, only one of them is really needed -- and you can chose which you want based on whether you need data present or not and whether you are setting values whose value you want to have after the workflow. The real question is what are you trying to accomplish at the end of the day? Is it that when the window is opened in search mode and ready to go, you want something to occur? Well, an idea to consider is changing completely so something like.... On gain focus of the first field on the screen (where focus goes when the window is opened) and run if of $OPERATION$ = "QUERY" fire. You will likely find that there is no gain of focus in the sequence above where it cycles through the query window on the way to modify since the window never really gets instantiated. The challenge here is that it will occur again if you tab out of and then back into the field -- so you need to record you have done it once before to avoid repeating the action. What is it that you are doing that you need to happen if you open a search, type in the entry ID and say search that you do not if you have a window that opens directly to the screen on that entry ? Why is there a difference in the functionality using the two different yet equivalent searches? Also, if using the mid-tier, are you sure you have an updated cached copy of the definition? Sometimes you adjust the definition -- like creating without the run if and testing and then adding the run if. Well, it would still be running without the run if unless the cache interval had occurred during that time. Some things to think about, Doug Mueller -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Andrey Sent: Wednesday, May 12, 2010 8:13 AM To: [email protected] Subject: Re: fire AL when window open only in Search Mode All what I need - fire AL if window opened only on Search Mode Currently I have test AL with Execute On: Display, Window Open, Window Load Run If: $OPERATION$="QUERY" If Action: Message ("test") ... but this AL also triggered when a window opened in New or Modify Mode and I can not understand what is happening _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
