I would like to export the project as an XML file, as is it possible in Studio

Hi @Brett Saviano,

thanks for the information! I just mentioned it in the proper section of my article. 

You're welcome 😊 I'm happy you found it useful 

Thank you Brett,

if it's feasible for you, link this article to the one you're writing in order to connect articles on similar subjects. I'll do the same 

Thanks!!

Thanks, Julius! That was part of the problem. I'm still facing some issue but now I'm able to reach a web service deployed with another program (in the next days I will retry with Render).

The Gateway is very interesting, but could it work on 2021.1?

Edit. I think so, as on Github it says IRIS supports the Gateway from version 2020.3. I will try it, thanks!

Ok, probably that's the problem. I was looking for this information but I couldn't find it before. I'm not sure if I can upgrade the remote server. Is there an alternative?

Thanks!

Hi Enrico,

Thank you for the response. I've tried both adding an OnFailureTimeout method in my custom BO and directly modifying the OnFailureTimeout method inside the Ens.BusinessOperation. However, in the first case, nothing happens, while in the second case, the error "ERROR #5883: Item 'Ens.BusinessOperation' is mapped from a database that you do not have write permission on" occurs

Thanks! This is what I was looking for, it's a good idea. 

Hi Ashok,

Thank you for your response. As I said to Ian, maybe I expressed wrong and I apologize for any confusion, but I did not intend to start a new line within the log that is printed in the Visual Trace. Instead, I wanted to start a new line within VSC in order to avoid writing long one-line logs in the visual interface of VSC.

For example, I am looking for a way to transform this line of code:

$$$LOGINFO("this is the first line "_$c(13,10)_"this is second line"_$c(13,10)_" this is third line")

 Into something like that, to improve code readability: 

$$$LOGINFO("this is the first line "
            _$c(13,10)_"this is second line"
            _$c(13,10)_" this is third line")

Hi Ian,

Thank you for your response. Maybe I expressed wrong and I apologize for any confusion, but I did not intend to start a new line within the log that is printed in the Visual Trace. Instead, I wanted to start a new line within VSC in order to avoid writing long one-line logs in the visual interface of VSC.

For example, I am looking for a way to transform this line of code:

$$$LOGINFO("this is the first line "_$c(13,10)_"this is second line"_$c(13,10)_" this is third line")

 Into something like that, to improve code readability: 

$$$LOGINFO("this is the first line "
            _$c(13,10)_"this is second line"
            _$c(13,10)_" this is third line")

No, I don't have any HTML-type formatting. This is the message displayed through the trace: 

To display this message in the visual trace, I used the following code:

$$$TRACE("object: 'No response or error was received in reply to the previous message, attempting to resend the message.', "_$CHAR(10)_"retryCount: '"_..RetryCount_"'"_$CHAR(10)_"ResponseTimeout: '"_httpRequest.Timeout_"'")

I used $CHAR(10) to insert a new line since the $$$TRACE command isn't affected by syntax like "\n." 

Thank you Alex, how can I modify the OnFailureTimeout method for my purpose? I can find only a little documentation

Thank you Luis, this was useful. 

However, I've encountered two issues while adapting the code you provided to my specific situation:

if ..RetryCount = 1 {
    ; Find the production
    #dim p As Ens.Config.Production
    Set p = ##class(Ens.Config.Production).%OpenId("ProductionName")
    if '$isObject(p) {
        $$$LOGERROR("Production not found")
        quit
    }
    #dim item As Ens.Config.Item
    #dim sett As Ens.Config.Setting
    ; Loop over all the elements of the production 
    for i=1:1:p.Items.Count() {
        s item=p.Items.GetAt(i)
        ; Find the desired business component
        if (item.Name="Component1Name"
            ||(item.Name="Component2Name"))
            {
            $$$LOGINFO(item.Name_" found")
            ; Explore settings
            for s=1:1:item.Settings.Count() {
                set sett=item.Settings.GetAt(s)
                ; Search for the FailureTimeout
                if (sett.Name="FailureTimeout"){
                    $$$LOGINFO(sett.Name_" found")
                    ; Change the valure of the FailureTimeout based on the Severity
                    If Severity = "high" {
                        set sett.Value = -1
                    } Else {
                        set sett.Value = 30
                    }
                } 
            }
        }
    } 
    Set sc = p.%Save()
    If $$$ISERR(sc) { 
        $$$LOGERROR($System.Status.GetErrorText(sc))
        quit
    } 
}

With this code, I can adjust the FailureTimeout value based on the Severity parameter, and the updated value is correctly shown in the Production settings. Nevertheless, there are a couple of issues:

1. This functionality only applies to modified settings, as it doesn't affect settings with default values, which are not included in the loop (set sett=item.Settings.GetAt(s)). Consequently, it's necessary to modify the settings at least once to ensure they are processed within the loop.
2. While the FailureTimeout value gets updated, the sending procedure uses this updated value for the subsequent message, not the current one. As a consequence, the current message continues to operate with the outdated FailureTimeout value, causing the sending (and re-sending) procedure to deviate from the desired timeouts. 

Hi Rich, sorry for the late response but I've worked on other projects for some times.

I believe the issue with my code lies in the fact that the POST request was sent via a %Net.HttpRequest object:

// Send an HTTP POST request
Set messageStatus = httpRequest.Post(operation)

rather than using directly the adapter: 

set tsc = ..Adapter.PostURL(URL,.tResponse,,InputStream)

so the Timeout property of the %Net.HttpRequest object wasn't affected by the change on Response Timeout.

I solved this issue with a little help of @Menno Voerman's suggestion:

Set tHttpRequest.WriteTimeout = ..Adapter.WriteTimeout
Set tHttpRequest.Timeout = ..Adapter.ResponseTimeout
Set tHttpRequest.OpenTimeout = ..Adapter.ConnectTimeout  

In this way is possible to modify the response timeout dinamically too. 

I'm not sure if switching to the Adapter.PostURL method is a better choice compared to using httpRequest.Post. For now, I'm using the latter to minimize changes in my code.

Thanks Tani, this was very helpful!

Thanks for the suggestion, I will!

Thanks Evgeny, this is a good solution for who use Docker!

Thanks John, this is an interesting feature! Unfortunately I've only IRIS 2021.1 😓