Hi Listers,
I finally got the solution for this issue:
Required functionality can be obtained as follow
1) Every user must have unrestricted Access - unchecked in people
form and they should have company level restrictions
2) Open the form "RQC:ServiceRequestConsole" in remedy
administrator tool (admin tool) - Open table properties
(z2TH_ServiceRequest)
- Open the tab "Table/Tree property"
- In Qualification - Remove ('Submitter' = $ User $ ) AND
This will allow user to see the entire request belong to his company.
I am VERY happy :-)
On Oct 4, 4:10 pm, Ri Mez <[EMAIL PROTECTED]> wrote:
> Unfortunately, this will not be acceptable for our customer who wants
> to be able to see all [Public] Work Info.
>
> On Oct 4, 3:18 pm, Roger Justice <[EMAIL PROTECTED]> wrote:
>
>
>
> > I made the work info tab hidden since it was the requester.
>
> > -----Original Message-----
> > From: Ri Mez <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Sent: Thu, 4 Oct 2007 9:06 am
> > Subject: Re: ITSM v7 -RequestorConsole- View All issues by company
>
> > Thanks Roger,
>
> > Did you allow them to have access to the Work Info in your view? The
> > issue I've come across is that whenever I try to configure access like
> > you are describing they can still see the Internal Work Info.
>
> > Richard
>
> > On Oct 4, 1:52 pm, Roger Justice <[EMAIL PROTECTED]> wrote:
> > > I created a new view of the HPD:Helpdesk form that is read only and used
> > > it
> > when the view button I created on the Requesterconsoletable field was
> > selected
> > to view an Incident. This minimizes the user trying to change the Incident.
> > If
> > they tried to modify an Incident with Incident Viewer permissions they get
> > an
> > error message and in some instances will complain.
>
> > > -----Original Message-----
> > > From: Ri Mez <[EMAIL PROTECTED]>
> > > To: [EMAIL PROTECTED]
> > > Sent: Thu, 4 Oct 2007 3:27 am
> > > Subject: Re: ITSM v7 -RequestorConsole- View All issues by company
>
> > > Hi Roger,
>
> > > Thanks for the feedback. Could you possibly provide more detail on
> > > this? What were the risks involved in this method? When you said that
> > > you created a new "requestorread only" were you referring to a new
> > > permission group?
>
> > > Any further feedback would be VERY much appreciated.
>
> > > Cheers.
> > > Richard
>
> > > On Oct 3, 2:23 pm, Roger Justice <[EMAIL PROTECTED]> wrote:
> > > > I had to implement a similar request for a client and added a new table
> > field
> > > that used the overviewconsoleso that they could see both Incident and
> > Changes
> > > that they were the Requester. I then created a new Requester Read Only for
> > > Incident and Change and provided each user with a Incident Viewer and
> > > Change
> > > Viewer Permissions
>
> > > > -----Original Message-----
> > > > From: Ri Mez <[EMAIL PROTECTED]>
> > > > To: [EMAIL PROTECTED]
> > > > Sent: Wed, 3 Oct 2007 6:00 am
> > > > Subject: ITSM v7 -RequestorConsole- View All issues by company
>
> > > > Hi,
>
> > > > I currently have a customer who needs to be able to see *all issues*
> > > > which they generated (through the RC). Currently the RC will only show
> > > > all of the issues that the logged in user generated.
>
> > > > Does anyone have any experience with providing therequestorconsole
> > > > users with an overview of *all issues* generated from/for their
> > > > company (in a muti-tenacy environment)?
>
> > > > The users are actually the customer companies internal IT. When they
> > > > have an issue regarding a product we support (the operating company)
> > > > they generate an issue through the RC.
>
> > > > I've thought about giving the Incident Viewer permissions but this
> > > > also allows them to see the internal work info logs (not good).
>
> > > > Any feedback would be much appreciated.
>
> > > > Regards,
> > > > Richard
>
> > > > _______________________________________________________________________________
> > > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.orgARSlist:"Where
> > > > the
> > > > Answers Are"
>
> > > > ________________________________________________________________________
> > > > Email and AIM finally together. You've gotta check out free AOL Mail!
> > > -http://mail.aol.com
>
> > > > _______________________________________________________________________________
> > > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.orgARSlist:"Where
> > > > the
> > > Answers Are"
>
> > > _______________________________________________________________________________
> > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.orgARSlist:"Where the
> > > Answers Are"
>
> > > ________________________________________________________________________
> > > Email and AIM finally together. You've gotta check out free AOL Mail!
> > -http://mail.aol.com
>
> > > _______________________________________________________________________________
> > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.orgARSlist:"Where the
> > Answers Are"
>
> > _______________________________________________________________________________
> > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.orgARSlist:"Where the
> > Answers Are"
>
> > ________________________________________________________________________
> > Email and AIM finally together. You've gotta check out free AOL Mail!
> > -http://mail.aol.com
>
> > _______________________________________________________________________________
> > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.orgARSlist:"Where the
> > Answers Are"
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives atwww.arslist.orgARSlist:"Where the
> Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
