Hello everyone,
Just an FYI.
'TR.Submitter' != $NULL$ would not work if you want to track the following
scenario:-
1. 'Submitter' field has a value in it and user erased the value in it and
saved it. In that case 'TR.Submitter' would be NULL even though a change
occured on that field.
I would suggest to use , 'Submitter'!='DB.Submitter'. This would track all
records.
Thanks
Chintan.
Leigh Gruber <[EMAIL PROTECTED]> wrote:
** v\:* {behavior:url(#default#VML);} o\:*
{behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape
{behavior:url(#default#VML);} st1\:*{behavior:url(#default#ieooui) }
John,
THANK YOU so much. With all the great ideas presented, this one will require
only a minimum of my time and is just the sort of solution I was hoping to
find. As a side bar, I will make a second filter to ensure that every form is
at least touched during that week.
To EVERYONE who helped contributed to this thread, THANKS for all your help,
Leigh
---------------------------------
From: Action Request System discussion list(ARSList) [mailto:[EMAIL
PROTECTED] On Behalf Of John Sundberg
Sent: Wednesday, July 11, 2007 10:59 PM
To: arslist@ARSLIST.ORG
Subject: Re: Submitter Mode - Locked ...Brute force?
** (off the top of my head - so some details are missing - but you should get
the point)
A technique to find if you can take advantage of submitter mode locked:
Create a new table called "SubmitterChangeTracker"
create a filter if 'TR.Submitter' != $NULL$ -- push a record to
SubmitterChangeTracker with schemaname, recordnumber, etc....
Put that filter on Modify -- for all your schemas....
Then let it run for a week -- if you find records in SubmitterChangeTracker --
you will be able to track it down.
etc...
-John
On 7/11/07, Leigh Gruber <[EMAIL PROTECTED]> wrote:
**
Good Morning Listers,
We have an existing system operating with the Submitter Mode set to
Changeable. This system has around 750 forms with a mix of Remedy and home
grown applications. We need to change submitter mode to Locked so we can host
another custom application which must run in Submitter Mode Locked.
I have 3 questions!
1. Is there any way, other than ones that require "brute force", to determine
if the original system has workflow that modifies the submitter field? I have
set the development box to Submitter Mode locked and tried some very limited
record modification, but I don't have any testing resources available.
Here's what I've tried so far on our dev system (Remedy 6.3; MS SQL Server):
Analyzed Advanced search results on the object_search_details form. The
selection criteria was ('Item Details' LIKE "%Submitter%") AND NOT('Item
Details' LIKE "%1 = 0%"). I haven't seen a problem in resulting (100 or so)
records.
I've also checked the Submitter field #2 for other names it may have.
2. Are there any "gotchas" I should know about that might cause us problems
if/when I change the production system?
3. Is it safe to assume that our Remedy/BMC applications will NOT have
workflow that writes to the Submitter form?
I would appreciate any words of wisdom you might have for me.
Many thanks,
Leigh Gruber
The information contained in this message may be privileged and/or
confidential. If you are not the intended recipient, or responsible for
delivering this message to the intended recipient, any review, forwarding,
dissemination, distribution or copying of this communication or any
attachment(s) is strictly prohibited. If you have received this message in
error, please so notify the sender immediately, and delete it and all
attachments from your computer and network.
__20060125_______________________This posting was submitted with HTML in
it___
--
John David Sundberg
235 East 6th Street, Suite 400B
St. Paul, MN 55101
(651) 556-0930-work
(651) 247-6766-cell
(651) 695-8577-fax
[EMAIL PROTECTED] __20060125_______________________This posting was submitted
with HTML in it___
__20060125_______________________This posting was submitted with HTML in it___
---------------------------------
Yahoo! oneSearch: Finally, mobile search that gives answers, not web links.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
