Vladimir, I believe this is a bug in the version of the ITSM suite that you are using in that a modification pushes the submitter field over to the SHR:Consolidated form. Turn on your filter and active link workflow logging (I believe it’s a filter) and find the workflow that is pushing the submitter on Modify. You can remove the Submitter push from the workflow and you will no longer receive this error.
Scott Parrish IT Prophets, LLC (770) 653-5203 www.itprophets.com From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Joe DeSouza Sent: Monday, August 02, 2010 5:24 PM To: arslist@ARSLIST.ORG Subject: Re: ARERR 371 ** Not through the application interface. Changing it any other way *MAY* violate license agreements.. Technically you could do it with a Direct SQL using the application interface, but I am not 100% sure if doing so you would be in violation of the license agreement. You would need to read that in full before trying it out.. I had tried it out once for fun - but not implemented it in production anywhere.. and it works.. Joe ________________________________ From: "Novikov, Vladimir A CTR US USA" <vladimir.a.novikov....@us.army.mil> To: arslist@ARSLIST.ORG Sent: Mon, August 2, 2010 3:08:38 PM Subject: ARERR 371 ** Hi, I’m getting the following error when trying to modify Requester Info on HD tickets. Does anyone know if there’s a way to get around it without changing submitter mode or creating custom fields to store requester info? We’re on ARS 6.3. ARERR [371] You cannot change the value of the Submitter field -- the "Submitter Mode" of the system is configured to be locked : SHR:ConsolidatedList : Submitter Thanks Vlad _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_
