If absolutely necessary to be done at client level, you could run an AL
table loop to validate data followed by the Modify All operation couldn't
you?
Joe
-----Original Message-----
From: Grooms, Frederick W
Sent: Tuesday, June 14, 2011 5:01 PM Newsgroups:
public.remedy.arsystem.general
To: [email protected]
Subject: Re: Data validation checks when user uses the Modify All option in
the client
Filters are the only way to go to validate data during Modify All. All Set
Fields used to pull in data (needed for validation) should also be in the
Filters.
Fred
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Anderson Debra (PRN)
Sent: Tuesday, June 14, 2011 3:52 PM
To: [email protected]
Subject: Data validation checks when user uses the Modify All option in the
client
**
Hi Everyone,
We're using ARS 7.0 all custom code system.
In the past I have pretty much not allowed user's to use the modify ALL
option however I have a new feature where there is a strong request to allow
this option.
Unfortunately I am having some challenges getting workflow that would do
data validation to work when more than one record is modified.
I believe filters are probably the only option to that is workable (instead
of active links) but even in this case some of my On Modify filters do not
see to catch data validation issues in all cases. Part of the workflow
involves setting some fields via queries to other forms to verify existing
data.
Does anyone have any suggested best practices for handling this type of
process?
Thanks
Debra
Debra Anderson
T 415.808.9118 | F 415.808.3535
600 Harrison St . San Francisco, CA . 94107
PRN | media where & when it matters
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
