continON
CompanySubscriptions
Request a demo

Platform & Configuration

Builders

The Builders are continON’s configuration environment. A process designed on a canvas runs as live requests, a form binds to its states, a saved query feeds its reports, and a template turns its data into the finished PDF. Change the definition and the running platform follows — without rebuilding application code.

Request a demoBack to the module universe

DefinitionStored as

  • Processmetadata
  • Formmetadata
  • Querymetadata
  • Document templatemetadata
  • Reportmetadata
  • Dashboardmetadata

interpreted at runtime Edit a definition and it takes effect without redeploying the applications that use it.

The operating model

Most operational software hard-codes how work moves: change the approval chain and you file a development ticket. In continON, the shape of the work is data. Process, form, query, document, report, and dashboard definitions are stored as metadata and interpreted at runtime, so an edited definition takes effect without redeploying the applications that use it.

The definitions actually run. A submitted request becomes a live process instance that advances through the states drawn on the canvas, resolves who acts at each step from positions in the org chart, and fires the configured activities — a notification, a generated document, a task — on every transition. That runtime engine, not the drawing surface, is what separates the Builders from a diagram tool.

The boundary is stated honestly. Most change is configuration: stages, fields, rules, layouts, grants. Where a requirement goes past the visual designers, advanced users extend with SQL and JavaScript, and the table designer generates real database schema — which is exactly why continON describes the Builders as configuration you can extend, not as a no-code product.

Assembling the definition

Design the process

Map states, transitions, actor groups, time limits and rules on the visual canvas. Each saved definition is versioned.

Process BuilderStates · transitions · actors · time limits
  1. Submitted
  2. In review
  3. Approved
  4. Filed

Each transition resolves its actors from positions in the org chart — the seat, not a named person.

attaches to a stateForm BuilderA versioned form bound to each state, so the right fields open when work arrives
fires on transitionActivities
  • Notification
  • Email
  • Add stakeholder
  • Run procedure
  • Generate task
executes on transitionDocument Template DesignerA bound template runs its query with the request’s context and files the finished PDF
Report DesignerDashboard Designer
the shared data layerQuery & Data Source BuilderDocuments, reports and dashboards all read through it — scoped to positions and partners

Everything inside Builders

6 capabilities

  1. Design the work

  2. The data layer

  3. Documents, reports & dashboards

Connected through one operating model

Builders does not stand alone.

Records cross module boundaries without being re-entered — these are the relationships continON actually maintains.

  1. System AdministrationEnterprise profile, users and permission groups, languages and localization, shared reference data, and license-based module activation — the configuration every module runs under.
  2. Document ManagementFiles attached to a request live in the governed document store under position-based access.
  3. Task ManagementA transition activity can generate tasks for the people who must act next.
  4. Project ManagementPer-project dashboards are this designer’s parameterization applied at project scope.

See Builders on your own operations.

A guided walkthrough on a sanitized demo tenant — this module, the shared platform, and a connected workflow end to end.

Request a demoExplore the platform