**
I have a form with many fields. When a field is changed by a user other than the currently assigned user, a notification is sent to the currently assigned user.



When the reporting group sets the record as reportable, they set field A to 'yes'. This triggers the notification needlessly.



I can configure the run if statement such that modifications to field A do not qualify the notification, but...if the reporting group modifies several fields in addition to field A, the notification doesn't run. (The reporting group does more than mark requests as reportable!)



The low tech answer is to teach the reporting group to set the request as reportable as a self contained process.



What's the high tech answer?



Thanks,



Rick



4.5.2

Oracle 8i

Solaris
You may also control your subscription options, including UNSUBSCRIBE, at http://www.ARSLIST.org This posting was submitted via the Web interface

**
Richard,

What about using a dialog box to prompt them to mark the request as reportable? If reportable, select yes and set the field. If no, no action is taken. Would something like that work for you?

Neil Sullivan
WPAFB, OH
937-255-1953, ext 3533

-----Original Message-----
From: Phillips, Richard Mr Northrop Grumman 5 SIG CMD [mailto:Richard.Phillips@HQ.5SIGCMD.ARMY.MIL]
Sent: Thursday, December 26, 2002 12:05 PM
To: ARSLIST@ARSLIST.ORG
Subject: Suppressing notifications...


**
I have a form with many fields. When a field is changed by a user other than the currently assigned user, a notification is sent to the currently assigned user.



When the reporting group sets the record as reportable, they set field A to 'yes'. This triggers the notification needlessly.



I can configure the run if statement such that modifications to field A do not qualify the notification, but...if the reporting group modifies several fields in addition to field A, the notification doesn't run. (The reporting group does more than mark requests as reportable!)



The low tech answer is to teach the reporting group to set the request as reportable as a self contained process.



What's the high tech answer?



Thanks,



Rick



4.5.2

Oracle 8i

Solaris
You may also control your subscription options, including UNSUBSCRIBE, at http://www.ARSLIST.org This posting was submitted via the Web interface

You may also control your subscription options, including UNSUBSCRIBE, at http://www.ARSLIST.org This posting was submitted via the Web interface

**
Richard:

Use a qualification that will check all of the fields they can modify. Long process, but it works.

James Mckenzie

-----Original Message-----
From: Phillips, Richard Mr Northrop Grumman 5 SIG CMD [mailto:Richard.Phillips@HQ.5SIGCMD.ARMY.MIL]
Sent: Thursday, December 26, 2002 10:05 AM
To: ARSLIST@ARSLIST.ORG
Subject: Suppressing notifications...


**
I have a form with many fields. When a field is changed by a user other than the currently assigned user, a notification is sent to the currently assigned user.



When the reporting group sets the record as reportable, they set field A to 'yes'. This triggers the notification needlessly.



I can configure the run if statement such that modifications to field A do not qualify the notification, but...if the reporting group modifies several fields in addition to field A, the notification doesn't run. (The reporting group does more than mark requests as reportable!)



The low tech answer is to teach the reporting group to set the request as reportable as a self contained process.



What's the high tech answer?



Thanks,



Rick



4.5.2

Oracle 8i

Solaris
You may also control your subscription options, including UNSUBSCRIBE, at http://www.ARSLIST.org This posting was submitted via the Web interface

You may also control your subscription options, including UNSUBSCRIBE, at http://www.ARSLIST.org This posting was submitted via the Web interface