I believe the Run Process even works if you do not have a preference server set. It doesn't save the value to the INI but it does take effect since it updates the in memory cache.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Mueller, Doug Sent: Thursday, April 29, 2010 2:50 PM To: [email protected] Subject: Re: Delete Option (Solved) Well, the user preference record is read at login and used throughout. If the user opens and changes the user preference record, the client knows it it and updates the in memory copy of the user's preferences. So, they take affect immediately. If workflow pushes to the user preference record, it is never opened in the client so the values are changed in the record but not updated in the client memory (yes, even if by an active link, a push doesn't actually open the form and no client logic runs on the operation). So, they take affect at the next login operation (or restart). If the run process command is used, this updates the user preference record using the equivalent of a push AND updates the in memory copy of the user's preferenes. So, it does the equivalent programatically as opening the user preference form and changing it on the client -- it does the client side work of updating the cached preferences for the current user and the server work of updating the definition for the next time. I hope this helps explain things. Doug Mueller -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of josepht Sent: Thursday, April 29, 2010 12:40 PM To: [email protected] Subject: Re: Delete Option (Solved) Thanks for the help. PERFORM-ACTION-SET-PREFERENCE did the trick not sure why set fields didn't seem to go into effect until the user logged out and then back in. Well it worked at least for most of the users. After setting Use This Server in the Preference Server option it worked for all users. Mueller, Doug wrote: > > One way you can make sure that people don't open the wrong VUI is.... > > Put in an active link that runs On Open that has a run if like > > $VUI$ = "special name" AND NOT $GROUPIDS$ LIKE "%;1;%" > > The action could be an error message saying "you are not allowed to open > this > view" and then a close window. It could be something else -- you decide. > It > should be able to change the user preference directly and have it take > affect > immediately (well, for the next window open, not for the window open in > process > but it is not waiting to the next login). I think it is a special run > process > command that allows you to do this and it should work regardless of > whether you > are using centralized user preferences or local user preferences. OK, I > broke > down an looked at the doc and the command you want is > PERFORM-ACTION-SET-PREFERENCE. Take a look at the documentation about the > special run process commands and you will find it. > > The key is that this active link would prevent anyone but the admin from > opening > this VUI. Also, there is a way to control user preferences with the > affect > being immediate and not next login (again, immediate for all operations > AFTER > the setting not altering something that is in the middle of operation). > > This is a general way you can control opening windows and a way to control > user > preferences from workflow. > > I hope this helps, > > Doug Mueller > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of josepht > Sent: Wednesday, April 28, 2010 3:14 PM > To: [email protected] > Subject: Re: Delete Option (Solved) > > I used this method to lock down both Modify All and Delete permissions on > all > of our current forms. But I wanted the administrator to still have access > to > these options so I created a view with them enabled. > > Now the only problem is the Default Form View field available on the > Advanced tab of the User Options under Tools. If a user knew the name of > the > Admistrator view, they could enter it into that field, and then open that > view for all the forms that they can reach from the object list and using > any workflow that does not specify a specific view. Granted for regular > Users this will only grant Modify All permissions and they would need to > know the exact name of the view for all forms, but this is still a > loophole > that could be exploited. > > Is there any way to disable this field in the menu or to deny permissions > to > certain views? I have gone into the actual User Preference form and > disabled > that field, but it still works in the menu item. The closest i could get > to > blocking it was an active link that set the default view to null if the > user > is not an administrator, but this does not seem to apply to the user until > the next time they log in. But durring the session that they specify a > default view the name they entered remains in use. I can not get this to > overwrite their entry while they are in the options pop-up which would be > the ideal place to do it. > > Gary Roach wrote: >> >> This works great. Thank you all for your responses. >> >> Thank you, >> >> Gary Roach >> Project Services Analyst >> [email protected] >> T 724.539.1510 >> F 724.539.5797 >> >> Kennametal Inc. | 1600 Technology Way | Latrobe, PA 15650 | >> www.kennametal.com >> >> >> Rohini Prasher <rohi...@...> >> Sent by: "Action Request System discussion list(ARSList)" >> <[email protected]> >> 10/15/2008 07:42 AM >> Please respond to >> [email protected] >> >> To >> [email protected] >> cc >> >> Subject >> Re: Delete Option >> >> ** >> You can do this in aradmin, select the required view of the form, open >> view properties, in menu access tab of view properties, deselect delete >> option. >> >> Regards, >> Rohini Prasher >> >> From: Action Request System discussion list(ARSList) >> [mailto:[email protected]] On Behalf Of Gary Roach >> Sent: Wednesday, October 15, 2008 5:01 PM >> To: [email protected] >> Subject: Delete Option >> >> ** >> List, >> >> Is it possible to remove the Delete option in the tool bar so users >> cannot >> delete records ? Currently, they can go to ->Actions ->Delete and >> delete >> records. I had a filter that ran on Delete but, it was somehow causing >> my >> archiving not to run. I disabled it and archiving ran. I still do not >> want the users to be able to delete records. >> >> Adminstrator=6.3 patch 15 >> HP-UX >> Client=6.00.01 patch1364 >> >> Thank you, >> >> Gary Roach >> Project Services Analyst >> T 724.539.1510 >> F 724.539.5797 >> >> Kennametal Inc. | 1600 Technology Way | Latrobe, PA 15650 | >> www.kennametal.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
