Menu

How it works

Declare the process.
Work in the application.

JCM turns reviewable declarations into the building blocks of case management. Your team works in an application. Your developers work in its repository.

01

Declare

Define the model, screens and process in YAML, with Java extensions when needed.

02

Check

Run jcm check for startup, tests, extension API and layer checks.

03

Review

Walk the program’s cases. Review access, accessibility and the generated changes.

04

Deliver

Release through your team’s approved environment and change process.

A shared view of the process

Visual editing.
Versioned definitions.

Studio provides a visual way to work with application configuration. Bring reviewed changes back to the same repository for checks and delivery.

JCM Studio queue editor showing date window, roles and case type configuration in a synthetic test application.
Actual JCM sample application · synthetic test dataView full image ↗

This captured test screen includes example role names. A program’s actual permissions require their own review and restricted-user tests.

01

Workflows

Make the next decision explicit.

Declare states, transitions and the conditions that permit a case to move forward. Keep the process in reviewable files alongside the application.

02

Queues

Bring the work to the team.

Organize cases into shared and personal work lists. Configure how people take the next case and which work is available to them.

03

Clocks

Keep time in the process.

Connect deadlines and tasks to the lifecycle of a case. Make calendar rules and the work they trigger part of the application’s configuration.

04

Letters

Close the loop with a clear record.

Use letter templates to prepare correspondence from case information. Review the wording and data mapping as part of program delivery.

05

Hearings

Make space for the next step.

Bring scheduling and hearing slots into the case process, with the supporting work visible to the team.

06

Forms & records

Keep the details together.

Declare the data a program needs and how people work with it. Extend the application in Java where program logic calls for code.

Delivery is more than passing a build. Check representative journeys, keyboard and screen-reader use, access boundaries and operational readiness before release. WCAG 2.1 AA is the accessibility target; we test against it and don’t claim product-wide certification.

Start with your program.
Build on your terms.

Explore a demo