If this is just a drop down field, then all you need to do is to flush the 
mid-tier cache. Then the changes will become visible in your WSDL. The consumer 
of your web service will then need to consume the new WSDL to see the changes. 
But again, try with the flush cache first.


> On Jan 24, 2017, at 5:08 PM, Kevin M Candelaria <[email protected]> wrote:
> 
> **
> ** Thomas
>  
> I added 3 new client types. to Field 1000000022
>  
> These were updated in every form. All I have left to do is the WebService to 
> update it because when I go visit the service it is not listed
>  
>  https://*******/arsys/WSDL/public/*****/HPD_IncidentInterface_WS 
> <https://*******/arsys/WSDL/public/*****/HPD_IncidentInterface_WS>
>  
> Kevin Candelaria
> Senior Technical Support Specialist
> Temple University Computer Services
> ( 215.204.3095 |   * <mailto:*[email protected]> 
> <mailto:[email protected]> <mailto:[email protected]> 
> <mailto:[email protected]>[email protected] <mailto:[email protected]>
>  
> From: Action Request System discussion list(ARSList) <[email protected] 
> <mailto:[email protected]>> on behalf of Thomas Miskiewicz 
> <[email protected] <mailto:[email protected]>>
> Sent: Tuesday, January 24, 2017 11:04 AM
> To: [email protected] <mailto:[email protected]>
> Subject: Re: Updating Incident Work info via webservice problem
>  
> ** Kevin,
> 
> what kind of changes were made to the form? What is the type of operation you 
> want to change? What exactly do you want to change?
> 
> 
> Thomas
> 
>> On Jan 24, 2017, at 4:51 PM, Kevin M Candelaria <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> **
>> I discovered that I need to make the change to the Webservice. The Primary 
>> form it calls has the changes already. How can I update the webservice to 
>> get the new data from the primary form that I changed?
>>  
>> Kevin Candelaria
>> Senior Technical Support Specialist
>> Temple University Computer Services
>> ( 215.204.3095 |   * <mailto:*[email protected]> 
>> <mailto:[email protected]> <mailto:[email protected]> 
>> <mailto:[email protected]>[email protected] <mailto:[email protected]>
>>  
>> From: Action Request System discussion list(ARSList) <[email protected] 
>> <mailto:[email protected]>> on behalf of Thomas Miskiewicz 
>> <[email protected] <mailto:[email protected]>>
>> Sent: Friday, January 20, 2017 1:46 AM
>> To: [email protected] <mailto:[email protected]>
>> Subject: Re: Updating Incident Work info via webservice problem
>>  
>> ** Hi Kevin,
>> 
>> you need to check the Mid-Tier Logs, because that’s the gate for your Web 
>> Service. You might want to check Filter log as maybe a filter is overwriting 
>> the values as their being set by the web Service.
>> 
>> 
>> Thomas Miskiewicz
>> Uninterrupted productivity for
>> BMC Remedy ARS - arsmacros.com <http://arsmacros.com/>
>> 
>>> On 20 Jan 2017, at 00:01, Kevin M Candelaria <[email protected] 
>>> <mailto:[email protected]>> wrote:
>>> 
>>> **
>>> Hello ARList folks,
>>>  
>>> I recently created 3 new Client Types for the drops down in the people form.
>>> We have an asp form page that is filled out and creates an incident via a 
>>> webservice.
>>> The incidents are created but one of the form fields when filled out does 
>>> not do a second pass and update the work info.
>>> Any other client types do work properly except the 3 new ones I made to 
>>> HPD:Help Desk
>>>  
>>> Any ideas or where I can look in Developer studio to see where the fail 
>>> point is? or what logs I can look into to see where the second pass is 
>>> failing for these 3 specific client types.
>>>  
>>>  
>>> Kevin Candelaria
>>> Senior Technical Support Specialist
>>> Temple University Computer Services
>>> ( 215.204.3095 |   * <mailto:*[email protected]> 
>>> <mailto:[email protected]> <mailto:[email protected]> 
>>> <mailto:[email protected]>[email protected] <mailto:[email protected]>
>>>  
>>> _ARSlist: "Where the Answers Are" and have been for 20 years_
>> 
>> _ARSlist: "Where the Answers Are" and have been for 20 years_
>> _ARSlist: "Where the Answers Are" and have been for 20 years_
> 
> _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"

Reply via email to