Analyse WEBCON configuration with AI, compare versions and discover dependencies
Spectrum lets you analyse and compare any part of your WEBCON BPS configuration — from entire applications to their smallest components — and track changes over time.
Select a process and ask a question in your own words. The assistant uses its configuration to explain the workflow, approval rules and actions along the way.
For example, ask: “When does a contract require management approval?” The assistant helps you understand the conditions for moving between stages. The conversation appears beside the process, and the panel shows which element each question refers to.
Data on your infrastructure Portable without installation Server for the whole team
Spectrum features
Check changes and dependencies in your WEBCON BPS configuration
Spectrum helps you review a package before deployment, compare configuration versions and understand how an application works. You can also ask the AI assistant about a selected process.
Package deployment analysis
Check the impact of an import before you deploy the package
Select a package and its target environment to see which elements the import will add, overwrite, remove or retain. Start with the scope of process changes, then compare the values before and after the change.
If a package changes a shared rule, Spectrum also identifies processes in other applications that use it. This helps you decide what to test and which teams to involve before deployment.
The results take import settings into account. Unresolved references and effects requiring further verification are clearly marked.
Compare application versions from two environments or separate WEBCON BPS instances. Inspect differences across an entire application, a selected process or a single rule, down to a specific step, path and condition.
You can also compare the current configuration with an earlier snapshot of the same installation to establish what has changed since the previous deployment.
Trace the history of changes in your configuration
Spectrum saves configuration snapshots from export packages or by reading environments directly. In the Server edition, you can schedule snapshots to capture subsequent states automatically.
The history covers processes, rules, forms and data sources. Comparing saved states also reveals changes made directly in the production environment.
Select a rule, form field, data source or connection. Spectrum shows the forms, actions, path conditions and queries that reference it, including those in other applications.
For each reference, you can inspect how the element is used. A separate marker for elements without references helps you plan configuration clean-up before migration.
A process can start workflow instances in other processes, write data to them or call them through an API. The graph shows the direction of these connections and successive levels of dependencies.
Before changing a workflow, check which other processes to include in testing. Application names shown alongside connections help you identify the teams to consult before deployment.
Review the configuration for stored passwords, disabled certificate verification and test environment addresses. Spectrum also identifies references to inactive elements and cycles in process calls.
Each finding identifies the element and the relevant configuration fragment. You can assess the issue and attach this information to a change request.
Search by name, acronym or text fragment. Results are grouped by element type and show the application each match belongs to.
If you do not know the object's name, search within the configuration using a SQL fragment, service address or condition. A result link lets a colleague open the same view within their access permissions.
Share a process description with people outside IT
The Business view explains what determines the process flow, which actions run automatically, where data comes from and who receives tasks. A process owner can review this information without Designer Studio.
The diagram retains the author's layout. You can export it to PDF or as an editable drawing for Miro and Visio. Configuration descriptions can optionally be generated using a model chosen by your organisation.
Manage projects for multiple clients in a single Server instance, with a separate workspace for each. A client sees their own environments, an analyst sees assigned applications, and an auditor can be granted read-only access.
The permission preview lets you check access scope before inviting a user. Company licences depend on the number of users; WEBCON partner licences depend on the number of clients served.
Users can sign in with their corporate Microsoft Entra ID account. Their roles determine access to data and operations in Spectrum.
OpenShift
Run Spectrum in your organisation's cluster using ready-made manifests. The application supports health probes and running without root privileges.
Docker
Deploy the application in a container with PostgreSQL on your infrastructure. Your IT team manages the environment, updates and data.
RBAC — role-based access
Match permissions to user responsibilities by restricting access to selected clients, environments and applications.
Data security
Keep your configuration on your own infrastructure
Spectrum stores packages, environment snapshots and descriptions on your computer or company servers.
Licence verification sends the licence number, software version and counts of users, workspaces and environments. It does not include their names or configuration content. On a network without internet access, you can verify the licence with a file for a full year.
When you use the assistant or AI descriptions, your question and the necessary configuration material are sent to the model provider selected by your organisation.