go to post Eduard Lebedyuk · 5 hr ago This can possibly work if you make %Persistent a secondary superclass. In that case, new properties would go to a separate subscript, and your setup can maybe work (requires testing). Storage works like this (parent has N properties, Child - X): Child Extends %Persistent, Parent: ^a(id) = $lb("", prop1, prop2, ..., propX) Child Extends Parent, %Persistent: ^a(id) = $lb("Child", propA, propB, ..., propN) ^a(id, "Child") = $lb(propO, propP, ..., propX)
go to post Eduard Lebedyuk · Feb 17 I use return where it's important that we exit (middle of the loop, etc) immediately, in all other cases I use quit.
go to post Eduard Lebedyuk · Feb 12 I think you might want to track these numbers instead: Number of properties. $lb is list, so the larger the number of elements in a list the longer the time to get to the last element. Also larger larger lists exhaust the global buffer faster, so they might be less optimal. Method size in sloc. Ideally, your class shouldn't have methods spanning hundreds (thousands) of lines. I wouldn't worry about total class length, but rather the number of individual elements and method sizes. There's also class limits docs, but if you hit them, you probably have an issue already.
go to post Eduard Lebedyuk · Feb 11 I'm thinking we may need to create a custom business operation extending the default one EnsLib.HL7.Operation.TCPOperation, and we would need to wrap up the RetryCount inside the response. What do you think? I think you are correct. RetryCount is a runtime property, I don't think it's stored anywhere longterm, so you need a custom BO to save it. There are some workarounds you can attempt: Query event log Get current retry count using: $$$GetJobMonitor(tConfigName,$$$SystemName_":"_$Job,$$$eMonitorRetry) But I would definitely recommend subclassing.
go to post Eduard Lebedyuk · Feb 9 Great tutorial, but please consider adding IAM policies/roles jsons.
go to post Eduard Lebedyuk · Feb 9 Check ParseIOStream/ParseFramedIOStream from EnsLib.HL7.Parser. These methods take a stream (read to a specific position) and return next HL7 message. Overall loop can be seen in EnsLib.HL7.Service.FileService's OnProcessInput.
go to post Eduard Lebedyuk · Feb 5 Circular dependency possibly? I'd recommend outputting dynamic object on every pass.
go to post Eduard Lebedyuk · Jan 8 However, it is often difficult to test just the REST API without inadvertently involving the authentication scheme, the web application configuration, or even network connectivity. Those are a lot of hoops to jump through just to test the code within your dispatch class. Another way you can do this is by splitting web (rest) api from the business logic. I think ideally your REST handler method does only the following two things: Parses incoming request Verifies incoming request (debatable, might also be offloaded to the underlying API) Calls underlying API This way you can focus on unit testing your underlying api layer and keep the REST parts of your implementation as simple as possible.
go to post Eduard Lebedyuk · Jan 8 You can use BPs to do that automatically. BS (pool size 1) sends file to BP (1 request, pool size 1). BP parses the file and sends X async requests to BO (pool size >1) for processing, total request count is stored in BP. BP OnError/OnResponse methods are called once rows are being processed, maintain count here. Once OnError/OnResponse count matches original count send a final batch request.
go to post Eduard Lebedyuk · Dec 18, 2025 a-z, A-Z only. Everything else is considered non-alphabetic, although I guess non-latin characters would be a more correct term.
go to post Eduard Lebedyuk · Dec 17, 2025 PS: why is the correct result in the testNumbers method 321 and not 213? Thanks for noticing! Fixed.
go to post Eduard Lebedyuk · Dec 16, 2025 Check out %GetSetting implementation in Ens.Config.DefaultSettings: // Look in table starting with most specific match If $D(^Ens.Config.DefaultSettingsD(pProductionName,pItemName,pHostClassName,pSettingName),data) || $D(^Ens.Config.DefaultSettingsD("*", pItemName,pHostClassName,pSettingName),data) || $D(^Ens.Config.DefaultSettingsD(pProductionName,"*", pHostClassName,pSettingName),data) || $D(^Ens.Config.DefaultSettingsD("*", "*", pHostClassName,pSettingName),data) || $D(^Ens.Config.DefaultSettingsD(pProductionName,pItemName,"*", pSettingName),data) || $D(^Ens.Config.DefaultSettingsD("*", pItemName,"*", pSettingName),data) || $D(^Ens.Config.DefaultSettingsD(pProductionName,"*", "*", pSettingName),data) || $D(^Ens.Config.DefaultSettingsD("*", "*", "*", pSettingName),data) In your case your first setting would be resolved on line three: $D(^Ens.Config.DefaultSettingsD(pProductionName,"*", pHostClassName,pSettingName),data) And your second setting would be resolved on line five: || $D(^Ens.Config.DefaultSettingsD(pProductionName,pItemName,"*", pSettingName),data) But since line three resolves to a valid setting, line five would never be hit. To work around that provide both item name and class name explicitly - it would be resolved on the first line for your outlier (since both item and class match) and the rest of the items would get their setting resolved on line three.
go to post Eduard Lebedyuk · Dec 15, 2025 1️⃣ When you joined the Developer Community and how you first discovered it. November 2015 not long after DC started. @Evgeny Shvarov told me about it. 2️⃣ A meaningful moment or story from your personal journey here. I've been writing my Continuous Delivery series for seven years now! That's one of my longest writing projects.3️⃣ An article, question, or discussion you consider especially valuable — one you believe others should take the time to revisit. Lots of great stuff to find here on DC! This post by @Guillaume Rongier is probably the one I revisited the most over the years. This post by @Dmitry Maslennikov too. This comment by @Timothy Leavitt (wrote an article based on that). Also this one - should be in product imo.
