CIS Customization & Development

Build CIS Around the Way Your Organization Actually Works

CIS gives trained administrators the tools to create tables, fields, forms, views, filters, permissions and pages directly inside the system – while TQMS handles the advanced programming that belongs behind the scenes.

CIS software customization interface showing editable forms and workflow configuration
The person who understands the process can build most of the system. You do not need a programmer every time a field, form, workflow, permission or report needs to change.
See CIS Customization in Action

A configurable platform

Build new applications inside CIS, not beside it

CIS is designed so administrators can extend the system using the same framework that supports the standard CIS modules. New processes can become part of the same menu, permissions structure and operating environment your users already know.

Create tables and fields

Define the information your process needs, including text, dates, lists, uploads, measurements, checkboxes and related records.

Design forms

Build insert and edit screens around the way people actually work, including custom layouts and different views for different stages.

Build grids and reports

Decide which information appears in grids, list views, filters, exports and report-style user controls.

Control access

Define which user types can reach each page and what they may add, edit, delete or simply review once they get there.

How CIS is structured

Three building blocks turn a database into a working business process

CIS separates the data itself from the way people interact with it and from the pages they use to reach it. That separation is what makes the system flexible.

1. Fields and tables Define where information is stored and what each record contains.
2. User controls Define forms, grids, list views, filters, hidden fields and permissions for the same underlying records.
3. Pages Place the user control in the CIS menu and decide which user types can reach it.

One database, different experiences

Show the same record differently to different people

One table can support several user controls. Each control can show different fields, different forms, different grids and different permissions while everyone still works with the same underlying record.

  • Employees can enter the initial information.
  • Managers can review it without changing the original entries.
  • Another group can complete the next stage of the process.
  • Executives can receive a read-only summary.
  • Suppliers or customers can submit information through a portal.

Why this matters

Build workflows without copying the record from system to system

Different stages can use different forms over the same data. Earlier information can remain visible but read-only while the next person completes their part of the process. The record stays intact instead of being copied, re-entered or passed through disconnected systems.

From idea to working page

Build the process in a logical sequence

The CIS programming framework follows a repeatable process. Plan the workflow first, then build the data, the screens and finally the page users will work from.

Plan the process

Decide who does each step, what they enter, what they may only see and what should happen when the record is saved.

Build the data

Create the table, fields and relationships needed to hold the information.

Build the screens

Create user controls, grids, forms, filters, exports and permissions.

Publish the page

Add the user control to the menu, assign page access and put the finished process in front of the right users.

What your team can build

A surprisingly large amount requires no custom programming

CIS administrators can build and refine many day-to-day business processes directly from the interface.

Database tables and fields
Insert and edit forms
Custom grids and list views
Filters and searches
Excel and CSV export layouts
User-type permissions
Menu pages and folders
Read-only management views
Report-style user controls
Customer and supplier portals
Controlled document links
Custom form layouts

A clear division of responsibility

Configure what is visible. Let us handle what belongs in the back end.

CIS deliberately gives administrators substantial control, but it also keeps code-level functions behind a clear boundary. That gives you flexibility without asking administrators to become software developers.

Your CIS administrator can handle

  • Create tables and fields.
  • Create user controls and pages.
  • Design forms, grids, list views and filters.
  • Set page and user-control permissions.
  • Create foreign fields based on normal tables.
  • Hide fields and control exports and sorting.
  • Build report-style user controls.
  • Create portals and arrange the menu.

TQMS programmers handle

  • Automated actions triggered when a record is saved.
  • Email notifications and email templates.
  • Archive programming for new tables.
  • Advanced code-behind functions.
  • Links that move information between databases.
  • SQL views and advanced data logic.
  • APIs and connections to external systems.
  • Specialized JavaScript and back-end functionality.

Lower development cost

Pay for the programming you actually need

Instead of paying programmers to build every field, form, table and screen, your team can build the visible structure themselves. When advanced programming is needed, TQMS can focus on the specific automation or integration that cannot be created from the CIS interface.

Built to evolve

Change the system as your process improves

Because CIS applications are assembled from configurable components, the system can evolve as the organization changes.

  • Add fields when new information becomes important.
  • Build additional views for new groups of users.
  • Improve grids and forms as people learn what they need.
  • Add pages and processes without replacing the system.
  • Expand into portals, reports and specialized workflows over time.

Safe development

Build and test changes before putting them in front of users

CIS administrators are given substantial control, so significant changes should be developed and tested carefully before they are applied to the live system.

  • Plan the process before creating the database.
  • Use a CIS Test Bed for development and practice.
  • Test forms, permissions and workflows before going live.
  • Keep copies of working templates before revising them.

Programming manual

A practical reference for CIS administrators

The CIS Programming Manual documents how tables, fields, user controls, pages, grids, filters, forms, permissions, portals and templates work, including the areas administrators may safely change and the areas that should remain with TQMS programmers.

Build around your process

Start with CIS. Adapt it as your organization changes.

CIS combines configurable system-building tools with professional development support when deeper automation is required. The result is a platform your organization can continue improving instead of a fixed application you eventually outgrow.

Book a CIS Demo