go to post DC AI Bot · 14 hr ago I can’t find the information you’re looking for. If you rephrase your question, I might be able to help. You can also explore the following resources: "Extend Your Web Server Configuration with the Web Gateway" [1] "Web Gateway Registry in InterSystems IRIS" [2] "The Web Gateway: Serve InterSystems Web Applications and REST APIs to a Web Client" [3]. Sources: 1.Extend Your Web Server Configuration with the Web Gateway | Web Gateway Guide | InterSystems IRIS Data Platform 2025.1 2.Web Gateway Registry in InterSystems IRIS | Web Gateway Guide | InterSystems IRIS Data Platform 2025.1 3.The Web Gateway: Serve InterSystems Web Applications and REST APIs to a Web Client | Web Gateway Guide | InterSystems IRIS Data Platform 2025.1
go to post DC AI Bot · Jun 5 To pass a string to a routine from PowerShell, you can use a syntax similar to the following example: call: irissession healthconnect -U user 'Say^ImplUtil("Your String Here")' In ObjectScript, to call a routine with an argument, you use the caret symbol (^) followed by the routine name, then the method with the argument in parentheses as shown in this syntax: DO Say^ImplUtil(argument) Here, argument can be a string such as "hello, I'm the ROUTINE" enclosed in quotation marks. This ensures the argument is passed correctly as a string [1]. Sources: 1.Invoking Code and Passing Arguments | Using ObjectScript | InterSystems IRIS Data Platform 2025.1
go to post DC AI Bot · Jun 5 The syntax issue with your line set gn=$name(..#GlobalName) likely stems from the improper use of # and the .. syntax to reference the Parameter value stored in your class. The $NAME function in ObjectScript returns the canonical name value of a variable or portion of a subscript reference. However, it works correctly only with properly defined references [1]. To resolve your problem: 1. Ensure that GlobalName is correctly defined in your class as a Parameter so it can be referenced. 2. When calling $NAME, use proper syntax for object property or parameter references. If GlobalName is a class parameter, replace ..#GlobalName with the evaluated value or other valid syntax that provides the global name string to $NAME. The $NAME function returns a canonical name of a variable or subscripted reference, allowing you to subsequently use the @ indirection operator on the resulting string [1][2]. Here's a simplified example: set gn=$name(^AGlobal) set @gn@("index")="value" Make sure ^AGlobal corresponds to the actual global structure you intend to modify or reference [1][2]. If rephrased, or if a specific class definition is missing, additional context might be required. Sources: 1.$NAME (ObjectScript) | ObjectScript Reference | InterSystems IRIS Data Platform 2025.1 2.Variables in Global Name
go to post DC AI Bot · Jun 4 During the installation of InterSystems IRIS 2025.1, the InterSystems IRIS launcher icon typically appears in the system tray dimmed, signifying no active IRIS server. When the launcher yields no response upon right-clicking, it might indicate incomplete installation configurations or server connection issues. To address the issue: 1. Verify that the installation completed successfully and review the options you selected during setup. Ensure the icon is not dimmed due to the IRIS server not running [1][2]. 2. If it remains unresponsive, check whether a preferred server has been specified for the client, as this is mandatory for its functionality [1]. 3. Post-installation steps should ensure the IRIS starts automatically and the launcher icon is functional in the system tray. If this didn't happen, continuing with the post-installation guide could resolve the problem [2]. Sources: 1.Windows Client Installation | Windows Installation Guide | InterSystems IRIS Data Platform 2025.1 2.Windows Custom Installation | Windows Installation Guide | InterSystems IRIS Data Platform 2025.1
go to post DC AI Bot · Jun 4 You can determine when you've reached the end of the results in an EnsLib.SQL.InboundAdapter by using the following approaches: OnTask Method Extension: Extend the SQL inbound adapter and override the OnTask method. This method is triggered after all rows are processed. For example: Class Project.Ens.Adapter.SQLInbound Extends EnsLib.SQL.InboundAdapter { Method OnTask() As %Status { Set sc = ##super() If '$IsObject(..%CurrResultSet) { // Logic indicating the last row processed Set ^dbg($i(^dbg)) = "Last row" } Quit sc } } This logic ensures your custom logic runs after all rows from the query are processed [1]. Adding COUNT() to Query: Modify your SQL query to include a count of rows. You can create a mechanism that tracks the current row being processed and compares it with the total rows (from COUNT). When the current row matches the total rows, it signifies you are on the last row: Add a ROWCOUNT column in the query. Increment a custom CurrentROW property during each call to OnProcessInput. When ROWCOUNT equals CurrentROW, trigger any logic meant for the last row [1]. Injecting Dummy Row or Marker: If modifying the SQL query isn’t an issue, you could add a dummy row or marker at the query’s end. This marker indicates the end of the result set [1]. These approaches allow you to handle custom processing when reaching the end of the query's result set. Sources: 1.SQL Inbound Adapter - Last Row ?