Hi Team,
I have an issue in my environment, Close down approvals are getting
attached in Implementation Stage which can be approved by approvers and the
change still remains in implementation with pending task.
Please provide in case you have any information regarding this behavior.
Thanks,
Abhi
. After that the Change can be closed.
Now in ITSM 7.6, I am thinking this is about the same functionality as the
Close Down Approval. However I can’t figure out how to make it work.
Really don’t want to do anything custom if the functionality is already
there.
Thanks
Mark
*Mark Bri
7.6, I am thinking this is about the same functionality as the
Close Down Approval. However I can't figure out how to make it work. Really
don't want to do anything custom if the functionality is already there.
Thanks
Mark
Mark Brittain
Remedy Developer
ITILv3 Foundation
NaviSite -
: Wednesday, January 13, 2010 4:26 PM
To: arslist@ARSLIST.ORG
Subject: Re: Close Down approval - part 2
I am basing my approvals off Risk. I was just informed that we have 9
risk levels. Is there an easy way to add new risk levels? I know risk
is intergrated into the Calendar and the Change Risk
I am basing my approvals off Risk. I was just informed that we have 9
risk levels. Is there an easy way to add new risk levels? I know risk
is intergrated into the Calendar and the Change Risk Selection.
___
UNSUBSCRIBE or
Ok so I have figured out how to get my close down approvals to fire. Now the
issue is the following:
The close down approval only start IF status=Completed and statusreason=Final
Review Required.
What I would like is for users to be able to select "successful" or "successful
w/ i
o:arsl...@arslist.org] On Behalf Of Rick Cook
Sent: Tuesday, January 12, 2010 6:35 PM
To: arslist@ARSLIST.ORG
Subject: Re: Close Down approval
** Yeah, I saw that. All of our Approval Processes have nothing selected for
Change Timing, and on the Mappings, they are Normal for the Close Down
Approv
--
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Pierson, Shawn
Sent: Wednesday, January 13, 2010 8:31 AM
To: arslist@ARSLIST.ORG
Subject: Re: Close Down approval
I too have set up close down approvals by disabling all of the OOtB approval
processes a
hury | Forest Laboratories, Inc.
Analyst, Service Management
Mobile:646.483.2779
-Original Message-
From: Chowdhury, Tauf
Sent: Wednesday, January 13, 2010 9:27 AM
To: arslist@ARSLIST.ORG
Subject: RE: Close Down approval
Marcelo/Rick,
I am running CHM 7.0.3 p7 and have multiple approval p
erson
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Chowdhury, Tauf
Sent: Wednesday, January 13, 2010 8:27 AM
To: arslist@ARSLIST.ORG
Subject: Re: Close Down approval
Marcelo/Rick,
I am running CHM 7.0.3 p7 and have mul
our company.
On the "Approval Process Config" form, APR-SysApproval Definition I think, the
Close down approval is set to use the Process Name - Change Level -Close down.
Not sure if you checked this but the field System Approval Flag is Null. If set
to YES, the approval will automatical
says that there is a
> defect if the change has “latent” timing selected, the close down approval
> will not fire.
>
>
>
> BMC Knowledge Base article ID: 20006650
>
>
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> arsl...@arslist.org] *On Behal
FYI... if we do get it to work, here is an article that says that there is a
defect if the change has "latent" timing selected, the close down approval will
not fire.
BMC Knowledge Base article ID: 20006650
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arsli
e PhaseName: "implementation
> approval" working..
>
> I am able to create an "Approver Mapping" select the correct
> categorization, criteria, set the "Phase Name*" to Close Down Approval and
> set level=1 and approve if risk is <=3.
>
> I have go
ver Mapping" select the correct categorization,
criteria, set the "Phase Name*" to Close Down Approval and set level=1 and
approve if risk is <=3.
I have gone to Application Admin>Foundation>Advanced Options>Approval Process
Configuration:
Using the default process wi
the correct
> categorization, criteria, set the "Phase Name*" to Close Down Approval and
> set level=1 and approve if risk is <=3.
>
> I have gone to Application Admin>Foundation>Advanced Options>Approval
> Process Configuration:
> Using the default process with
hase Name*" to Close Down Approval and set level=1 and
approve if risk is <=3.
I have gone to Application Admin>Foundation>Advanced Options>Approval Process
Configuration:
Using the default process with name "Close Down Approval".
Begin: Completed (no status reason)
Ap
Hello everyone,
Approvals are skipped at Implementation Approval and Close Down Approval
phase.
Approval mappings are configured at Implementation Approval and Close Down
Approval phase and people, support Groups and functional roles are define.
All the Change Request were able to bypass
18 matches
Mail list logo
