I would stay within the box as much as is possible without having to do client side scripting.
When you create the WS you want to create, I would define two separate operations, one for A to consume and the other for B to consume. And the one that needs those two fields, you can set your minOccurs and maxOccurs both to 1 making it mandatory for that operation, while the other should not be exposed to those two fields. Joe _____ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Abhijit Hendre Sent: Friday, October 04, 2013 6:58 AM To: arslist@ARSLIST.ORG Subject: Re: Question on Webservice ** Hi Neha, You can have same web service to be consumed by both application , A & B. What you can do is - add 2 new optional fields on base form where web service is defined. When Application B will consume web service , do not pass value for these fields . And, when Application A will consume web service , make it mandatory to pass those two fields. You can make those two fields mandatory at Application end using client side scripting such as JavaScript. Get hold of application guys to make that happen. Thanks, Abhijit H On 4 October 2013 16:07, Neha Khandelwal <jbpn...@gmail.com> wrote: Thanks Karthik ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "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"
