ning to a search screen (lost the CR for some reason). Set that up to
return to the CR and refresh the approval window.
- Original Message -
From: "Andrew C Goodall"
To: arslist@ARSLIST.ORG
Sent: Friday, September 2, 2011 10:13:02 AM
Subject: Re: disable change flag on hidde
.com
<http://www.jcp.com/>
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing
Sent: Friday, September 02, 2011 9:10 AM
To: arslist@ARSLIST.ORG
Subject: Re: disable change flag on hidden fields
An
jcpenney . www.jcp.com
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of pritch
Sent: Friday, September 02, 2011 9:04 AM
To: arslist@ARSLIST.ORG
Subject: Re: disable change flag on hidden fields
Yes - I actually had to put in som
e it so that all
system populated hidden fields have it set to true.
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Andrew C Goodall
Sent: Thursday, September 01, 2011 5:26 PM
To: arslist@ARSLIST.ORG
Subject: disable change flag on hidden fields
ct it, I put an alternate
message up that the approval will be processed momentarily, please refresh your
screen before making any additional changes.
- Original Message -
From: "Mike Roper"
To: arslist@ARSLIST.ORG
Sent: Friday, September 2, 2011 2:19:37 AM
Subject: Re: disable cha
6:26 PM
To: arslist@ARSLIST.ORG
Subject: disable change flag on hidden fields
**
ITSM 7.5.01
What are some of the scenario's where you'd want to keep the "disable change
flag" = false on a hidden field?
I ask because we're seeing some behavior on "CHG:Infr
While I haven't looked at this particular workflow in a while, I've seen that
issue with CHG as well. As far as I can tell there may be a few things going
on. The first is that the approval process updates the change and the second is
that if you have SLAs attached it's going to update some addi
That means the DB instance of the record has changed and do you want to
potentially over write the changes. Approvals fire filters that modify the DB
entry.
-Original Message-
From: Andrew C Goodall
To: arslist
Sent: Thu, Sep 1, 2011 7:26 pm
Subject: disable change flag on hidden
ITSM 7.5.01
What are some of the scenario's where you'd want to keep the "disable
change flag" = false on a hidden field?
I ask because we're seeing some behavior on "CHG:Infrastructure Change"
where users are receiving the message:
"This record has been updated by another user since you
9 matches
Mail list logo
