I have used the ShowInformationMessage function in a QAction which works perfectly in our TEST DMS.
Our TEST DMS is a 1 agent dms with a single failover pair.
Screenshot below shows code and successful message pop up from the element in TEST DMS.
However when I deploy the EXACT same protocol into our Production DMS, which runs the same version of dataminer and cube client I never get the popup message, but do see the protocol.Log line above succesfully makes it into the element log.
Our Production DMS is 8 agents with failover pairs.
What am I missing for this to no longer work in our Prod DMS.
The Qaction is being triggered from a standalone write parameter, as is supported and woking in TEST.
For both TEST and PROD, from Cube Client, About.
Server version : 10.5.12.0-16857
Client version : 10.6.2601.2484-5bef200b
Launcher version : 10.6.2624.752-899d3473
Hi Sam,
This issue is related to a known bug that was addressed via DataMiner release note 43958: General Feature Release 10.6.1 | DataMiner Docs
The fix is included in DataMiner versions 10.5.0 CU10 and 10.6.1 core.
Based on your Dojo question, your server is currently running 10.5.12, which means the fix has already been introduced in the next increment of the feature release track 10.6.1.
Please make sure to carefully select your upgrade version, as your client is already running a more recent version. If you need further assistance or guidance on upgrading, feel free to reach out.
Kind regards,
Thijs
RN explained that: "When a QAction triggered an information message with regard to a particular element, SLNet would incorrectly only forward that message to the DataMiner Agent that hosted that element. As a result, that information message would not appear in client applications connected to any of the other DataMiner Agents in the system."
So in some cases the message might have come through, in case your element that pushed the notification ran on the DataMiner node your client was connected to.