We need to make sure we have accurate information available in our function signatures, hovers, etc. as releases changes in Symitar.

Dylan Martinez 4 days ago

PowerOn Pro

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 6 days ago

3

PowerOn Pro

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 11 days ago

2

PowerOn Pro

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 11 days ago

1

PowerOn Pro

We need to have stateful parameters within Quest that are accessible via Pipelines.

Dylan Martinez 4 months ago

PowerOn Pipelines

We need to add management of Job Files via Pipelines.

Dylan Martinez 4 months ago

PowerOn Pipelines

Add a branded border somewhere in the Quest UI which will give users a clear signal they’re in a Production Sym instance.

dylan 5 months ago

Glaci

Need to add organization owner the ability (through Libum Portal) to set restrictions on which Sym developers can deploy to.

Dylan Martinez about 1 year ago

Feature

PowerOn Pro

Basically if you change the name of a PowerOn (updating only the case) we don’t detect the deployments. Unix supports both, so either we need to or normalize.

Dylan Martinez about 1 year ago

2

Bug

PowerOn Pro

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

2

PowerOn Pro

Need to add support for rendering HTML on-demand PowerOn files within VS Code.

Dylan Martinez over 1 year ago

1

Feature

PowerOn Pro

Need to add syntax highlighting for inline HTML and remove requirement for managing the htmlViewLine function and others.

Dylan Martinez over 1 year ago

3

Feature

PowerOn Pro

Need to provide a self-managed source control capability to our Remote Syms feature.

Dylan Martinez over 1 year ago

Feature

PowerOn Pro

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

1

Product Idea

Libum

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

3

Refinement

PowerOn Pro

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

2

Feature

PowerOn Pro

Need to add a batch FM run targeting a specific report available via command.

Dylan Martinez over 1 year ago

Parity

+1

PowerOn Pro

Need to add a revamped job files manager so devs don't have to create, modify, delete Job Files through Batch Control.

Dylan Martinez over 1 year ago

Feature

PowerOn Pro

Need to add support for managing the SymX PowerOn lifecycle.

Dylan Martinez over 1 year ago

1

Feature

PowerOn Pro