In Progress
Remove remote sym bugged
easy one - when removing a remote sym from the Remote Sym list, it gets removed but doesn’t disappear from the list until you reload window
An Anonymous User 1 day ago
PowerOn Pro
In Progress
Remove remote sym bugged
easy one - when removing a remote sym from the Remote Sym list, it gets removed but doesn’t disappear from the list until you reload window
An Anonymous User 1 day ago
PowerOn Pro
In Progress
bad password is mistaken as validation problem
If you have bad login info when you attempt to validate, without Debug enabled, all you see is “found errors in FOO” which obscures the real issue. 2026-07-16 14:12:18.837 [info] [@libum-llc/symitar] [SymitarHTTPs] Validation response status: 200, data: {"TaskManager_PowerOnValidateAndInstall":{"exitCode":0,"message":"Error: Invalid User Number or Password.\n","status":"error","statistics":{"durationInMillis":200}},"message":"error"} 2026-07-16 14:12:18.838 [info] [@libum-llc/symitar] [SymitarHTTPs] TaskManager message: Error: Invalid User Number or Password. 2026-07-16 14:12:18.838 [info] [@libum-llc/symitar] [SymitarHTTPs] Validation failed for FOO 2026-07-16 14:12:18.838 [info] [@libum-llc/symitar] [SymitarHTTPs] Top-level error message: error 2026-07-16 14:12:18.839 [info] [validateSymitarPowerOn] found errors in FOO
An Anonymous User 1 day ago
PowerOn Pro
In Progress
bad password is mistaken as validation problem
If you have bad login info when you attempt to validate, without Debug enabled, all you see is “found errors in FOO” which obscures the real issue. 2026-07-16 14:12:18.837 [info] [@libum-llc/symitar] [SymitarHTTPs] Validation response status: 200, data: {"TaskManager_PowerOnValidateAndInstall":{"exitCode":0,"message":"Error: Invalid User Number or Password.\n","status":"error","statistics":{"durationInMillis":200}},"message":"error"} 2026-07-16 14:12:18.838 [info] [@libum-llc/symitar] [SymitarHTTPs] TaskManager message: Error: Invalid User Number or Password. 2026-07-16 14:12:18.838 [info] [@libum-llc/symitar] [SymitarHTTPs] Validation failed for FOO 2026-07-16 14:12:18.838 [info] [@libum-llc/symitar] [SymitarHTTPs] Top-level error message: error 2026-07-16 14:12:18.839 [info] [validateSymitarPowerOn] found errors in FOO
An Anonymous User 1 day ago
PowerOn Pro
In Progress
Validation task still spins in status bar after error
After saving a file, I got this error: [error] [validateSymitarPowerOn] socket hang up But the Validating status spinner continued to spin rather than realizing the task had failed
An Anonymous User 9 days ago
PowerOn Pro
In Progress
Validation task still spins in status bar after error
After saving a file, I got this error: [error] [validateSymitarPowerOn] socket hang up But the Validating status spinner continued to spin rather than realizing the task had failed
An Anonymous User 9 days ago
PowerOn Pro
Planned
When warning about mismatching includes, let me click the warning to open the file
“An #INCLUDE file has local changes:. Consider enabling "Auto Deploy Include Files" in settings.” Let me click the or the whole message itself to open the file in question so I can examine the diffs and easily deploy the file myself if I choose.
An Anonymous User 16 days ago
PowerOn Pro
Planned
When warning about mismatching includes, let me click the warning to open the file
“An #INCLUDE file has local changes:. Consider enabling "Auto Deploy Include Files" in settings.” Let me click the or the whole message itself to open the file in question so I can examine the diffs and easily deploy the file myself if I choose.
An Anonymous User 16 days ago
PowerOn Pro
In Progress
Allow re-clicking of current connection
When a connection fails, I currently must click Local Development and then back to my original connection in order to re-attempt connection. We either need a retry button, or we need to be able to re-select the current active connection to instruct it to reconnect.
An Anonymous User 26 days ago
PowerOn Pro
In Progress
Allow re-clicking of current connection
When a connection fails, I currently must click Local Development and then back to my original connection in order to re-attempt connection. We either need a retry button, or we need to be able to re-select the current active connection to instruct it to reconnect.
An Anonymous User 26 days ago
PowerOn Pro
In Progress
@divProjectError is incorrectly treated as number value (it is a "character" AKA string)
PowerOn Pro currently reports an operator-type-mismatch error (Cannot compare 'NUMBER' with 'CHARACTER') when writing code like the following: if @divProjectError <> "" then do [logic goes here] end Tested using PowerOn Pro 1.9.6.
Zebulan 2 months ago
PowerOn Pro
In Progress
@divProjectError is incorrectly treated as number value (it is a "character" AKA string)
PowerOn Pro currently reports an operator-type-mismatch error (Cannot compare 'NUMBER' with 'CHARACTER') when writing code like the following: if @divProjectError <> "" then do [logic goes here] end Tested using PowerOn Pro 1.9.6.
Zebulan 2 months ago
PowerOn Pro
Planned
Regularly sync content for eDocs or Help Center
We need to make sure we have accurate information available in our function signatures, hovers, etc. as releases changes in Symitar.
Dylan Martinez 2 months ago
PowerOn Pro
Planned
Regularly sync content for eDocs or Help Center
We need to make sure we have accurate information available in our function signatures, hovers, etc. as releases changes in Symitar.
Dylan Martinez 2 months ago
PowerOn Pro
In Progress
PowerOn Variable Limit
We have specfile variables over the 3000 limit. That limit of 3000 is still published in the Symitar eDocs. I ran a test and it seems the new limit is 6000. Can you verify and update your error “ Specfile exceeds PowerOn limit of 3000 combined variables/arrays/procedures” to reflect this new limit.
An Anonymous User 2 months ago
PowerOn Pro
In Progress
PowerOn Variable Limit
We have specfile variables over the 3000 limit. That limit of 3000 is still published in the Symitar eDocs. I ran a test and it seems the new limit is 6000. Can you verify and update your error “ Specfile exceeds PowerOn limit of 3000 combined variables/arrays/procedures” to reflect this new limit.
An Anonymous User 2 months ago
PowerOn Pro
In Progress
Add formatting option to place "do" on same line as "then"/"for each ..."/etc.
In my opinion, the current formatting for PowerOn files adds a lot of visual noise by giving do…end blocks their own indentation. In most coding languages, it is standard to put braces on the same line/indentation as the flow-control statement they’re attached to, and I think it would make sense to at least have that as an option in PowerOn Pro. For comparison, here is the current style enforced by the extension: if x = 5 then if x = 5 then do [etc.] end for each share with
Zebulan 2 months ago
PowerOn Pro
In Progress
Add formatting option to place "do" on same line as "then"/"for each ..."/etc.
In my opinion, the current formatting for PowerOn files adds a lot of visual noise by giving do…end blocks their own indentation. In most coding languages, it is standard to put braces on the same line/indentation as the flow-control statement they’re attached to, and I think it would make sense to at least have that as an option in PowerOn Pro. For comparison, here is the current style enforced by the extension: if x = 5 then if x = 5 then do [etc.] end for each share with
Zebulan 2 months ago
PowerOn Pro
Planned
Add Versioning to Parameter Manager
We need to have stateful parameters within Quest that are accessible via Pipelines.
Dylan Martinez 5 months ago
PowerOn Pipelines
Planned
Add Versioning to Parameter Manager
We need to have stateful parameters within Quest that are accessible via Pipelines.
Dylan Martinez 5 months ago
PowerOn Pipelines
Planned
Add deployment protections to Sym connections
Need to add organization owner the ability (through Libum Portal) to set restrictions on which Sym developers can deploy to.
Dylan Martinez over 1 year ago
Feature
PowerOn Pro
Planned
Add deployment protections to Sym connections
Need to add organization owner the ability (through Libum Portal) to set restrictions on which Sym developers can deploy to.
Dylan Martinez over 1 year ago
Feature
PowerOn Pro
In Progress
Cancel running batch job
Since these batch jobs don’t show up in batch control, we could use some way to cancel a currently running batch run initiated by PowerOn Pro.
An Anonymous User over 1 year ago
PowerOn Pro
In Progress
Cancel running batch job
Since these batch jobs don’t show up in batch control, we could use some way to cancel a currently running batch run initiated by PowerOn Pro.
An Anonymous User over 1 year ago
PowerOn Pro
In Progress
Add On-Demand rendering for PowerOn
Need to add support for rendering HTML on-demand PowerOn files within VS Code.
Dylan Martinez over 1 year ago
Feature
PowerOn Pro
In Progress
Add On-Demand rendering for PowerOn
Need to add support for rendering HTML on-demand PowerOn files within VS Code.
Dylan Martinez over 1 year ago
Feature
PowerOn Pro
In Progress
Add embedded support for HTML
Need to add syntax highlighting for inline HTML and remove requirement for managing the htmlViewLine function and others.
Dylan Martinez over 1 year ago
Feature
PowerOn Pro
In Progress
Add embedded support for HTML
Need to add syntax highlighting for inline HTML and remove requirement for managing the htmlViewLine function and others.
Dylan Martinez over 1 year ago
Feature
PowerOn Pro
Planned
Add Source Control Management (SCM) to Remote Syms
Need to provide a self-managed source control capability to our Remote Syms feature.
Dylan Martinez over 1 year ago
Feature
PowerOn Pro
Planned
Add Source Control Management (SCM) to Remote Syms
Need to provide a self-managed source control capability to our Remote Syms feature.
Dylan Martinez over 1 year ago
Feature
PowerOn Pro
Planned
Create PowerOn Linter
For the folks who like clean PowerOn code by default. This should likely be available via CLI so that folks can consume in their CI/CD workflows. (ref. Jordan Weschler)
Dylan Martinez over 1 year ago
Product Idea
Libum
Planned
Create PowerOn Linter
For the folks who like clean PowerOn code by default. This should likely be available via CLI so that folks can consume in their CI/CD workflows. (ref. Jordan Weschler)
Dylan Martinez over 1 year ago
Product Idea
Libum
Planned
Improve the SSH connection type user experience
There are multiple areas of improvement here. prompting the user to accept key on first use support non-CLI enabled organizations
Dylan Martinez over 1 year ago
Refinement
PowerOn Pro
Planned
Improve the SSH connection type user experience
There are multiple areas of improvement here. prompting the user to accept key on first use support non-CLI enabled organizations
Dylan Martinez over 1 year ago
Refinement
PowerOn Pro
Planned
Add Miscellaneous Posting to available commands
My understanding is that we want to be able to run this via PowerOn Pro and display output in VS Code. (ref. Technology Happens)
Dylan Martinez over 1 year ago
Feature
PowerOn Pro
Planned
Add Miscellaneous Posting to available commands
My understanding is that we want to be able to run this via PowerOn Pro and display output in VS Code. (ref. Technology Happens)
Dylan Martinez over 1 year ago
Feature
PowerOn Pro
Planned
Run FM from batch output
Need to add a batch FM run targeting a specific report available via command.
Dylan Martinez over 1 year ago
Parity
PowerOn Pro
Planned
Run FM from batch output
Need to add a batch FM run targeting a specific report available via command.
Dylan Martinez over 1 year ago
Parity
PowerOn Pro