Tell us how we could make any one of our products more useful to you.
In Progress
Allow VALIDATION specfiles to be syntax checked
Specfiles with the VALIDATION keyword are being skipped due to “File has no PRINT or LETTER division” however per eDocs, validation specfiles are not supposed to use these: Do not use a SELECT or PRINT division in a validation specfile.
In Progress
Deploy and Install should deploy includes before deploying and installing
When using “Deploy and Install,” it checks if any includes also need to be deployed. However, it will deploy and install the main file before it deploys the includes, resulting in an installed file with old include code in memory. It needs to deploy the includes first before deploying and installing the main file.
In Progress
Referencing fields by number displays an error message
these are both valid but the built-in error checker flags them as errors: account:040 account:010:001
Planned
Validation messages in the Output section of VS Code
It would be nice to have the messages from Episys shown on VS Code’s Output panel in place of the generic xxxx.xx install failed.
Task after pull request complete to have reviewer push to host
we dont have pipelines deploy directly to the host. When the pull request is finished by the reviewer, they then deploy changed files manually. is there a way to create or is there a task that can be used to create a pipeline that deploys only changed files?
Add the ability to just re-install
There are times when deploying a specfile, we deploy a file but it is dependent on another specfile to be reinstalled for the changes to take affect.
In Progress
flag strings longer than 132 chars
any “string” longer than 132 could show up in the problems tab. for example htmlviewline(“
In Progress
Add support for headers ... end
It’s possible to define report headers not only by the typical means of header=”…”, but also by a section like this: print title = "foo" headers print "bar" newline end [...] end PowerOn Pro does not seem to recognize this syntax yet.
In Progress
Add support for complex expressions in references to sub-fields
Something like card note:text:(myNumberVar - 1) is not parsed correctly by PowerOn Pro; card note:text:(myNumberVar) seems to already work fine, though.
In Progress
Saving .PRO file does not auto-deploy
I have the config option to auto-deploy on save, but it tells me it’s skipping validation because the file is an include file and cannot be validated. It then stops, instead of copying the file to the sym.
NexumAPI - Helpfile Retrieval
Helpfiles can store data like purpose codes. Adding it to the filemanagement service would be helpful. Abstracting to real value would be even better as most helpfiles are tied to an endpoint, but it is difficult to know. Example use case: Edit and define purpose codes from an admin layer When setting up a new loan type, it would be ideal to tie the pieces like GL, purpose, loantype, collateral into one layer. Type and collateral are already retrieved.
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.
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.
Planned
Add Versioning to Parameter Manager
We need to have stateful parameters within Quest that are accessible via 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.
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.
In Progress
Add On-Demand rendering for PowerOn
Need to add support for rendering HTML on-demand PowerOn files within VS Code.
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.
Planned
Add Source Control Management (SCM) to Remote Syms
Need to provide a self-managed source control capability to our Remote Syms feature.