Just a blind shot, but in 7.x the Public group has to be "Change" type.
Regards,
Nicky Madjarov
phone: 973-202-4278
Find out how to bust your AR System performance @
http://www.SpeedUpARS.com
----- Original Message -----
From: "Mitchell, Sharon N. (MSFC-IS30)[UNITeS]" <[email protected]>
Newsgroups: public.remedy.arsystem.general
To: <[email protected]>
Sent: Wednesday, May 06, 2009 3:44 PM
Subject: Re: Floating License/Write Access Problem after Upgrade to 7.1
Misi,
I tried this and got the same result. Thanks for the suggestion though!
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Misi Mladoniczky
Sent: Wednesday, May 06, 2009 2:26 PM
To: [email protected]
Subject: Re: Floating License/Write Access Problem after Upgrade to 7.1
Hi,
I do not know about this particular problem, but would it not be possible
to use the Submitter Mode Locked setting and set the Submitter-field to
the same as Login Name and Assigned To?
With this setting, you can update the User-record without a write-license.
You can fix up your current records by exporting to an ARX-file and then
reimporting using AR Import where you set the Submitter-field to the
correct value.
This sounds like a bug though... If a write-license is available, you
should definitely be able to update. If it is only out-of-the-box
workflow, it should work anyway...
I had an issue in an update where one of the field became NULL instead of
Zero, which caused the process to hang. This was in conjunction with an
upgrade from 6.3 to 7.1. I think I fixed the data with export/import to
ARX in this case as well.
Best Regards - Misi, RRR AB, http://www.rrr.se
Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
* RRR|Translator - Manage and automate your language translations.
Find these products, and many free tools and utilities, at http://rrr.se.
We upgraded our server from 7.0.1 to 7.1 this past weekend. We are now
having a problem with our floating license users updating their own user
records. The fields they are trying to update have Assignee permissions
(write access), and they are the assignee of their own user records.
When first logging in, they're given a Read (floating) license. When
trying to update their own user record, they get:
ARERR [331] You do not have write access (for this entry) to field :
[field(s) trying to update]
What's strange is they can go to any another form (even when first logging
in) and update a record with no problem. At this point they're given a
write Floating license. Then after that, they can go to their user record
and update it with no problem.
So why aren't they given a write Floating license when first trying to
update their user record?
Any ideas are greatly appreciated.
Thanks,
Sharon
Windows 2003
AR Server/Email Engine 7.1 patch 6
Approval Server 7.0.1
Oracle 10g
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
--
This message was scanned by ESVA and is believed to be clean.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
