Now that we have the protocol-as-solution functionality it's possible to put all the scripting code in just a few QActions and still maintain a readable and structured overview by making use of folders and separate cs files.
Is there negative impact when using just a few big QActions instead of many small QActions?
Jens Vandewalle [SLC] [DevOps Enabler] Selected answer as best 17th November 2020
With the protocol as solution, it can still make sense to have multiple QActions to organize your features and group your triggers.
This way you can at a glance know which parameters are linked to which specific features and what they do from the protocol XML.
João Severino [SLC] [DevOps Catalyst] Answered question 2nd October 2020