Learning

Hi Maximiliano A DomHelper object can be created in a QAction like this: DomHelper domHelper = new DomHelper(protocol.SLNet.SendMessages, “myDomModuleID”); With protocol being the SLProtocol object. The DomHelper class is available …

Hi Olivier, I get the impression that this question has already been answered in the comments. If this is indeed the case, could you select this answer to indicate that …

Hello Gerwin, Currently this isn’t supported, the only available virtual function connections supported are the ones that are reflected and mapped onto the main element/connector. If you feel like this …

Hi Robin, Unfortunately, there is no straightforward way to achieve the behaviour you are looking for. This limitation comes from how the “New Alarm” action works. As defined, it always …

Hi Maximiliano, When creating a new protocol solution, the solution will have a Dlls folder. In this folder, you can add any custom DLLs that are used by the connector. …

Hi Min, You could take a look at the data aggregator, which can collect the data through GQI queries.

Hi Dave, Good question, and thanks for raising this. The “Detect unsupported connector versions” BPA requires direct access to the DataMiner Catalog API. A DMZ-only connection to dataminer.services is not …

Hi Gerwin, The element.xml files will indeed be migrated to the database when enabling swarming. You can find more information in the instructions to enable swarming in our docs: Enabling …

I found the issue, I was trying to address the wrong ID’s, constructing the action JSON and calling a different method resolved my issue