Hi Chris,

 

Thanks for your kind suggestion.

Before that I have done one customization like "when anybody changes the
profile status, password should be reset (One common Password).

Bur it is work around for only Requestor console. Like when any Requestor
opens Remedy user. Authentication failed error comes because password has
been changed.

But when Internal support people create a ticket for requestor through
Incident management Console, one error comes but still ticket create for the
offline people.

 

Thanks, 

 

Sandeep 

Vyom Labs Pvt. Ltd. 

An ISO 20000 certified company. 

Consulting | Outsourcing | Training || BMC Remedy BSM | ITIL 

Web: www.vyomlabs.com  

 

 

 

 

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Moore, Christopher Allen
Sent: Thursday, July 17, 2008 10:11 PM
To: [email protected]
Subject: Re: People status other than enabled

 

Sandeep - 

 

I had this requirement a while back.  I put a character field on both the
home page and the requester console, and then populated it with the status
of the user profile when the form opened.  If it was anything other than
'Enabled' I closed the window (All Windows).  Pretty simple but it got the
job done.  A pretty savvy user could get around it by constructing a URL to
go straight to a form, but that's probably not going to happen.

 

Also make sure when you set people to offline you change their passwords.

 

Chris

 

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Lisa Westerfield
Sent: Thursday, July 17, 2008 9:37 AM
To: [email protected]
Subject: Re: People status other than enabled

 

We have run into this exact problem in various areas of the workflow.  For
some reason the 'Status' field is not often considered in the workflow
qualifications throughout ITSM, causing issues as you are seeing.  However,
I have found in at least one case where 'Status' was considered, but it only
ignored the record if it was set to "Obsolete" and not "Offline".  You may
want to try the "Obsolete" status first, and if that doesn't work you will
have to modify the workflow to consider the 'Status' field.

 

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of ITSM Support
Sent: Monday, August 06, 2007 6:33 AM
To: [email protected]
Subject: People status other than enabled

 

** 

Hi List,

 

When I modify the people information like "people status--offline" or other
than enabled, still Requester (Customer) is able to create an incident
ticket.

Even Support person is also able to create a ticket for offline customer.

 

Has anyone faced this problem before and how was it resolved?

 

Thanks, 

 

Sandeep 

Vyom Labs Pvt. Ltd. 

An ISO 20000 certified company. 

Consulting | Outsourcing | Training || BMC Remedy BSM | ITIL 

Web : www.vyomlabs.com   

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___ 

  <http://www.bmc.com/userworld/>   

TuringSMI is a Platinum Sponsor of both BMC UserWorld Events

Email Disclaimer  
This email has been sent from the TuringSMI Group 

This message is subject to and does not create or vary any contractual
relationship between TuringSMI, SMI Technologies, SMI Telco, its
subsidiaries or affiliates and you. Internet communications are not secure
and therefore the TuringSMI Group does not accept any legal responsibility
for the contents of this message. Any views or opinions expressed are those
of the author.  This message is intended for the addressee(s) only and its
contents and any attached files are strictly confidential. If you have
received it in error, please contact the sender on the number above.

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html_____Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers
Are" html___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to