Re: Disable change flag

2013-11-15 Thread Lucero, Michelle
Hi, Vidya:

The proper syntax is  $OPERATION$ ="SET".

Again, I would go with the advice of others and run logging to find out what 
workflow is firing on "Display".

Thank you,
Michelle
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of vidyasagar kommu
Sent: Friday, November 15, 2013 12:43 AM
To: arslist@ARSLIST.ORG
Subject: Re: Disable change flag

**
Hi ,

I have written a Active Link
$OPERATION$ = "MODIFY"
If Action RunProcess: SET-CHANGE-FLAG [1]

I am not getting any error but my issue is not resolved when I am searching 
records in form if i move the cursor one record to another record without any 
changes it is asking for "Do You Want to save the record".

Requesting you to guide me .

Thanks
Vidya
On Thu, Nov 14, 2013 at 2:05 PM, LJ LongWing 
mailto:lj.longw...@gmail.com>> wrote:
**
Sagar,
What is the actual run-process that you are executing, please 
copy/pastebecause what you have provided isn't proper syntax.  Andwhat 
is the error you are getting, if any.

On Thu, Nov 14, 2013 at 6:57 AM, vidyasagar kommu 
mailto:kommuvidyasa...@gmail.com>> wrote:
**
Hi All,


When we have a list of records in a form after a search and we scroll up and 
down without making any change, we must never get the question "Do you want to 
save the request".

As we know we can do the  field to make disable  change flag should be enable 
so that it will not ask for the "Do you want to save the request"



Could you please guide me how to use the Disable Change flag using the Run 
process .
I have written one workflow which will fire window open,Load ,Display
Run if: $Operation$!="CREATE"
If action : SET CHANGE FLAG 0

But it is not working ...

Requesting you to guide how to resolve.

Thanks in advance
Regards
Sagar
_ARSlist: "Where the Answers Are" and have been for 20 years_

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



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

--
This message, and any attachments, is for the intended recipient(s) only, may 
contain information that is privileged, confidential and/or proprietary and 
subject to important terms and conditions available at 
http://www.bankofamerica.com/emaildisclaimer.   If you are not the intended 
recipient, please delete this message.

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


Re: EXTERNAL: Re: Disable change flag

2013-11-15 Thread Reiser, John J
Vidya,
What is your trigger for this? ( Display, Window Open etc)
This action tells the client that something was modified on that record. 
SET-CHANGE-FLAG [1] turns the flag ON.
Then when you leave the current record the system wants to know if you need to 
save your changes.

A few others have given you sound advice. Find the Active Link that is making a 
change to your record when you view it. Active Link logging is your best bet. 
If you find an active link that is setting something like a Display Only field 
you would probably want to find out if disabling the change flag for that field 
is an option. Some display only fields are used as change triggers so don't 
just disable it without investigating.

HTH,
---
John J. Reiser
Remedy Developer/Administrator
Senior Software Development Analyst
Lockheed Martin - MS2
The star that burns twice as bright burns half as long.
Pay close attention and be illuminated by its brilliance. - paraphrased by me

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of vidyasagar kommu
Sent: Friday, November 15, 2013 1:43 AM
To: arslist@ARSLIST.ORG
Subject: EXTERNAL: Re: Disable change flag

**
Hi ,

I have written a Active Link
$OPERATION$ = "MODIFY"
If Action RunProcess: SET-CHANGE-FLAG [1]

I am not getting any error but my issue is not resolved when I am searching 
records in form if i move the cursor one record to another record without any 
changes it is asking for "Do You Want to save the record".

Requesting you to guide me .

Thanks
Vidya
On Thu, Nov 14, 2013 at 2:05 PM, LJ LongWing 
mailto:lj.longw...@gmail.com>> wrote:
**
Sagar,
What is the actual run-process that you are executing, please 
copy/pastebecause what you have provided isn't proper syntax.  Andwhat 
is the error you are getting, if any.

On Thu, Nov 14, 2013 at 6:57 AM, vidyasagar kommu 
mailto:kommuvidyasa...@gmail.com>> wrote:
**
Hi All,


When we have a list of records in a form after a search and we scroll up and 
down without making any change, we must never get the question "Do you want to 
save the request".

As we know we can do the  field to make disable  change flag should be enable 
so that it will not ask for the "Do you want to save the request"



Could you please guide me how to use the Disable Change flag using the Run 
process .
I have written one workflow which will fire window open,Load ,Display
Run if: $Operation$!="CREATE"
If action : SET CHANGE FLAG 0

But it is not working ...

Requesting you to guide how to resolve.

Thanks in advance
Regards
Sagar
_ARSlist: "Where the Answers Are" and have been for 20 years_

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



--
Sagar _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"


Re: Disable change flag

2013-11-15 Thread Kemes, Lisa A DLA CTR INFORMATION OPERATIONS
Do you know what's causing the change to begin with?  Have you turned on
any logs?  I would start there...

-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of vidyasagar kommu
Sent: Friday, November 15, 2013 1:43 AM
To: arslist@ARSLIST.ORG
Subject: Re: Disable change flag

** 
Hi ,
 
I have written a Active Link 
$OPERATION$ = "MODIFY"
If Action RunProcess: SET-CHANGE-FLAG [1]
 
I am not getting any error but my issue is not resolved when I am
searching records in form if i move the cursor one record to another
record without any changes it is asking for "Do You Want to save the
record".
 
Requesting you to guide me .
 
Thanks
Vidya


On Thu, Nov 14, 2013 at 2:05 PM, LJ LongWing 
wrote:


** 
Sagar, 
What is the actual run-process that you are executing, please
copy/pastebecause what you have provided isn't proper syntax.
Andwhat is the error you are getting, if any.


On Thu, Nov 14, 2013 at 6:57 AM, vidyasagar kommu
 wrote:


** 
Hi All,
 
When we have a list of records in a form after a search and we scroll up
and down without making any change, we must never get the question "Do
you want to save the request".

As we know we can do the  field to make disable  change flag should be
enable so that it will not ask for the "Do you want to save the request"

 

Could you please guide me how to use the Disable Change
flag using the Run process .
I have written one workflow which will fire window
open,Load ,Display 
Run if: $Operation$!="CREATE"
If action : SET CHANGE FLAG 0
 
But it is not working ...
 
Requesting you to guide how to resolve.
 
Thanks in advance
Regards
Sagar 
_ARSlist: "Where the Answers Are" and have been for 20
years_ 


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




-- 
Sagar _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"


Re: Disable change flag

2013-11-14 Thread vidyasagar kommu
Hi ,

I have written a Active Link
$OPERATION$ = "MODIFY"
If Action RunProcess: SET-CHANGE-FLAG [1]

I am not getting any error but my issue is not resolved when I am
searching records in form if i move the cursor one record to another record
without any changes it is asking for "Do You Want to save the record".

Requesting you to guide me .

Thanks
Vidya

On Thu, Nov 14, 2013 at 2:05 PM, LJ LongWing  wrote:

> **
> Sagar,
> What is the actual run-process that you are executing, please
> copy/pastebecause what you have provided isn't proper syntax.
>  Andwhat is the error you are getting, if any.
>
>
> On Thu, Nov 14, 2013 at 6:57 AM, vidyasagar kommu <
> kommuvidyasa...@gmail.com> wrote:
>
>> **
>>  Hi All,
>>
>>
>> When we have a list of records in a form after a search and we scroll up
>> and down without making any change, we must never get the question "Do you
>> want to save the request".
>>
>> As we know we can do the  field to make disable  change flag should be
>> enable so that it will not ask for the "Do you want to save the request"
>>
>>
>> Could you please guide me how to use the Disable Change flag using the
>> Run process .
>> I have written one workflow which will fire window open,Load ,Display
>> Run if: $Operation$!="CREATE"
>> If action : SET CHANGE FLAG 0
>>
>> But it is not working ...
>>
>> Requesting you to guide how to resolve.
>>
>> Thanks in advance
>> Regards
>> Sagar
>> _ARSlist: "Where the Answers Are" and have been for 20 years_
>
>
> _ARSlist: "Where the Answers Are" and have been for 20 years_




-- 
Sagar

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


Re: Disable change flag

2013-11-14 Thread Mueller, Doug
Finally,

Why on $OPERATION$ != "CREATE"?   This is really only an issue on the modify 
window
so why not $OPERATION$ = "MODIFY"?

And, why on all the firing conditions you  are stating.  The message is only 
issued
on attempting to close the window.  So, why not fire on the conditions that are
about closing the window so that No matter when during the open window the 
change
occurs, the flag is cleared right at the point that the window is closing and
getting ready to issue the message?

Doug

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W
Sent: Thursday, November 14, 2013 6:06 AM
To: arslist@ARSLIST.ORG
Subject: Re: Disable change flag

I think the first question is what active links are changing data on displaying 
of a record.   Run active link logging and correct those so you don't have to 
resort to the SET-CHANGE-FLAG 

Also I hope it is just a typo in your email, but the run process command is  
SET-CHANGE-FLAG  not  SET CHANGE FLAG And is your workflow set at order 999 so 
it fires after all other active links?

Fred

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of vidyasagar kommu
Sent: Thursday, November 14, 2013 7:57 AM
To: arslist@ARSLIST.ORG
Subject: Disable change flag

**
Hi All,
 
When we have a list of records in a form after a search and we scroll up and 
down without making any change, we must never get the question "Do you want to 
save the request".
As we know we can do the  field to make disable  change flag should be enable 
so that it will not ask for the "Do you want to save the request"
 
Could you please guide me how to use the Disable Change flag using the Run 
process .
I have written one workflow which will fire window open,Load ,Display Run if: 
$Operation$!="CREATE"
If action : SET CHANGE FLAG 0
 
But it is not working ...
 
Requesting you to guide how to resolve.
 
Thanks in advance
Regards
Sagar 

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "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"


Re: Disable change flag

2013-11-14 Thread Grooms, Frederick W
I think the first question is what active links are changing data on displaying 
of a record.   Run active link logging and correct those so you don't have to 
resort to the SET-CHANGE-FLAG 

Also I hope it is just a typo in your email, but the run process command is  
SET-CHANGE-FLAG  not  SET CHANGE FLAG
And is your workflow set at order 999 so it fires after all other active links?

Fred

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of vidyasagar kommu
Sent: Thursday, November 14, 2013 7:57 AM
To: arslist@ARSLIST.ORG
Subject: Disable change flag

** 
Hi All,
 
When we have a list of records in a form after a search and we scroll up and 
down without making any change, we must never get the question "Do you want to 
save the request".
As we know we can do the  field to make disable  change flag should be enable 
so that it will not ask for the "Do you want to save the request"
 
Could you please guide me how to use the Disable Change flag using the Run 
process .
I have written one workflow which will fire window open,Load ,Display 
Run if: $Operation$!="CREATE"
If action : SET CHANGE FLAG 0
 
But it is not working ...
 
Requesting you to guide how to resolve.
 
Thanks in advance
Regards
Sagar 

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


Re: Disable change flag

2013-11-14 Thread LJ LongWing
Sagar,
What is the actual run-process that you are executing, please
copy/pastebecause what you have provided isn't proper syntax.
 Andwhat is the error you are getting, if any.


On Thu, Nov 14, 2013 at 6:57 AM, vidyasagar kommu  wrote:

> **
> Hi All,
>
>
> When we have a list of records in a form after a search and we scroll up
> and down without making any change, we must never get the question "Do you
> want to save the request".
>
> As we know we can do the  field to make disable  change flag should be
> enable so that it will not ask for the "Do you want to save the request"
>
>
> Could you please guide me how to use the Disable Change flag using the Run
> process .
> I have written one workflow which will fire window open,Load ,Display
> Run if: $Operation$!="CREATE"
> If action : SET CHANGE FLAG 0
>
> But it is not working ...
>
> Requesting you to guide how to resolve.
>
> Thanks in advance
> Regards
> Sagar
> _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"


Re: disable change flag on hidden fields

2011-09-02 Thread pritch
Actually, folks were updating the record and saving it (ignoring that msg) 
which caused some issues with various fields that were updated by the approval 
/ rejection.  It was either that or close the screen down (I'm on 7.6.03 and 
users access system strictly via web client) and they didn't like the idea of 
closing the screen.  I find that in most cases, by the time they clear the 
initial (warning) message that says 'your approval / rejection has been sent to 
the server for processing' the approval has been processed.  The 30 second 
limit was only put in for the event that the approval is tied up for some 
reason - haven't seen it actually hit that limit in production.  

Kind of surprised BMC didn't put something like that in out of the box.  I also 
had to do some work on the approval 're-assignments'.  With the web client it 
was returning 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 hidden fields

Genius - love that idea.
Did you do this specifically because of the "This record has been
updated by another user since you retrieved it..." received when
attempting to approve or reject the change request?

Regards,
 
Andrew Goodall
Software Engineer 2 | Development Services |  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 some workflow for my client that has a
'processing, please wait ..." message, go into a loop to detect that the
record has been updated by the application service and then refresh the
screen for them.  If after about 30 seconds it doesn't detect 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 change flag on hidden fields

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 additional fields. I *think* the only reason they do that is
to immediately reflect the current approval or SLA status on the change.

Take this scenario...

I open the change request and go to the approvals tab and approve my
change. My approval happens to move the change into "Completed" because
it's a close down approval. This could trigger an SLA to update the
ticket. So, if you have the ticket open while workflow fires in the
background, you'll get the "record has been updated" warning if you make
any other changes to the record. There are a lot of things going on in
background and really makes debugging a challenge.

Alternatively, if you have the change open during the approval process
and someone approves through approval central, you can can get the
record updated warning as well.

I think it's just a shortcoming in the design because when you offer
multiple entry points to update a record, toes are going to be stepped
on at some point.

Regards,
Mike Roper


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged 
material.  If the reader of this message is not the intended recipient,
you are hereby notified that your access is unauthorized, and any review,
dissemination, distribution or copying of this message including any 
attachments is strictly prohibited.  If you are not the intended
recipient, please contact the sender and delete the material from any
computer.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"


Re: disable change flag on hidden fields

2011-09-02 Thread Andrew C Goodall
Thanks LJ and everyone else for the responses. I realize logically why
these messages occur. This really all stemmed from me trying to
understand what BMC workflow is causing this just on an Approve or
reject selection from the process bar.

During this investigation I noticed that when a user clicked on the
approver tab the Save button would highlight because BMC did not disable
the change flag on some hidden z_Temp fields. So wondered under what
circumstances you may not want the change flag to be disabled on a
hidden field.

I realize that the "This record has been updated by another user since
you retrieved it..." is probably filter related from a push - probably
by them updating the Approval Status field.

BMC support just cam back and reported this is related to SW00342156.

 

Regards,

 

Andrew Goodall

Software Engineer 2 | Development Services |  jcpenney . www.jcp.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

 

Andrew,

As others have pointed out, the 'this record has been updated' is in
relation to the fact that when you hit 'save', the client checks the
last modified date of the record on the screen against the last modified
date on the server, if the two don't match (the one on the server is
newer), it gives you that message.  The 'disable change flag' is a flag
used on the client only that indicates if a field is changed and you
choose to close the window without saving, if the flag isn't set to
'false', then you get the prompt 'are you sure you want to navigate away
from this page' (Mid-Tier) or 'do you want to close this window without
saving' (client)but the answer to your question of 'why would you
want to do that'not entirely sure, I'm sure it was an oversight on
the developers part...I try to make 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

 

** 

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 retrieved it..."
even tough all they did was an Approve or reject action.

 

I found some BMC hidden z_Temp fields were the "disable change flag" =
false

 

So I'm trying to rack my brain as to why you'd ever want a hidden field
to have "disable change flag" = false?

 

Regards,

 

Andrew Goodall

Software Engineer 2 | Development Services |  jcpenney . www.jcp.com
<http://www.jcp.com/>  

 


The information transmitted is intended only for the person or entity to
which it is addressed and 
may contain confidential and/or privileged material. If the reader of
this message is not the intended
recipient, you are hereby notified that your access is unauthorized, and
any review, dissemination,
distribution or copying of this message including any attachments is
strictly prohibited. If you are not
the intended recipient, please contact the sender and delete the
material from any computer.

 

_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ 

_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"


Re: disable change flag on hidden fields

2011-09-02 Thread Andrew C Goodall
Genius - love that idea.
Did you do this specifically because of the "This record has been
updated by another user since you retrieved it..." received when
attempting to approve or reject the change request?

Regards,
 
Andrew Goodall
Software Engineer 2 | Development Services |  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 some workflow for my client that has a
'processing, please wait ..." message, go into a loop to detect that the
record has been updated by the application service and then refresh the
screen for them.  If after about 30 seconds it doesn't detect 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 change flag on hidden fields

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 additional fields. I *think* the only reason they do that is
to immediately reflect the current approval or SLA status on the change.

Take this scenario...

I open the change request and go to the approvals tab and approve my
change. My approval happens to move the change into "Completed" because
it's a close down approval. This could trigger an SLA to update the
ticket. So, if you have the ticket open while workflow fires in the
background, you'll get the "record has been updated" warning if you make
any other changes to the record. There are a lot of things going on in
background and really makes debugging a challenge.

Alternatively, if you have the change open during the approval process
and someone approves through approval central, you can can get the
record updated warning as well.

I think it's just a shortcoming in the design because when you offer
multiple entry points to update a record, toes are going to be stepped
on at some point.

Regards,
Mike Roper


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged 
material.  If the reader of this message is not the intended recipient,
you are hereby notified that your access is unauthorized, and any review,
dissemination, distribution or copying of this message including any 
attachments is strictly prohibited.  If you are not the intended
recipient, please contact the sender and delete the material from any
computer.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"


Re: disable change flag on hidden fields

2011-09-02 Thread LJ LongWing
Andrew,

As others have pointed out, the 'this record has been updated' is in
relation to the fact that when you hit 'save', the client checks the last
modified date of the record on the screen against the last modified date on
the server, if the two don't match (the one on the server is newer), it
gives you that message.  The 'disable change flag' is a flag used on the
client only that indicates if a field is changed and you choose to close the
window without saving, if the flag isn't set to 'false', then you get the
prompt 'are you sure you want to navigate away from this page' (Mid-Tier) or
'do you want to close this window without saving' (client)..but the answer
to your question of 'why would you want to do that'..not entirely sure, I'm
sure it was an oversight on the developers part.I try to make 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

 

** 

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 retrieved it..."
even tough all they did was an Approve or reject action.

 

I found some BMC hidden z_Temp fields were the "disable change flag" = false

 

So I'm trying to rack my brain as to why you'd ever want a hidden field to
have "disable change flag" = false?

 

Regards,

 

Andrew Goodall

Software Engineer 2 | Development Services |  jcpenney . www.jcp.com
   

 


The information transmitted is intended only for the person or entity to
which it is addressed and 
may contain confidential and/or privileged material. If the reader of this
message is not the intended
recipient, you are hereby notified that your access is unauthorized, and any
review, dissemination,
distribution or copying of this message including any attachments is
strictly prohibited. If you are not
the intended recipient, please contact the sender and delete the material
from any computer.

 

_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ 


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"


Re: disable change flag on hidden fields

2011-09-02 Thread pritch
Yes - I actually had to put in some workflow for my client that has a 
'processing, please wait ..." message, go into a loop to detect that the record 
has been updated by the application service and then refresh the screen for 
them.  If after about 30 seconds it doesn't detect 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 change flag on hidden fields

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 additional fields. I 
*think* the only reason they do that is to immediately reflect the current 
approval or SLA status on the change.

Take this scenario...

I open the change request and go to the approvals tab and approve my change. My 
approval happens to move the change into "Completed" because it's a close down 
approval. This could trigger an SLA to update the ticket. So, if you have the 
ticket open while workflow fires in the background, you'll get the "record has 
been updated" warning if you make any other changes to the record. There are a 
lot of things going on in background and really makes debugging a challenge.

Alternatively, if you have the change open during the approval process and 
someone approves through approval central, you can can get the record updated 
warning as well.

I think it's just a shortcoming in the design because when you offer multiple 
entry points to update a record, toes are going to be stepped on at some point.

Regards,
Mike Roper

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"


Re: disable change flag on hidden fields

2011-09-02 Thread Grooms, Frederick W
One scenario I can think of is the case where you need to do a push to that 
form to trigger some other change (Think of it like walking a table field when 
you don't want to put a table on a form).

I use this method for custom notifications.  I have a form that defines the 
selection criteria and the message.  On submit I do a push to the notification 
definition form modifying all matching records (all I set on the notification 
form is a display only temp field with the ticket id of the source).  Workflow 
on the definition form then does a push to send the messages.  If the disable 
change flag on the temp field was not set to false then the workflow to 
actually send the message would never fire.

Fred

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Andrew C Goodall
Sent: Thursday, September 01, 2011 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:Infrastructure Change" where 
users are receiving the message: 
"This record has been updated by another user since you retrieved it..." even 
though all they did was an Approve or reject action.

I found some BMC hidden z_Temp fields were the "disable change flag" = false

So I'm trying to rack my brain as to why you'd ever want a hidden field to have 
"disable change flag" = false?

Regards,
 
Andrew Goodall
Software Engineer 2 | Development Services |  jcpenney . www.jcp.com  

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"


Re: disable change flag on hidden fields

2011-09-01 Thread Mike Roper
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 additional fields. I 
*think* the only reason they do that is to immediately reflect the current 
approval or SLA status on the change.

Take this scenario...

I open the change request and go to the approvals tab and approve my change. My 
approval happens to move the change into "Completed" because it's a close down 
approval. This could trigger an SLA to update the ticket. So, if you have the 
ticket open while workflow fires in the background, you'll get the "record has 
been updated" warning if you make any other changes to the record. There are a 
lot of things going on in background and really makes debugging a challenge.

Alternatively, if you have the change open during the approval process and 
someone approves through approval central, you can can get the record updated 
warning as well.

I think it's just a shortcoming in the design because when you offer multiple 
entry points to update a record, toes are going to be stepped on at some point.

Regards,
Mike Roper

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"


Re: disable change flag on hidden fields

2011-09-01 Thread Roger Justice
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 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:Infrastructure Change” where 
users are receiving the message: 
“This record has been updated by another user since you retrieved it..." even 
tough all they did was an Approve or reject action.
 
I found some BMC hidden z_Temp fields were the “disable change flag” = false
 
So I’m trying to rack my brain as to why you’d ever want a hidden field to have 
“disable change flag” = false?
 
Regards,
 
Andrew Goodall
Software Engineer 2 | Development Services |  jcpenney . www.jcp.com  
 


The information transmitted is intended only for the person or entity to which 
it is addressed and 
may contain confidential and/or privileged material. If the reader of this 
message is not the intended
recipient, you are hereby notified that your access is unauthorized, and any 
review, dissemination,
distribution or copying of this message including any attachments is strictly 
prohibited. If you are not
the intended recipient, please contact the sender and delete the material from 
any computer.

_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ 

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"