Custom Corsa integration for cases and documents
Appfront builds the integration between Corsa and the systems your staff actually work in. For each new case, the integration creates a case file in Corsa, registers documents with the right case types and metadata, pulls statuses and decisions back, and records every exchange in a log. Failed messages go into a queue that you can resubmit yourself. So nobody has to copy files by hand from a line-of-business application into the document management system any more.
What is a Corsa integration?
A Corsa integration is a link between Corsa and the systems where the work happens: line-of-business applications, portals, email and signing tools. When a new case arrives, the integration creates a case file, places documents in that file with case type, document type and metadata, and passes statuses, decisions and processing deadlines back to the system the case handler works in. Every exchange gets its own line in the log.
Without an integration, people shuffle files around. A permit application arrives in the line-of-business application, the case handler saves the PDF to the desktop and then uploads it to Corsa, with hastily completed metadata. In a Woo request (Dutch freedom of information) or an objection procedure, the file turns out to be incomplete: attachments are missing, the dispatch date is wrong and nobody knows which version was sent. Tracing it all back then takes more time than the case itself.
We build custom because no two Corsa setups are the same. Your case types, document types, folder structure, retention periods and mandate rules have grown over the years, as have the line-of-business applications around them. We connect via Zaak- en Documentservices where possible and via the REST API where necessary, and we translate your own code lists into the integration. A generic package doesn't know your case type list or your internal agreements.
A case file for every case
As soon as a case is created in the line-of-business application or the portal, the integration creates the corresponding case file in Corsa, with the case type, parties involved and attributes from the source.
Documents with metadata
Every document ends up in the right file, with document type, date, sender, confidentiality and retention period. Versions, attachments and signed copies stay linked to each other and to the case.
Statuses that flow back
A status change or decision in Corsa flows back to the source system and to the case handler, so both sides have the same picture of where a case stands.
How we build your Corsa integration
We start with a stack of real cases from recent weeks and the question of who moved which file by hand.
For each line-of-business application, we review which cases and documents need to go to Corsa, who does that now and which data goes with them. The result is a message overview.
We carry your case types, document types, code lists, retention periods and permissions over into the integration, and decide per field which system takes precedence when the two sides differ.
Then we build the processing itself: creating files, registering documents, reporting statuses back and a queue in which administrators can see failed messages with the reason and resubmit them.
We first run the integration alongside your existing way of working, compare the results case by case and then take over the maintenance, including alerts on failures and regular updates.
What a Corsa integration actually does
The components below appear in almost every Corsa integration. Which ones you need depends on your line-of-business applications, your case types and the archiving rules you are bound by.
Creating case files
New cases from line-of-business applications and portals automatically get a case file in Corsa, with the right case type code, parties involved, attributes and the department handling the case.
Document registration
Documents are registered in the case file with document type, date, sender and confidentiality level, including attachments, signed versions and the delivery method used.
Metadata and code lists
Your own code lists for case types, departments and outcomes are mapped, so both systems speak the same language without anyone rebuilding a drop-down list by hand.
Queue and reprocessing
Failed messages stay visible in a queue with the error message and number of attempts, so administrators can resubmit them themselves and no work silently disappears.
Archiving and retention periods
Archive attributes and retention periods are passed along per file, so destruction lists and transfer to the digital archive can be justified later without a clean-up exercise afterwards.
Permissions and audit log
Access is role-based and every exchange can be traced by case, document and time, including who or which system performed the action.
Who we build Corsa integrations for
The software is intended for organisations that use Corsa as their document management system while the actual work happens in other applications.
Municipalities
Permits, objections and notifications originate in line-of-business applications and portals. The key here is automatically creating case files with the right case type code.
Water boards
Many cases are tied to objects and areas in the field. The key is getting documents from inspection and management systems into the file in full.
Environmental agencies and safety regions
Work is done on behalf of multiple participants. The key is that every document ends up with the right client and in the right file, with permissions per participant.
Healthcare and education institutions
Contracts, files and correspondence run through multiple systems. The key is retention periods and confidentiality that automatically travel with the document.
Technology and integrations
This page is about connecting Corsa to the line-of-business applications, portals and archive systems around it. Also see our other integrations, web development for portals that submit documents, and software development for the workflow around it. You can read about our approach on building software.
Why Appfront for your Corsa integration?
An integration is only as good as the agreements underneath it. That is what we build on: first the data and the rules, then the technology.
An integration is not a file copy
A document without a case type, date and retention period is just as hard to find in Corsa as on a network drive. We handle the metadata in the integration, not afterwards in a clean-up exercise.
Errors must be visible
Every integration gets stuck at some point. That is why you see failed messages with the reason in a queue and can resubmit them yourself, without work silently disappearing.
Standards where possible
We use Corsa's existing services and the national standards as long as they fit, and build custom solutions for the fields and rules they don't cover.
Security and privacy in a Corsa integration
The integration contains case data, documents and personal data of residents, clients or employees. Access is role-based: case handlers see their own files, administrators the queue and the log. Every exchange is recorded with time and source. We define retention periods, confidentiality and the requirements of the GDPR and the Archiefwet (Dutch Archives Act) per document type, supplemented with NEN 7510 for healthcare data.
The software runs in a European data centre, with encrypted storage and daily backups. Integrations with Corsa, line-of-business applications and portals use their own keys, which can be revoked per integration.
Frequently asked questions about Corsa integration
Questions that information managers and application administrators ask before getting started.
A Corsa integration ensures that cases and documents from your line-of-business applications, portals and email end up in Corsa automatically, in the right file and with the right metadata. In the other direction, statuses and decisions from Corsa flow back into the source system. Manual downloading, uploading and retyping disappear, and for each case you can see what was exchanged and when.
That depends on your version and setup. Where possible, we use the Case and Document services that many line-of-business applications already support, supplemented by Corsa's REST and web services. If a system is not prepared for this, we build an intermediate layer that converts messages, so your DMS configuration does not need to change.
No. We take your existing case types, document types and code lists as the starting point and translate them into the integration. If duplicate or unused types come to light during the inventory, we will flag it, but the decision is yours. Cleaning up can happen later; the integration does not have to wait for it.
Messages stay in the queue instead of being lost. Once the connection is back, they are processed in their original order. Administrators can see the error message and the number of attempts for each message, and can resubmit a message themselves or deliberately let it lapse.
Yes. In addition to writing documents to Corsa, the integration can retrieve files and documents, for example to display them in a portal, send them along with an application or prepare them for a signing round. Permissions and confidentiality settings from Corsa remain leading, so nobody sees more than they are allowed to.
We supply archive attributes and retention periods per document type at registration, so they do not have to be added afterwards. This keeps destruction lists and transfer to a digital repository well founded. What exactly belongs in which field, we determine together with your information management adviser during the inventory.
Check that first. Standard integrations exist for many well-known line-of-business applications, and if they fit your process, that is the cheapest route. Custom work only becomes worthwhile for in-house or older applications, deviating metadata, multiple participating organisations, or processes in which steps from several systems come together in one file.
Do you want every case to end up complete in Corsa automatically?
Tell us which line-of-business applications you use, how documents currently get into Corsa and which case types are involved. We will show you what the creation of case files, document registration with metadata and the queue with reprocessing look like, and what that means for your workflow.