Do API logging in conjunction with this and look for the +CE entry to
the form this is pushing to.  You should be able to tell if that
succeeded or failed.
 
If it succeeded then something else is going on.
 
If BMC happens to be listening I'd love to be able to see the "run if"
values in logging for AL/Filters.... 
 
William Rentfrow
Principal Consultant, StrataCom Inc.
[email protected]
Corporate Website, www.stratacominc.com <http://www.stratacominc.com/> 
Blog, www.williamrentfrow.com <http://www.williamrentfrow.com/> 
715-410-8156 C
 

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of LJ Longwing
Sent: Wednesday, July 08, 2009 2:02 PM
To: [email protected]
Subject: Re: Push Fields Info in Filter Logs


** 
I believe if you don't see the fields it's indicative of the fact that
it didn't end up doing the push based on your qualification.....

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Lyle Taylor
Sent: Wednesday, July 08, 2009 12:43 PM
To: [email protected]
Subject: Push Fields Info in Filter Logs


** 

Hi All,

 

ARS 7.1 Patch 6

 

I'm trying to do some filter logging to track down why something isn't
working the way I'm expecting, and I'm running into a lack of
information.  It seems that some Push Fields actions show which fields
and values are getting pushed, and other Push Fields actions are not.
Does anyone know why it shows this information in some cases but not in
others?

 

Here's an example from my log file.  This entry shows what's being
pushed:

 

/* Wed Jul 08 2009 12:36:29.1890 */     Checking
"INT:FNDHPD:ACT:UPDATEASSOCIATIONSTATUS_100_PHAS"

         0: Push Fields -> "HPD:Associations"

               <deferred from filter
INT:FNDHPD:ACT:UPDATEASSOCIATIONSTATUS_100_PHAS>

               z1D Status Enum (1000005088) = 1

               z1D End Date 01 (1000005086) = 

               z1D End Date 02 (1000005087) = 

               z1D Start Date 02 (1000005083) = 

               z1D Action (1000000076) = TICKETUPDATE

               ConsolidatedStatus (301569500) = 8000

               z1D Start Date 01 (1000005082) = 11/10/2008 9:21:31 AM

 

Whereas for this other filter, this is all I get:

 

/* Wed Jul 08 2009 12:36:29.2050 */     Checking "LDS:MIRS:HPD:Update
Child Incident Relationship`!" (500)

    --> Passed -- perform actions

         0: Push Fields -> "LDS:MIRS:Associations"

 

I overrode philter phasing here hoping that it might show more info, but
even without it, I get essentially the same thing as the filter above
(showing that it was deferred), but still not showing the fields being
pushed.

 

Any ideas for why this is happening?

 

Thanks,

Lyle Taylor



NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

_Platinum Sponsor: [email protected] ARSlist: "Where the Answers
Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the
Answers Are"_ 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

Reply via email to