Hi all
I had a strange behavior that I don't know how to explain, and in case there is a workaround
Right now, I have a custom connector where there is a table filled with different endpoints, polling time, and last poll execution. There is a timer->group->action->parameter that triggers a QAction. This action picks every row in the table, compares polling time/last poll execution, and in case poll information from the endpoint.
Now I tried to add an extra parameter (button for each row) that will enable the possibility to force the poll for the selected row, so I went to add an extra trigger in the QAction and set the attribute row=true but I noticed that if I set this attribute, the trigger via timer will not work anymore :/
It is possible that if I had this row attribute, I would implicitly disable any other kind of interaction?
Hi Marco,
You ran into a limitation of the QAction triggers.
You can only have QActions trigger on "normal" parameters or on row parameters, but not on both simultaneously.
A workaround that you could look into is to have 2 QActions
- one for "normal" flow and without the row=true option
- another with the "force" flow and with the row=true option
Then, to make your code reusable, you could move the existing code into a precompiled QAction and reference it from your 2 other QActions.
You should move your code from your existing QAction into a new one that has the precompile option and point your existing one to it.
Then create a new one and also point to the precompile
You should end up with something similar to the following
<QAction id="1" name="Precompiled Code" encoding="csharp" options="precompile">
…
</QAction>
<QAction id="2" name="Process Timer" encoding="csharp" triggers="2" dllImport="[ProtocolName].[ProtocolVersion].QAction.1.dll">
…
</QAction>
<QAction id="3" name="Process Button" encoding="csharp" triggers="3" row="true" dllImport="[ProtocolName].[ProtocolVersion].QAction.1.dll">
…
</QAction>
Hi Severino
Thanks a lot for answering! and for the example, I'll try to fix it in this way then!
Hi Severino
I suspected that, thanks for the confermation than.
Just to be sure, the approch should be bring my QAction as precompiled, let it be used by the timer, and for the row I will create a new one that relay on the precompiled QAction, I'm right? Or I need 2 new QAction, one for the timer and nother for the row?