Hi Flávio,

Is this what you’re looking for?

https://success.outsystems.com/Documentation/11/Extensibility_and_Integration/SOAP/Consuming_SOAP_Web_Services/Use_Advanced_Extensibility/Example%3A_Change_service_endpoint_at_runtime

Regards,

Nordin

Hi Nordin

I use this already in the onBeforeRequestAdvanced of the soap but in the scope of the scope it only accepts site properties but, like i said this site propertie would be share in all applications using this integration module. Is there a way to use something other than site properties or someway to pass a value too the onBeforeRequestAdvanced.

Hi Flávio,

If you would want to pass a value to the OnBeforeRequestAdvanced action, while not using a Site Property, AFAIK you're only option would be to use a Session Variable instead. You can access its value within the scope of the OnBeforeRequest action.

Regards,

Nordin

Or create a single entry entity where you fetch the URI from.
Then have a backoffice screen where you can change it (so it's somewhat like a site property)

I would advise against using a session variable, if you try to run it from a process or timer it will not have the desired value.

In that case, you should go with Joey's proposal. 

You can save the URI to an Entity and fetch the record via an Aggregate and pass the value to the ChangeEndpoint action.

Regards,

Nordin

Hi All

Isn't this what the action SetWebReferenceURL in the EnhancedWebReferences extension is for?

It only works for SOAP APIs, but that's what you're using, right?

Yes, but can i use this action before calling the soap action i need in another action besides the onBeforeRequest?

When i put the name of the soap in using in the input of the action SetWebReferenceURL i get this error.

Oh, I see.

OutSystems broke stuff that worked fine in older versions and is telling *you* to fix it.

That's nice.

Anyway, seems to be you need to wrap the calls to the SOAP API in an action, and one of the parameters for this wrapper has to be a caller identifier, so you can then fetch the endpoint from the database.

To be fair, using wrappers is a good idea anyway, because instead of having multiple espaces consuming the API, you'll only have one, which makes maintenance a lot easier.

Sorry could you elaborate a bit more? what is a caller identifier and are u sugesting for me to save the soap endpointst in the database? Is there any way i can do this dynamically change to the endpoint of the soap?

I even tried to call a soap action using a javascript node but it didnt seam to work.

Oh wait, I missread your post about using an entity to store the endpoints.

Well, I have bad news for you.

So, technically you can change site properties on runtime, it's just that doing it is usually a bad idea because it'll automatically do a TenantInvalidateCache which will kill the performance of your application.

Well, if you're only calling that SOAP API once a day in a timer, then it's not that bad, but if you're calling it in response to an action by the user then you really shouldn't do this.

The other only option I see would be to use an extension to call the SOAP API...

Edit to add: or it used to, these days it might only do an EspaceInvalidadeCache, which, while still being bad, is not as bad as the TenantInvalidateCache.

Hi All,

I am facing now the same issue when I consume a SOAP service with Outsystems 11 in the case I describe below:

I have 30 different fiscal companies, each of them with a software (ERP) exposing a SOAP service with the same WSDL (same structure/methods).

When I consume one of this services using deprecated SetWebReference (EnhancedWebReferences extension) action, it is perfect! Allows me to consume only 1 SOAP service instead of 30 SOAP services and communicate with each of them just changing the end point URI at run time with current scope of my wrapper action:

Now, after Outsystems upgrade to achieve SOAP v1.2, i can't implement same logic with callback action OnBeforeRequest. Why? Because i can't pass values to OnBeforeRequest as input variables, and, inside of it, we only have access to session variables or site properties, and using them, in my opinion, it is not a good idea...

In my opinion, it is not a good idea use:

• Session variables - asynchronous tasks (timers and processes) have no session
• Site Properties - EspaceInvalidadeCache 
• Database Entity to save URI at wrapper action and get it after at OnBeforeRequest - it is bad because i don't kown if i am processing right URI, and it is also not a good solution to lock(Get <Entity> ForUpdate) the entity and make "sequential requests" ... it doesn't make sense

Does anyone already have a solution to this problem?

Thanks!!