This is such a pet peeve of mine.  Not sure if this is "fixed" in 8.0 or
8.1 (we are on 7.6.4 sp5).   

OK, fine Remedy Application Service is always taking over the modified
by field, but then there should be (OOB) a field of when a real person
touched it.  For example, I created a service request, that created a
Work Order.  When I go to the Work Order console and do a filter on
Submitted by Me, guess what?  Nothing comes up because it's the app
service that created the Work Order.  So we have to customize,
customize, customize.

Lisa

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Suresh Loganathan
Sent: Friday, April 11, 2014 10:38 AM
To: [email protected]
Subject: Re: Remedy Application Service showing in Submitter and Last
Modified Field

** 

Roger/Tauf,

Thanks for the information.The ways are 1. Check the info with audit log
and 2. create customization.

am I right? Any idea about AR_Escalator? Recently, we can see the info
from people form.

Regards,
Suresh Loganathan.


On Apr 11, 2014 7:44 PM, "Roger Justice" <[email protected]> wrote:


        ** This is a standard rejection workflow and it does not capture
who did the rejection. You will need to create a customization off of
the Signature form to capture the specific person that cancels the
Change.
        
        
        
        -----Original Message-----
        From: Suresh Loganathan <[email protected]>
        To: arslist <[email protected]>
        Sent: Fri, Apr 11, 2014 9:59 am
        Subject: Remedy Application Service showing in Submitter and
Last Modified Field
        
        
        ** 
        Team,
        Having a big issue in my remedy environment with  "Remedy
Application Service" and  " AR_Escalator".
        Believe, it's an Out Of Box behaviour. Scenario: 1, if we reject
the change from CHG:Infrastructure Change form. The work info submitter
field showing as Remedy Application Service.
        It's creating a confusion who reject the change. Have tried with
logs enable with Escalation, ACTL and FLTR.
        Do we have any option to fix this change via configuration work?
Kindly advise.
        Regards,
        Suresh Loganathan.
        _ARSlist: "Where the Answers Are" and have been for 20 years_ 
        _ARSlist: "Where the Answers Are" and have been for 20 years_

_ARSlist: "Where the Answers Are" and have been for 20 years_ 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to