So... when an "Error" should be thrown from a filter you plan on doing:
For a Submit: a Push to create the "message" record a Run Process to do a "Application-Delete-Entry" a "goto 1000" action? For a Modify: a Push to create the "message" record a Set field action (by matching ID's) to retrieve all of the DB values for the record a "goto 1000" action? Or just use a Remedy Error Message for that case and tell the users to "get over" seeing the Error number? :) Or how else will you keep the save/modify from happening to the data? Also be mindful of how to deal with phase 2 push actions too. After all they need to be "turned off" or "backed out" too. To bad there is not a way to tell the ARS server to "forget about it" without throwing an fatal error. (Something like ... "Application-Forget-Pending" :) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. Never ascribe to malice, that which can be explained by incompetence. On 8/16/06, Heider, Stephen <[EMAIL PROTECTED]> wrote:
ARS 7.0. In the next version (complete rewrite) of our custom help desk system I plan to somehow implement a better way to display messages from filters. In active links I have a small display only dialog that I use to display messages to the user. As far as I am aware there is no built-in way to capture the text from the messages and display it to the user in a better looking window like most applications. One of the requests I receive from users is to hide the Remedy error number in messages. It means nothing to them and I rarely need it to troubleshoot. To keep the error number from displaying I do what many developers do and add 4 or 5 returns after the text to push the error number down so users can't see it. This works fine except when there are multiple messages, for example when two people or groups were notified. In this case filters would run two Message commands, yet the user only sees the first message because the second message is about 5 or 6 lines below and not visible. Here is what I am planning on implementing. If anyone knows of a better approach please let me know. Create a regular form to hold filter messages. One record per message. Replace all Message commands in filters to Push a record to the new messages form (with some unique ID to link it to the user session). When the user clicks the Save button (for example) the active link would Push the updates to the ticket form as usual. The very next command in the active link would query the messages form for any records. If found, then another active link would Open Window Dialog to display the message(s). For good housekeeping, the same active link that ran the Open Window would then delete the records (or set status to Archive if you, the Administrator, wanted to review messages at a later date). Regarding performance, since 99% of the time there are no filter messages generated when users add/update tickets, the only "cost" would be one extra query performed after each Push to the ticket table. In our environment this would equate to a fraction of a second. Stephen _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
