Problem with Overriding
** Hi, Problem Description Overridden Filter A submits a record in Form F1 with value X in Column1 Filter B executes on submit of Form F1 and checks the push field if condition (Column1=X) and modifies the form F2 But Filter B has been failing at push field if condition even if Column1 got the value X The problem is Filter B could not identify value X in Column1 of Form F1 in push filed if condition (I think the problem with overriding but I need to have overriding in my workflows) How to overcome the above problem Any help would be appreciated Thanks and Regards, Gopala Krishna.Peela __20060125___This posting was submitted with HTML in it___
Re: Problem with Overriding
** Are you using the transaction value for Form F1? You may want to try TR.Column1 since that checks the transaction value being pushed to F1. CRAIG J. CARTER From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Gopala Krishna Peela Sent: Thursday, October 05, 2006 5:44 AM To: arslist@ARSLIST.ORG Subject: Problem with Overriding Hi, Problem Description Overridden Filter A submits a record in Form F1 with value X in Column1 Filter B executes on submit of Form F1 and checks the push field if condition (Column1=X) and modifies the form F2 But Filter B has been failing at push field if condition even if Column1 got the value X The problem is Filter B could not identify value X in Column1 of Form F1 in push filed if condition (I think the problem with overriding but I need to have overriding in my workflows) How to overcome the above problem Any help would be appreciated Thanks and Regards, Gopala Krishna.Peela __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___
Re: Problem with Overriding
** Hi, Thanx for response.Can we use like TR.Column1 in push field if condition? Thanks and Regards, Gopala Krishna.Peela From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Carter, Craig J Civ ARPC/DPD Sent: Thursday, October 05, 2006 5:44 PM To: arslist@ARSLIST.ORG Subject: Re: Problem with Overriding Are you using the transaction value for Form F1? You may want to try TR.Column1 since that checks the transaction value being pushed to F1. CRAIG J. CARTER From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Gopala Krishna Peela Sent: Thursday, October 05, 2006 5:44 AM To: arslist@ARSLIST.ORG Subject: Problem with Overriding Hi, Problem Description Overridden Filter A submits a record in Form F1 with value X in Column1 Filter B executes on submit of Form F1 and checks the push field if condition (Column1=X) and modifies the form F2 But Filter B has been failing at push field if condition even if Column1 got the value X The problem is Filter B could not identify value X in Column1 of Form F1 in push filed if condition (I think the problem with overriding but I need to have overriding in my workflows) How to overcome the above problem Any help would be appreciated Thanks and Regards, Gopala Krishna.Peela __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___
Re: Problem with Overriding
** In filter Run If qualifications only (not Set Field or Push Field If qualifications), the qualification can access values for the current record from the current transaction or from the database. This makes it possible for you to check state transitions. (From Remedy Help File) I think we can not use TR and DB in SetField or Push Field qualifications. any how I will try it out as you say.. Thanks and Regards, Gopala Krishna.Peela From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Carter, Craig J Civ ARPC/DPD Sent: Thursday, October 05, 2006 6:04 PM To: arslist@ARSLIST.ORG Subject: Re: Problem with Overriding The TR and DB qualifiers are used in the main filter condition. On submit to form F1, filter B condition would be TR.Column1 = X. You would then just use your push field to update form F2 with the value you want. Since your filter is firing on a submit, you want to check the value being submitted. If this doesnt work, you may need to provide more information. Is this only on submission of a new record or update of an existing record in form F1? CRAIG J. CARTER From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Gopala Krishna Peela Sent: Thursday, October 05, 2006 6:18 AM To: arslist@ARSLIST.ORG Subject: Re: Problem with Overriding Hi, Thanx for response.Can we use like TR.Column1 in push field if condition? Thanks and Regards, Gopala Krishna.Peela From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Carter, Craig J Civ ARPC/DPD Sent: Thursday, October 05, 2006 5:44 PM To: arslist@ARSLIST.ORG Subject: Re: Problem with Overriding Are you using the transaction value for Form F1? You may want to try TR.Column1 since that checks the transaction value being pushed to F1. CRAIG J. CARTER From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Gopala Krishna Peela Sent: Thursday, October 05, 2006 5:44 AM To: arslist@ARSLIST.ORG Subject: Problem with Overriding Hi, Problem Description Overridden Filter A submits a record in Form F1 with value X in Column1 Filter B executes on submit of Form F1 and checks the push field if condition (Column1=X) and modifies the form F2 But Filter B has been failing at push field if condition even if Column1 got the value X The problem is Filter B could not identify value X in Column1 of Form F1 in push filed if condition (I think the problem with overriding but I need to have overriding in my workflows) How to overcome the above problem Any help would be appreciated Thanks and Regards, Gopala Krishna.Peela __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___
Re: Problem with Overriding
** You are correct (as is the manual)you cannot use those in the push field and set field qualifications and Im not recommending that You simply have filter B check whether TR.Column1 = X and if it does, your true condition will be push the value you want to form F2. Your condition in the push fields action will be to identify the record in form F2 where the value should be pushed. CRAIG J. CARTER From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Gopala Krishna Peela Sent: Thursday, October 05, 2006 6:46 AM To: arslist@ARSLIST.ORG Subject: Re: Problem with Overriding In filter Run If qualifications only (not Set Field or Push Field If qualifications), the qualification can access values for the current record from the current transaction or from the database. This makes it possible for you to check state transitions. (From Remedy Help File) I think we can not use TR and DB in SetField or Push Field qualifications. any how I will try it out as you say.. Thanks and Regards, Gopala Krishna.Peela From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Carter, Craig J Civ ARPC/DPD Sent: Thursday, October 05, 2006 6:04 PM To: arslist@ARSLIST.ORG Subject: Re: Problem with Overriding The TR and DB qualifiers are used in the main filter condition. On submit to form F1, filter B condition would be TR.Column1 = X. You would then just use your push field to update form F2 with the value you want. Since your filter is firing on a submit, you want to check the value being submitted. If this doesnt work, you may need to provide more information. Is this only on submission of a new record or update of an existing record in form F1? CRAIG J. CARTER From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Gopala Krishna Peela Sent: Thursday, October 05, 2006 6:18 AM To: arslist@ARSLIST.ORG Subject: Re: Problem with Overriding Hi, Thanx for response.Can we use like TR.Column1 in push field if condition? Thanks and Regards, Gopala Krishna.Peela From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Carter, Craig J Civ ARPC/DPD Sent: Thursday, October 05, 2006 5:44 PM To: arslist@ARSLIST.ORG Subject: Re: Problem with Overriding Are you using the transaction value for Form F1? You may want to try TR.Column1 since that checks the transaction value being pushed to F1. CRAIG J. CARTER From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Gopala Krishna Peela Sent: Thursday, October 05, 2006 5:44 AM To: arslist@ARSLIST.ORG Subject: Problem with Overriding Hi, Problem Description Overridden Filter A submits a record in Form F1 with value X in Column1 Filter B executes on submit of Form F1 and checks the push field if condition (Column1=X) and modifies the form F2 But Filter B has been failing at push field if condition even if Column1 got the value X The problem is Filter B could not identify value X in Column1 of Form F1 in push filed if condition (I think the problem with overriding but I need to have overriding in my workflows) How to overcome the above problem Any help would be appreciated Thanks and Regards, Gopala Krishna.Peela __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___
Re: Problem with Overriding
** Thanks for help.. I had tried it but it was passing for TR.Column1 = X run if qualification And also tried for DB.Column1 = X.. but it was failed. I think with overriding it is Push field of filter A not committing the value into DB.. Is there any way we can do commit into DB for push field Thanks and Regards, Gopala Krishna.Peela Thanks and Regards, Gopala Krishna.Peela From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Carter, Craig J Civ ARPC/DPD Sent: Thursday, October 05, 2006 6:30 PM To: arslist@ARSLIST.ORG Subject: Re: Problem with Overriding You are correct (as is the manual)you cannot use those in the push field and set field qualifications and Im not recommending that You simply have filter B check whether TR.Column1 = X and if it does, your true condition will be push the value you want to form F2. Your condition in the push fields action will be to identify the record in form F2 where the value should be pushed. CRAIG J. CARTER From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Gopala Krishna Peela Sent: Thursday, October 05, 2006 6:46 AM To: arslist@ARSLIST.ORG Subject: Re: Problem with Overriding In filter Run If qualifications only (not Set Field or Push Field If qualifications), the qualification can access values for the current record from the current transaction or from the database. This makes it possible for you to check state transitions. (From Remedy Help File) I think we can not use TR and DB in SetField or Push Field qualifications. any how I will try it out as you say.. Thanks and Regards, Gopala Krishna.Peela From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Carter, Craig J Civ ARPC/DPD Sent: Thursday, October 05, 2006 6:04 PM To: arslist@ARSLIST.ORG Subject: Re: Problem with Overriding The TR and DB qualifiers are used in the main filter condition. On submit to form F1, filter B condition would be TR.Column1 = X. You would then just use your push field to update form F2 with the value you want. Since your filter is firing on a submit, you want to check the value being submitted. If this doesnt work, you may need to provide more information. Is this only on submission of a new record or update of an existing record in form F1? CRAIG J. CARTER From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Gopala Krishna Peela Sent: Thursday, October 05, 2006 6:18 AM To: arslist@ARSLIST.ORG Subject: Re: Problem with Overriding Hi, Thanx for response.Can we use like TR.Column1 in push field if condition? Thanks and Regards, Gopala Krishna.Peela From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Carter, Craig J Civ ARPC/DPD Sent: Thursday, October 05, 2006 5:44 PM To: arslist@ARSLIST.ORG Subject: Re: Problem with Overriding Are you using the transaction value for Form F1? You may want to try TR.Column1 since that checks the transaction value being pushed to F1. CRAIG J. CARTER From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Gopala Krishna Peela Sent: Thursday, October 05, 2006 5:44 AM To: arslist@ARSLIST.ORG Subject: Problem with Overriding Hi, Problem Description Overridden Filter A submits a record in Form F1 with value X in Column1 Filter B executes on submit of Form F1 and checks the push field if condition (Column1=X) and modifies the form F2 But Filter B has been failing at push field if condition even if Column1 got the value X The problem is Filter B could not identify value X in Column1 of Form F1 in push filed if condition (I think the problem with overriding but I need to have overriding in my workflows) How to overcome the above problem Any help would be appreciated Thanks and Regards, Gopala Krishna.Peela __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___
