This issue can be solved by creating simple workflow that will delete the the entry in "ENT:Enttitlement Generate QUAL/CACHE" form just before the OOB workflow creates an entry.
Thanks Mahesh Sent from my iPhone On Aug 11, 2012, at 9:32 PM, Steve Baumann <[email protected]> wrote: > To the 'write access error', there does seem to be a bit of conflict or at > least confusion in the documentation. The statement in your original post, > "An individual with a BMC Remedy AR System Read license can act on-behalf-of > another individual, group, or company." is a true statement but only if they > happen to be the first person to do this for the 'other' entity. Subsequest > read-only licensed individuals who try to perform an on-behalf-of action for > that entity will get an error. As was stated earlier, the first action > creates an entry in ENT:Enttitlement Generate QUAL/CACHE form, but the second > person receives the error when updating this record. This is standard age-old > ARS licensing behavior. > > There is another note on page 19 of the SRM User's Guide that states: "Users > who are allowed to submit requests on behalf of another user must be assigned > a fixed or floating license so that they can manage the requests after > submitting them on behalf of the other user." So, in one place we're told > only a RO license is needed, then in another we're told a Write license is > needed (at least to 'manage' the requests). Based on the fact that users need > to modify a record created by a different user, Write license wins. > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
