It sounds like a support ticket with BMC may be in order ;>( From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing Sent: Tuesday, July 08, 2014 2:53 PM To: arslist@ARSLIST.ORG Subject: Re: Filter set fields Web Service action setting field id 8 to null on error
** I've been assured many times over by Doug himself that the Web Service plugin doesn't use Field 8....but like this, I have seen otherwise. On Tue, Jul 8, 2014 at 12:49 PM, Campbell, Paul (Paul) <p...@avaya.com<mailto:p...@avaya.com>> wrote: ** OK, I have a strange condition happening, we have some filter Set fields web service calls that when the external web service returns some error condition, the filter sets field ID 8 to null, even when field ID 8 is not mapped in the set fields, this condition is causing the record submit to fail, even when I have an error handler associated with the filter. This is happening on many filters in our environment. Has anybody seen behavior occur like this? Our environment details are AR server version 7.6.04 SP4 201209051922 OS Version RHEL 6 DB Version Oracle 10G 10.2.0.5.0 - 64bit Custom app, no ITSM Here is a sanitized workflow log from an occurrence. The filter in question is BOB_SubmitNotificationTobob set fields action 0 and you can see where it sets field id 8 to null <WFLG> /* Tue Jul 08 2014 23:39:56 */ <WFLG> Workflow Trace Log -- ON <WFLG> BMC Remedy User Version 7.6.04 <CLAT> /* Tue Jul 08 2014 23:40:00.3760 */+API call <FLTR> /* Tue Jul 08 2014 18:10:29.3734 */ Start filter processing (phase 1) -- Operation - SET on PollingQueue - 000000000002046 <FLTR> /* Tue Jul 08 2014 18:10:29.3735 */ <Filter Level:0 Number Of Filters:1> Checking "PQ_SubmitBOBNotification_CallGuide" (102) <FLTR> --> Passed -- perform actions <FLTR> 0: Set Fields <FLTR> FiltersExecuted (536870955) = ... <FLTR> 1: Set Fields <FLTR> tmpDateText (536870944) = 07/08/2014 18:10:29 <FLTR> 2: Call Guide "SubmitBOBNotification_PushGuide" <FLTR> /* Tue Jul 08 2014 18:10:29.3811 */ <Filter Level:0 Number Of Filters:2> Checking "PQ_SubmitBOBNotification_G`!" (500) <FLTR> --> Passed -- perform actions <FLTR> 0: Set Fields <FLTR> FiltersExecuted (536870955) = ... <FLTR> 1: Push Fields -> "BOB_Notifications" <FLTR> code (601112005) = VCM <FLTR> NotificationType (536870931) = CVT_SUCCESS <FLTR> Command (2147483510<tel:%282147483510>) = SEND_NOTIFICATION <FLTR> Source_Form_Name (8) = PollingQueue <FLTR> Source_EntryID (536870919) = 000000000002046 <FLTR> RequestSource (536870932) = bob <FLTR> RequestorEmail (536870922) = b...@nobody.com<mailto:b...@nobody.com> <FLTR> SE_ID (706302002) = (628)076-2103 <FLTR> RequestorName (536878899) = BOB <FLTR> ReportID (536871046) = Change Me to FileLocation <FLTR> Description (536871044) = ConfigValidateExpert Request for (628)076-2103 <FLTR> SessionStatus (601112010) = Change me to Product Name <FLTR> ProductName (536870961) = Change me to Product Name <FLTR> NotificationDate (179) = 07/08/2014 18:10:29 <FLTR> AccountName (536870940) = Change me to Account Name <FLTR> RequestorPhoneNumber (536870926) = 9999999999 <FLTR> /* Tue Jul 08 2014 18:10:29.3854 */ Start filter processing (phase 1) -- Operation - CREATE on BOB_Notifications - <NULL> <FLTR> /* Tue Jul 08 2014 18:10:29.3854 */ <Filter Level:1 Number Of Filters:3> Checking "BOB_SubmitNotification_GetMethod" (0) <FLTR> --> Passed -- perform actions <FLTR> 0: Set Fields <FLTR> NotificationMethod (536870973) = <FLTR> /* Tue Jul 08 2014 18:10:29.3865 */ <Filter Level:1 Number Of Filters:4> Checking "BOB_SubmitNotification_ResetAttempts" (0) <FLTR> --> Passed -- perform actions <FLTR> 0: Set Fields <FLTR> SubmissionAttempts (536870938) = 0 <FLTR> /* Tue Jul 08 2014 18:10:29.3875 */ <Filter Level:1 Number Of Filters:20> Checking "BOB_SubmitNotificationTobob" (800) <FLTR> --> Passed -- perform actions <FLTR> 0: Set Fields <FLTR> Source_Form_Name (8) = <FLTR> Message not in catalog; Message number = 9130 <FLTR> PreparedStatementCallback; SQL [insert into bob.notification_request_event (request_id,notification_type,request_source,event_created_time,requestor_name,requestor_email,REPORT_ID,REPORT_TITLE,PRODUCT_TYPE,additional_info,device_info,notification_request <FLTR> **** Error while performing filter action: Error 9130 <FLTR> **** Filter "BOB_SubmitNotificationTobob_ConfigValidation_DEV": Calling filter error handler "BOB:ProcessFailure_LogErrorMsg" <FLTR> /* Tue Jul 08 2014 18:10:29.4764 */ Start filter processing (phase 1) -- Operation - ERROR-HANDLER on BOB_Notifications - <NULL> <FLTR> /* Tue Jul 08 2014 18:10:29.4764 */ <Filter Level:1 Number Of Filters:21> Checking "BOB:ProcessFailure_LogErrorMsg" (888) <FLTR> --> Passed -- perform actions <FLTR> 0: Set Fields <FLTR> ErrorTrap_AppendMessage (602008312) = PreparedStatementCallback; SQL [insert into bob.notification_request_event (request_id,notification_type,request_source,event_created_time,requestor_name,requestor_email,REPORT_ID,REPORT_TITLE,PRODUCT_TYPE,additional_info,device_info,notification_request <FLTR> ErrorTrap_LastAttemptTime (602008313) = 07/08/2014 18:10:29 <FLTR> ErrorTrap_Number (602008310) = 9130 <FLTR> ErrorTrap_Message (602008311) = Message not in catalog; Message number = 9130 <FLTR> 1: Set Fields <FLTR> ErrorTrap_History (536870963) = 9130 Message not in catalog; Message number = 9130 PreparedStatementCallback; SQL [insert into bob.notification_request_event (request_id,notification_type,request_source,event_created_time,requestor_name,requestor_email,REPORT_ID,REPORT_TITLE,PRODUCT_TYPE,additional_info,device_info,notification_request <FLTR> /* Tue Jul 08 2014 18:10:29.4769 */ End of filter processing (phase 1) -- Operation - ERROR-HANDLER on BOB_Notifications - <NULL> <FLTR> **** Filter "BOB:ProcessFailure_LogErrorMsg": Successfully handled filter error <FLTR> **** Filter "BOB_SubmitNotificationTobob_DEV" <FLTR> 1: Set Fields <FLTR> FiltersExecuted (536870955) = >>> <FLTR> LastSubmitAttempt (536870939) = 07/08/2014 18:10:29 <FLTR> SubmissionAttempts (536870938) = 1 <FLTR> /* Tue Jul 08 2014 18:10:29.4771 */ End of filter processing (phase 1) -- Operation - CREATE on BOB_Notifications - <NULL> <FLTR> 1: Push Fields -> "PQ_SubmitBOBNotification_G`!" (ARERR 552) <FLTR> **** Error while performing filter action: Error 552 <FLTR> **** Filter "PQ_SubmitBOBNotification_G`!": No enabled error handler <FLTR> /* Tue Jul 08 2014 18:10:29.4817 */ Call Guide "PQ_SubmitBOBNotification_PushGuide" (return) <FLTR> **** Error while performing filter action: Error 552 <FLTR> **** Filter "PQ_SubmitBOBNotification_CallGuide": Calling filter error handler "BOB:ProcessFailure_LogErrorMsg" <FLTR> /* Tue Jul 08 2014 18:10:29.4821 */ Start filter processing (phase 1) -- Operation - ERROR-HANDLER on PollingQueue - 000000000002046 <FLTR> /* Tue Jul 08 2014 18:10:29.4821 */ <Filter Level:0 Number Of Filters:22> Checking "BOB:ProcessFailure_LogErrorMsg" (888) <FLTR> --> Passed -- perform actions <FLTR> 0: Set Fields <FLTR> ErrorTrap_AppendMessage (602008312) = ORA-01400: cannot insert NULL into ("ARADMIN"."T604"."C8") <FLTR> ErrorTrap_LastAttemptTime (602008313) = 07/08/2014 18:10:29 <FLTR> ErrorTrap_Number (602008310) = 552 <FLTR> ErrorTrap_Message (602008311) = The SQL database operation failed. <FLTR> 1: Set Fields <FLTR> ErrorTrap_History (536870963) = 552 The SQL database operation failed. ORA-01400: cannot insert NULL into ("ARADMIN"."T604"."C8") <FLTR> /* Tue Jul 08 2014 18:10:29.4825 */ End of filter processing (phase 1) -- Operation - ERROR-HANDLER on PollingQueue - 000000000002046 <FLTR> **** Filter "BOB:ProcessFailure_LogErrorMsg": Successfully handled filter error <FLTR> **** Filter "PQ_SubmitBOBNotification_CallGuide" Paul Campbell | Systems Architect | | Avaya Client Services | | 678-421-5342<tel:678-421-5342> | Web Conference<https://collaborate.avaya.com/aacpa/?participantCode=4215342> | Audio Conference +1-513-228-8888<tel:%2B1-513-228-8888> code: 4215342 Everyone needs deadlines. Even the beavers. They loaf around all summer, but when they are faced with the winter deadline, they work like fury. If we didn’t have deadlines, we’d stagnate. Walt Disney _ARSlist: "Where the Answers Are" and have been for 20 years_ _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"
