Well, the submitter mode is tied to the license agreement. Here's how it works...or it least how I explain it to myself:
The default mode is submitter mode is changeable, meaning the value of the submitter field can be changed via workflow. In this mode, people with read licenses cannot update records submitted by themselves, because then it would be very easy to circumvent the write license enforcing code all together. That is, if a person with a read license can update a record if he's the submitter AND the submitter value can be changed with workflow, one could easily design a system whereby a user with a "free" read license could update ANY record by simply first changing the submitter value to the username of the person desiring to make the change. So to prevent this, if you set the submitter mode to LOCKED, a person with a read license can update a record HE created, but the submitter field is unchangeable...PERIOD. If submitter is changeable, the submitter field value can be changed via workflow, but people with read licenses cannot update records. In short, it's just a measure to help prevent people from skirting the license agreement. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Mike White Sent: Wednesday, July 11, 2007 12:24 PM To: [email protected] Subject: Re: Submitter Mode - Locked ...Brute force? Yup - this one got us stumped, too. Submitter Mode Locked simply means that the value entered in Field ID 2 for a record can't be changed after it's been created. Fred's response seems to indicate that there's some kind license or permission behavior difference relative to Submitter Mode setting, which I don't believe to be the case. That said, Submitter is a permission group, and changing the value of Submitter could reassign permissions from one person to another, but that's not the central point here. There was a subsequent thread that changing Submitter Mode and/or using Direct SQL to do so would violate the spirit of the license agreement. I don't understand what Submitter Mode has to do with licenses - it's simply a server setting that allows or disallows the value in a field to be changed. Mike White Office: 813-978-2192 E-mail: [EMAIL PROTECTED] "Shellman, David" <[EMAIL PROTECTED]> "Shellman, David" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 07/11/2007 12:46 Please respond to arslist To: [email protected] cc: Subject: Re: Submitter Mode - Locked ...Brute force? ** Fred, Norm and I have been having a side discussion. Each of us read your response differently. I get in trouble when I assume. Could you clarify your response for me? Thanks, Dave ________________________________ From: Action Request System discussion list(ARSList) [ mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W Sent: Wednesday, July 11, 2007 10:57 AM To: [email protected] Subject: Re: Submitter Mode - Locked ...Brute force? ** Once a record has been created Remedy will not let you change the Submitter (field ID 2) field. Submitter mode Locked means that even if the Submitter has a Read License they will be able to update the record (the non system fields of course) where they are the submitter not that they can change the Submitter field. Fred ________________________________ From: Action Request System discussion list(ARSList) [ mailto:[EMAIL PROTECTED] On Behalf Of Teale, Steven Sent: Wednesday, July 11, 2007 9:44 AM To: [email protected] Subject: Re: Submitter Mode - Locked ...Brute force? ** Leigh, There are some spreadsheets I have seen that will do some pretty clever analysis on workflow from def files. You could also run some sample logging and look for pushes to that field. Steven Teale AEGON Shared Services Louisville, Kentucky Phone: 502.560.2856 Mobile: 502.243.5619 Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Check Us Out ! www.aegonusa.com/AITSharedServices <http://www.aegonusa.com/AITSharedServices> < http://www.aegonusa.com/AITSharedServices <http://www.aegonusa.com/AITSharedServices> > ________________________________ From: Action Request System discussion list(ARSList) [ mailto:[EMAIL PROTECTED] On Behalf Of Leigh Gruber Sent: Wednesday, July 11, 2007 10:18 AM To: [email protected] Subject: Submitter Mode - Locked ...Brute force? 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 __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
<<image001.gif>>
<<image002.gif>>
<<image003.gif>>
<<image004.gif>>
