Might not help you in this instance, but I always hide and rename the
real Last Modified By & Last Modified Time fields, add 2 new fields and 

Then I put in workflow that set these new fields appropriately (at about
Execution order 10 via filters of course). I always add a hidden display
on field called

"ztmp_ByPassWorkflow"

 

Then I can set whatever fields I wish via filters running in execution
order 1-9 including "ztmp_ByPassWorkflow"

Which typically does a goto 1000, this way I skip all the other set
fields/etc

 

I typically also do not update (my new Fields) Last Modified By and Time
if it is a System "User" doing the modification ex: AR_ESCALATOR, Remedy
Application Service, etc

 

Doug Tanner

 

 

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of LJ Longwing
Sent: Tuesday, December 09, 2008 10:09 AM
To: arslist@ARSLIST.ORG
Subject: Re: Escalation Issue

 

Please note that I said 'in a supported way'....BMC doesn't support
doing direct DB updates of tables...:)

 

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Vijayalakshmi Paulraj
Sent: Monday, December 08, 2008 10:57 PM
To: arslist@ARSLIST.ORG
Subject: Re: Escalation Issue

** 

You can also use a very simple SQL Update query....

 

update table_name set assignee_groups = ';0;'  where <your_condition>

Thanks&Regards, 
Vijayalakshmi Paulraj 

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of LJ Longwing
Sent: Tuesday, December 09, 2008 1:47 AM
To: arslist@ARSLIST.ORG
Subject: Re: Escalation Issue

 

Only way you can update a record without changing the last mod by and
date (in a supported way) is through a 'merge' action on the
record....you could if you would like, write an API program that would
update the records via merge, which wouldn't cause the last mod fields
to change (if I remember correctly)...or do you also need to set the
fields during the merge to have them not auto updated....I forget.

 

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Sree Vyas
Sent: Monday, December 08, 2008 12:55 PM
To: arslist@ARSLIST.ORG
Subject: Escalation Issue

** 

Hi All,

 

I have inherited one escalation which change Assignee group to "Public"
for all the records. I knew it changes the modified date to the current
date when Escalation date.

 

Could anybody suggest any way to change Assignee group to "0" without
modifying other fields in a record.

 

Thru Database?

 

Regards,

Vyas

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

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

------------------------------------------------------------------------
--------------------
 
This message, including any attachments, contains confidential
information 
intended for a specific individual and purpose, and is intended for the
addressee only. Any unauthorized disclosure, use, dissemination,
copying, or distribution of 
this message or any of its attachments or the information contained in
this e-mail, or the taking of any action based on it, is strictly
prohibited. If you are not the intended recipient, please notify the
sender immediately by return e-mail and delete this message.
 
------------------------------------------------------------------------
--------------------

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

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


DISCLAIMER Important! This message is intended for the above named person(s) 
only and is CONFIDENTIAL AND PROPRIETARY. If you are not the intended recipient 
of this e-mail and have received it in error, please immediately notify the 
sender by return email and then delete it from your mailbox. This message may 
be protected by the attorney-client privilege and/or work product doctrine.  
Accessing, copying, disseminating or re-using any of the information contained 
in this e-mail by anyone other than the intended recipient is strictly 
prohibited. Finally, you should check this email and any attachments for the 
presence of viruses, as the sender accepts no liability for any damage caused 
by any virus transmitted by this email.  Thank you.


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

Reply via email to