To extend on this, if you use a character field for the control field, you can run any number of commands using that one field (e.g., delete, archive, etc.), having different filters for each operation qualifying on that field. Makes sharing the workflow easy.
Axton Grams Heider, Stephen wrote: > > > Mike, > > This is done all the time ??? > > One way is to add a display only radio button field that includes one > option: "Delete". A filter on your form is used to perform the actual > delete with the Application-Delete-Entry command. The escalation will > set this field to "Delete" for all matching records. > > If you want to extend this concept add one more selection to the said > radio button called "Ready to Delete". One or more processes and/or > escalations would set this field to "Ready to Delete". Then an > escalation would run nightly (for example) that sets this field to > "Delete" for all records that have the field set to "Ready to Delete". > This way, you have some time during the day (if you want) to review > records that are flagged for deletion. > > To take this one step further, set the Field Id of the radio button > field to a number that you normally won't use (within the range of user > defined Id numbers). Then, you can simply copy this field to any other > form (keeping the same field Id) and update the one filter that will > handle any number of tables. > > > Stephen > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Michael LoSapio > Sent: Thursday, August 31, 2006 3:40 PM > To: [email protected] > Subject: Bulk remove users part II > > All, > > So, I read what a bunch of you had posted and spoke with Remedy Support. > The "BEST" thing I could come up with was an escalation to run on the > SHR:People with the Run If qualification being something like > 'Submitter'="Mike" then run process Application-Delete-Entry > "SHR:People" "Request ID" > > So, I was basically told me there was NO way to script the removal > process to run nightly without ANY actual manual intervention. ie: we > would need to change the RUN IF qualification manually in order to > remove entries in the form. > > Is this in fact correct?... there is no way to run a nightly process > which traverses through an imported list of "Submitters" and removes > them all from the system?? Is there a way to create a variable in the > escalation's RUN IF string... or can I execute it off a command line. > > > I was pretty shocked to hear this too, being new to the AR system and > reading all the documentation about how it is supposed to adapt to YOUR > business needs and not adapt your business needs to the system. > > > > Any input would be greatly appreciated. > > -Mike > > ________________________________________________________________________ > _______ > UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
