Hello

You can send you're POST/GET URL's as part of the method itself. Refer the below sample codes

  Set httprequest=##class(%Net.HttpRequest).%New()
  Set httpRequest.ContentType = "application/json"
  Set httpRequest.Server = "renderProjectName.onrender.com"
  set httprequest.https=1 ;add this additional set if you're going to make it as a HTTPS call
  set httprequest.SSLConfiguration = "your ssl certificate" ; include the certificate as well for HTTPS call's
  Do httprequest.Post("/")

As for As I see there is no option to export the Business partners along with production export. Even there is no option with with deployable settings and config.Item definition as well. The Business partner details are stored in Ens. Config.BusinessPartner.

So, I hope you need to manually export your global's and import in to the another instance. 

hello @Yone Moreno 

You don't need to include the query params in the Url. That's is basically available in %request CSP object. You can take the query parameter values like below. And :studies represents it's a dynamic URL parameter value.

XData UrlMap [ XMLNamespace = "http://www.intersystems.com/urlmap" ]
{
<Routes>
<Route Url="/:studies" Method="GET" Call="consultarEstudiosDatosPaciente"/>
</Routes>
}

ClassMethod consultarEstudiosDatosPaciente(studies As %String="") As %Status
{
    
    set patientId = %request.Get("patientId")
    /// or 
    set patientId = %request.Data("patientId", 1)
    return $$$OK
}

Generally we can't execute the macros directly in terminal, studio output. The Macro preprocessor aka MPP do converts the marcos into the expression or function at the time of compilation. So, You can open and use the .int file for the specific code. 

Test.mac
macromac
 write $$$EnsMajorVersion ; 
Test.int
macromac
 write $system.Version.GetMajor() ; 

Get the relevant value of macros and execute it in terminal or output window.

Hello @Colin Brough 

I Believe, There is no functional difference between rule 1 and rule 2 except the invoking the DTL twice and finally call the Target. By default it has the feature to call multiple targets once the transformation completed. You utilized the feature in rule 2. That's the exact way to call multiple target unless different message and different transformation required. There will be a performance difference should be there. Because it executes the DTL first every time and eventually call the targets asynchronously(Whether it's asynchronous or synchronous It depends on the configuration in production Business process).

The syntax of $$$LOGINFO won't allow you make it in multiple lines. Instead you can set it in local variable and pass the variable in LOGINFO for better visibility 

set log= "object: 'This is a try'"
    		_"this is the second line with an example parameter: "_$get(x,1)
    		_"this is the third line with an example parameter: "_$get(y,5)
    
$$$LOGINFO(log)