Custom Djuma integration
Djuma is Visma Circle's case management system, delivered as a cloud environment for municipalities, water boards, provinces and other organisations. It supports the ZGW APIs and StUF-ZKN. Appfront builds the integration with the systems that are not yet connected to it: line-of-business applications, forms, portals and reports, so cases, documents and decisions no longer have to be transferred by hand.
What is a Djuma integration?
Djuma is a case management system from Visma Circle, delivered as a single cloud environment for all customers. It combines a case type catalogue, document management, document creation, e-forms, a customer portal, customer contact and a knowledge base, among other things. Municipalities, a water board and a province use it, as do organisations outside government.
According to the Softwarecatalogus, Djuma supports the ZGW APIs for cases, catalogues, documents and decisions, StUF-ZKN and the interface for ongoing cases on MijnOverheid. Even so, work remains. A line-of-business application produces a decision that is attached to the case by hand. An application from your own form is retyped. Management information is compiled from exports.
We build custom integrations because every organisation has different systems alongside Djuma. Which line-of-business applications, which channels and which figures need to go where determines how the integration works. Which interfaces you can use and which agreements go with them, we work out together with you and with Visma Circle.
Cases straight in
From form to Djuma.
Decision on the case
From the line-of-business application.
According to the standards
ZGW APIs or StUF.
How we build your Djuma integration
We start with your organisation: which systems run alongside Djuma, which data is currently handled by hand, and which integrations already exist. Then we look at which interfaces are available and which agreements you make with Visma Circle. We often start with one line-of-business application or one channel, because that is where most of the retyping happens. Statuses, documents, decisions and reporting follow once that works well. After that, we maintain the integration when Djuma or your other systems change. Because Djuma is a single environment for all customers, you receive new versions at the same time as other organisations; we then retest the integration before anything goes wrong in your case files.
Systems, processes and integrations.
ZGW APIs or StUF.
Cases, documents and decisions.
Go-live, monitoring, and maintenance when things change.
What a Djuma integration actually does
The components below feature in almost every Djuma integration. Which ones you need depends on your organisation and systems.
Creating a case
From form or portal.
Documents
On the right case.
Decisions
From the line-of-business application.
Statuses
To the resident.
Reporting
Lead times and volumes.
Log
Every message recorded.
Who we build a Djuma integration for
The integration is intended for organisations that work with Djuma and have systems that are not yet connected to it. The more line-of-business applications and channels you have, the more it delivers.
Municipalities
From front desk to archive.
Water boards
Permits and notifications.
Provinces
Cases across multiple teams.
Suppliers
A line-of-business application on Djuma.
Technology and integrations
This page is about integrations with Djuma. For the standards, see our page on the ZGW API integration and our page on the StUF integration; for other case management systems, our page on the iZaaksuite integration and our page on the Liber integration; and for the resident portal, our page on a citizen portal. You can read about our approach on building software.
Why Appfront for your Djuma integration?
Decisions that stay in a line-of-business application, applications that are retyped and management information from separate exports cost an organisation time and leave the case file incomplete. That is what we build on: every case complete, line-of-business applications connected, and an integration via the standards Djuma supports.
Complete file
Decision and case together.
Less retyping
Every channel comes in.
As agreed
Via the standards.
Security and privacy in a Djuma integration
The integration processes data about residents and businesses, sometimes including special category personal data. We use only what the case needs, access is set up per role, keys and certificates are stored encrypted, and every message is logged.
The part we build runs in a European data centre or in your own environment, with encrypted storage and daily backups. We record the processing in a data processing agreement and meet the security requirements that apply to your organisation.
Frequently asked questions about a Djuma integration
Questions organisations ask before they get started.
Djuma is a case management system from Visma Circle, delivered as a cloud environment. It supports case-based working with, among other things, a case type catalogue, document management, document creation, e-forms, a customer portal, customer contact and a knowledge base. It is used by municipalities, water boards, provinces and other organisations.
Yes. Djuma supports standards such as the ZGW APIs and StUF-ZKN, and Visma Circle also provides its own integrations and conversions. If your system already connects and does what you need, custom work isn't necessary, and we'll tell you so. A custom integration is for systems and channels that aren't covered.
Via the ZGW APIs or StUF-ZKN, depending on what your other system speaks and which interfaces are available for your environment. In the first step we look at which arrangements you need to make with Visma Circle for this, so you don't get stuck on a route that doesn't exist.
Yes. When the line-of-business application produces a decision or document, the integration places it with the right case in Djuma and updates the status. The case handler and the customer contact centre then see the whole file in one place.
Yes. Djuma supports the interface for ongoing cases on MijnOverheid and has a customer portal. If you have your own portal, the integration can show the status there too, so residents don't need to phone.
The integration reports it and records what went wrong. The message is retried or queued for review, so no case is lost or ends up duplicated in Djuma.
For organisations that use Djuma alongside line-of-business applications, channels and reports that aren't connected to it, and for suppliers who want to connect their line-of-business application to Djuma. If all your systems are already connected and nothing is missing, you don't need a custom integration.
Djuma connected to everything else?
Tell us which systems you use alongside Djuma and what is currently done by hand. We'll show you how the integration works.