Mohammad, you are using javascript right? Maybe I'm over simplifying things. If this is javascript, it would be a lot easier to capture the URL of the current page. Then, you could parse out the URL to find the current environment and/or build the URL to the next API call that you need to make. There are examples on-line here: How to Get the Current URL with JavaScript – JS Location Tutorial (freecodecamp.org)

I am an expert in Javascript, that was not my question, thank you tho Vickie Ortega !

Hi Mohammad. Based on your reply to Vickie, I assume your table is of non-sbm systems (otherwise you could determine the URL as she described.) SBM has a built in way of scaling endpoints. It is normally used in context of orchestrations, but is not limited to that context. First read this section of our product help:

https://docs.microfocus.com/doc/Solutions_Business_Manager/12.2/ttst_using_string_builder

Next, I would recommend creating a Custom Endpoint in your process app to represent your webservice endpoint. You would create this in Composer with an initial value (such as for a Dev Env), then once deployed, you would manage the endpoint's value per env in your Application Repository interface. When you deploy/promote, the current value of that's env's endpoint will be used dynamically.

From within your form logic, you can use the SBM String Builder to refer to the attributes of the Custom Endpoint such as its URL, AuthType, ID, Password, or UserName. For example, you could have a Form action that calls your custom javascript function with an argument in this format: (Where DemoEndpoint is the name of my custom endpoint).

myfunction("{#DemoEndpoint.URL}");

This is what I would recommend as best practice.

If you are committed to your previous approach, I would recommend a combination of a report on the aux table combined with a Rest Grid control, Embedded Report control, or a Rest Grid widget to consume the table and read from it in the form.

I dont think you got my point