Wow, I'm not sure what's up there, but I've never had to go through all that to test. Assuming this is a development environment you're working on, all I've had to do is make sure that Development Cache Mode is on (I always have it on in development), save my changes in the Admin tool, close any instances of the affected form in the User tool, and then reopen the form which loads the updated definitions including any affected active links. I've rarely ever had to remove all the ARV files, etc. I have never had to close the Admin tool, and I have never had to bounce the AR server after making the change.
Odd... Good luck, Lyle From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Lateralus Sent: Thursday, January 21, 2010 2:25 PM To: [email protected] Subject: Re: Work Info History not Locked? ** I think I might have this beat. I found I also had to modify: SHR:SHR:OnDisplay_050_SetActivityFields It also has a Set Fields action that switches the z1D_Secure_Log to "No". I have simply flipped it to "Yes" and I'm testing now. I'm also going to export all definitions for the HPD:Help Desk form and try to track down any other references to this field to try and understand anywhere else it's being manipulated. BTW - What methods do you use to do development/testing. I don't recall it being THIS painful (it's been awhile since I've worked with it). After each change I want to test, I have to: - Close Administrator - Ensure I have no active user sessions (close all User instances)\ - Delete everything from my local /Documents and Settings\<user>\Application Data\AR System\HOME folder - Punt the Remedy Server service on the (Windows) server. - Reopen User and Administrator tools to continue. If I DON'T do this... I get these strange "User does not have AR Write license" (or something like that...) when testing. Am I missing something here? Thanks again for all the excellent help! Scott. On Thu, Jan 21, 2010 at 1:37 PM, Charles Baldi <[email protected]<mailto:[email protected]>> wrote: ** Setting the ITSM WorkLog to default to "Locked" is notoriously difficult. There is OOB workflow that wants to force Locked to be "No" regardless of the user's choice. What we did to accomplish this is: 1. Set the default to the Locked field (z1D_Secure_Log) to "Yes" on HPD:Help Desk, or wherever. 2. Disable the OOB AL that wants to force them all to unlocked: SHR:SHR:NewLogNotEqualSecure_101 3. For good measure we added a filter to HPD:WorkLog (and others) that sets 'Secure Work Log' = "Yes" on Submit. We did this because there seemed to be some hard to pin down scenarios where just disabling the above AL did not seem to work. This may be overkill for you. This was with ARS 7.x and ITSM 7.0.3 various patches. Regards, Chuck Baldi On Thu, Jan 21, 2010 at 12:07 PM, Differ, Alfred W CTR NAVSEA, 210 <[email protected]<mailto:[email protected]>> wrote: If you have access to an Admin tool you can set the default value for the lock field. You might have to look at workflow that opens various forms in case they set values before submission, but start with the field default. If you feel comfortable doing a 'modify all' operation, you just have to track down the form holding your work info records and then query for the ones you want to lock. If you have a large number of tickets you might want to break up the effort into time slots with your query so you don't set loose a big update when people are working. Alfred Differ Sr. Remedy Developer NDTI / NSWC PHD, CODE 210 805-228-6555 [email protected]<mailto:[email protected]> -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Lateralus Sent: Thursday, January 21, 2010 6:08 To: [email protected]<mailto:[email protected]> Subject: Work Info History not Locked? ** Hi all, Long time listener, first time poster. I've somehow become the "accidental administrator" of our Remedy system despite my warnings. We have recently come under scruntiny as all of our Work Info Entries are "Unlocked" by default and can be edited/modified at any point in time. Is there some way I can enforce the "Locked" status for a Work Info entry? Bonus points if I'm able to retro-actively set this field to locked for all historical records as well. Cheers! Scott. ARServer 7.0.01 patch 002 _Platinum Sponsor: [email protected]<mailto:[email protected]> ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org<http://www.arslist.org/> Platinum Sponsor:[email protected]<mailto:sponsor%[email protected]> ARSlist: "Where the Answers Are" _Platinum Sponsor: [email protected]<mailto:[email protected]> ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
