I’ve had this come up countless time just in the last 24 hours, specifically during testing. As part of isolating the issue, you have to take out actions, test, put them back in, etc. You can copy/paste XML but it’s a pain. The ability to just disable an action would be incredibly helpful.
On a related note, when something wrongs wrong with an action, finding the “error message” is challenging depending on which type of action it was. Even something as trivial as console.error in the runActionNode would be helpful here.
Good thoughts here guys. Sorry for the pain…
Would be a nice to have to conditionally render multiple actions with the ability to have them numbered so you can change the order via number assignment too.
Hey Gregg - If I’m understanding what your suggesting, check out and vote for https://community.skuidify.com/skuid/topics/action-framework-conditions and https://community.skuidify.com/skuid/topics/action-framework-conditions.
Two of the same link.
LOL, yeah, I was hoping he’d vote twice Nice catch Pat, haven’t finished my first cup of coffee yet.
Here’s the corrected links:
A workaround approach would be to remove the action, save the page, test, then revert to the previous Page Version. Understood it’s not as convenient.
Thank you for your patience! Skuid has implemented this idea in the new 13.0.4 release which is now available on the Skuid Releases page - in v2 pages you can now choose to skip actions in a sequence for the purpose of testing and debugging and enable them when you’re ready to turn them back on.
Best practices for upgrading can be found in Upgrading Skuid on Salesforce. As a reminder, Salesforce does NOT allow reverting back to prior versions of managed packages. Skuid always recommends installing new versions in a non-business critical sandbox environment to test all mission critical functionality before installing into a production environment. We also recommend that you update out of date themes after you upgrade. Please let us know if you continue to encounter any problems with this issue after upgrading.
Thanks again for sharing this idea!