PowerScriptDataWindowsDatabase

Verify and safely maintain business-critical PowerBuilder applications.

Detect vulnerabilities and code issues, verify changes and see their impact across PowerScript, DataWindows and the database.

Visual Expert Web · Code Inspection dashboard
Visual Expert Web Code Inspection dashboard: defects by severity, status and type, defect trend across analyses
01Verify

Systematically verify every change, human or AI-generated

Inspect PowerBuilder code for vulnerabilities, bugs, maintainability problems and potentially dead code. The same rules run at every analysis, so verification does not rely on manual review alone.

  • Security vulnerabilities: hard-coded credentials and IP addresses, injection risks, unsafe use of encryption.
  • Bugs and quality issues: empty methods, oversized scripts, duplicated objects, naming conventions.
  • New defects reported for each analysis, so you see what a change introduced.
  • Continuous inspection in your CI/CD pipeline, before deployment.
Code inspection · Secure Coding rules
Secure Coding rules checked on a PowerBuilder + Oracle project in Visual Expert Web
Secure Coding rules checked on a PowerBuilder + Oracle project.
02Understand impact

Know what a change can affect before you make it

Visual Expert builds a model of your PowerBuilder application: callers and callees, DataWindow usage and references to database tables and columns.

  • Impact analysis on variables, functions, windows, DataWindows, tables and columns.
  • Call graphs and reverse call graphs to follow complex chains of calls.
  • Calls to stored procedures located in the PowerBuilder code.
  • Possibly unused objects, methods and variables listed before cleanup.
Impact analysis · column product.id
Impact analysis of a column in Visual Expert Web: the DataWindows, window and event that use it, with the SQL statement highlighted
Where the column product.id is used: DataWindows, window, event and the SQL statement.
03Remediate

Move from findings to managed remediation

Review and qualify each defect, assign the work, fix the code and let the next analysis confirm the correction.

  • Qualify findings: false positive, accepted risk or on hold. Decisions stay recorded.
  • Assign a defect and a task is created, with an assignee, a priority and a due date.
  • Mark as fixed: the defect waits in Pending Validation until the next analysis checks it.
  • Potential Solution (AI) proposes a remediation approach when VE AI is enabled.

Defect lifecycle

OpenPending ValidationResolved
Developer marks it as fixedSet by the next analysis

Reviewed defects can also be set aside. Their history is kept.

Risk AcceptedFalse PositiveOn Hold
VE AI · fixing a code issue
VE AI proposing a fix for a PowerBuilder code issue
04Document

Turn PowerBuilder code into shared, up-to-date knowledge

Generate documentation, diagrams and data-usage views from the analyzed application, refresh them on a schedule, and reduce dependence on a few long-time experts.

  • Navigable HTML documentation of objects and references, with hyperlinks.
  • Diagrams, call graphs and CRUD matrices generated from the code.
  • Scheduled updates so the documentation follows the code.
  • Technical and business logic explained by VE AI.
Documentation · application overview
Documentation dashboard of a PowerBuilder + Oracle project in Visual Expert Web
Application overview generated from a PowerBuilder + Oracle project.
PowerBuilder + database

Analyze PowerBuilder and database code together

One Visual Expert project can combine your PowerBuilder application with its Oracle or SQL Server code. A change to a table, a column or a procedure can be traced back to the windows and DataWindows that use it.

CRUD matrix · PowerBuilder objects × tables
CRUD matrix in Visual Expert Web: which PowerBuilder DataWindows and objects create, read, update or delete each table
CRUD matrix

Which DataWindows and procedures create, read, update or delete each table.

Schema changes

Find the PowerBuilder code to update when a table or column changes.

Stored procedure calls

Calls from PowerBuilder followed into the database code.

Your PowerBuilder sources · Teams · DevOps

Works with the way your PowerBuilder code is organized

Point Visual Expert at your libraries, targets or repository. Analyses refresh on a schedule or from Jenkins, and the whole team works from the same results in the browser.

PBLs, targets or solution folders

Create a project from PowerBuilder libraries, targets, a solution folder or a ws_objects folder.

PBLTargetSolutionws_objects

Several applications, one project

Analyze several PowerBuilder applications together, with the ancestor libraries they share.

Source control and automation

Read the code from Git, SVN or TFS (including PBG files), refresh analyses on a schedule or from Jenkins.

GitSVNTFSJenkinsJUnit / JSON

Shared in Visual Expert Web

Results, documentation, defects and tasks in the browser, with no installation for the team.

Go further

Code verification in the AI era

Why AI-assisted changes still need independent verification.

DevOps integration

Run verification automatically and publish the results to your tools.

System requirements

Supported versions and setup.

Pricing

Editions and licensing.

Free trial

Verify your own PowerBuilder application

Run Visual Expert on your code and review vulnerabilities, dependencies, dead code and documentation with our team.

Prefer a guided tour? Request a demo

I cannot remember so powerful a tool that allows a user to become familiar with a new application in literally a few hours.
Georges Mikhailovsky, Calibre Systems
Visual Expert customers includeHSBCAllianzBNP ParibasAvivaFujitsuAtos

Request your free trial

All fields are required.

This form is protected by reCAPTCHA.

Visual Expert Web · Code Inspection dashboard
Code Inspection dashboard
Defects by severity, status and type; trend across analyses.
Code inspection · Secure Coding rules · use the arrows or ← → keys
Secure Coding rules on a PowerBuilder + Oracle project
1 / 2Secure Coding rules on a PowerBuilder + Oracle project.
Code inspection results
2 / 2Rule violations listed for the analyzed application.
PowerBuilder impact analysis · use the arrows or ← → keys
Impact analysis of a column, Visual Expert Web
1 / 5Where the column product.id is used: DataWindows, window, event and SQL statement.
PowerBuilder impact analysis, view 1
2 / 5PowerBuilder impact analysis
PowerBuilder impact analysis, view 2
3 / 5PowerBuilder impact analysis
PowerBuilder impact analysis, view 3
4 / 5PowerBuilder impact analysis
PowerBuilder impact analysis, view 4
5 / 5PowerBuilder impact analysis
VE AI · fixing a PowerBuilder code issue · use the arrows or ← → keys
VE AI proposing a fix
1 / 2Available when VE AI is enabled.
Code Inspection dashboard with defect statuses
2 / 2Defect statuses, severity, aging and recent activity.
PowerBuilder documentation · use the arrows or ← → keys
Documentation dashboard, Visual Expert Web
1 / 4Application overview generated from the code.
PowerBuilder reference documentation
2 / 4Reference documentation
PowerBuilder reference documentation
3 / 4Reference documentation
PowerBuilder call graph diagram
4 / 4Call graph diagram
CRUD matrix · use the arrows or ← → keys
CRUD matrix in Visual Expert Web
1 / 2Which PowerBuilder objects create, read, update or delete each table (Visual Expert Web).
CRUD matrix, Visual Expert Desktop
2 / 2CRUD matrix in Visual Expert Desktop.