See what’s new at MCFP just improved.

This is intended

• Follow-up with selected fields, note, and processing status
• Change history and separate handling of already signed data

We measure completion by this

• Customers see only the approved additional claim.
• A change does not silently overwrite a previously completed version.

Builds on these projects

This is intended

• Views, search, filters, responsible persons and follow-up
• Clear separation of form status and internal processing status

We measure completion by this

• Only authorized persons can view and modify assigned data.
• New team statuses do not change the previous sending status.

Builds on these projects

This is intended

• Own drafts and traceable published versions
• Restore as new version with preview of differences

We measure completion by this

• An ongoing process retains its appropriate form version.
• Resetting does not delete any answers or version history.

Builds on these projects

This is intended

• Roles for create, edit, read, and administration
• Local event log without response content and secret links

We measure completion by this

• Permissions are checked server-side for every action.
• Logging and retention are limited and traceable.

This is intended

• Preview affected data and files plus secure confirmation
• Optional retention rules with preview before activation

We measure completion by this

• No automatic deletion without activated rule.
• Jointly referenced files and active processes remain protected.

Builds on these projects

This is intended

• Add, remove, and limit field groups
• Conditions, validation and PDF per group instance

We measure completion by this

• Each instance retains stable field assignments when continuing.
• Export and PDF show all instances without mixed values.

Builds on these projects

This is intended

• Secure print editor with preview and decimal formats
• Server-side recalculation and defined handling of empty values

We measure completion by this

• Manipulated browser results are not accepted without verification.
• Calculation rules, rounding, and PDF results match.

Builds on these projects

This is intended

• Configure sections, page breaks and attachment overview
• Preview with sample data and stable field mappings

We measure completion by this

• Long texts, images, and repeatable groups are not cut off.
• Existing PDF output remains available as compatible standard template.

Builds on these projects

This is intended

• Events, field mapping, signing, test data and shipping log
• Limited repetitions and protection against double processing

We measure completion by this

• Only explicitly configured targets and fields are transmitted.
• Private network addresses, secret logs, and uncontrolled retry loops are excluded.

Builds on these projects

This is intended

• Documented events and importable sample workflows
• Field mapping and understandable error cases

We measure completion by this

• Examples initially use fictitious test data.
• Duplicate events do not lead to duplicate processes in the reference workflow.

Builds on these projects

This is intended

• Select first connector based on demand and interface capability
• Assignment, duplicate check and manual error correction

We measure completion by this

• No blanket sync of the entire customer base.
• Connection errors do not affect form completion.

Builds on these projects

This is intended

• Optional aggregated step, error, and completion counts
• Filter by form version and limited retention

We measure completion by this

• No field values, signatures, or complete links in analysis events.
• Disabled analytics generate no additional events.

Builds on these projects

This is intended

• Focus management, error assignment, labels, and upload alternatives
• Test matrix for standard fields and individual sub-processes

We measure completion by this

• A form can be operated without a mouse until completion.
• Automatic checks and manual screen reader tests document the scope.

Builds on these projects

This is intended

• Prioritize real estate, services, and organizational practice inquiries
• Professional acceptance, professional days and package assignment per template

We measure completion by this

• Only the actually published library is announced.
• Templates include version status, professional assignment, and tested completion.

Builds on these projects

This is intended

• Form-related help texts and preview of suggested changes
• Clearly explain features and data processing before use

We measure completion by this

• Suggestions change answers only after explicit acceptance.
• The form continues to work fully without AI.

Builds on these projects

This is intended

• Change comparison, schema-capable suggestions, and rollback
• Check report on fields, conditions, and comprehensibility

We measure completion by this

• Existing templates are not replaced without confirmation.
• Invalid field references are caught before publication.

Builds on these projects

This is intended

• Signed references instead of personal data in freely shareable URLs
• Field releases, origin, and editable suggestions

We measure completion by this

• Customers of other cases do not gain access via manipulated parameters.
• Prefill does not replace mandatory field validation.

Builds on these projects