Mike,
The submitter mode Locked has everything to do with Licenses for my purposes!! The LICENSE aspect applies when you have an application like ours which is designed to operate with Read only licenses. When the submitter mode is LOCKED, my application (which tracks employees' skill sets) allows all the employees in the company to submit and MODIFY their own skill sets with only READ licenses... NO license charge for the vast majority of our employees who only enter and update their own skill sets. This whole email thread started because I want to move this app to a different server that is running with the submitter mode changeable. In order for the app to run (and not cost us big $$$ in extra licenses) I need to put the destination server in server mode locked. I don't want to mess up the existing applications on the destination server. If I lock the submitter and then the users hit workflow which would ordinarily be able to change the submitter field, there will be an uproar!! Too many forms and too little knowledge on my part of the existing apps caused me to request help. Now if I haven't' confused the heck out of everyone, I'd like to thank everyone for their help and ideas. Best regards, Leigh ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Mike White Sent: Wednesday, July 11, 2007 1: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___ 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. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
<<image001.gif>>
<<image002.gif>>
<<image003.gif>>
<<image004.gif>>
