AI translation
This page was translated from German with AI. If in doubt, the German original applies.
ZEDAL Forms 4¶
ZEDAL Forms is the desktop application for filling in, signing and exchanging ZEDAL documents — waste consignment notes, verification documents as well as notifications and movements according to DiWaSS. The application works against the ZEDAL server; qualified electronic signatures are not created in ZEDAL Forms itself but in the separately installed ITSigner app.
System requirements¶
- Windows 11 or Windows 10, version 1809 (build 10.0.17763) or higher
- x64 or ARM64 architecture
- User interface in German and English
- For signing, the ITSigner app on the same device
Info
ZEDAL Forms 4 is currently shipped for Windows only. There are no Android, iOS or macOS editions.
Installation and updates¶
ZEDAL Forms 4 is distributed as an MSIX package via the Windows App Installer. The authoritative file is
It installs the application and keeps it current: on each launch — at most once every 24 hours — App Installer checks for a new version and updates it in the background. The installation package itself resides at the same path as a .msixbundle and contains the x64 and ARM64 editions.
The package is signed with a code signing certificate of ZEDAL GmbH:
Installation and operation take place in the context of the signed-in user; administrator rights are not required. In managed environments, installing applications from outside the Microsoft Store (sideloading) must be permitted by policy.
Permissions¶
On Windows, ZEDAL Forms declares exactly one capability:
| Capability | Meaning |
|---|---|
runFullTrust |
Regular desktop application context for the MSIX-packaged application. It runs with the rights of the signed-in user. |
The application does not request device capabilities on Windows — no camera, microphone, location, Bluetooth, or access to other user profiles.
In addition, the package registers with the system:
- the protocol handlers
forms2020-bmu:andforms2020-zewass:, which allow other applications and links to open a document directly in ZEDAL Forms - a COM server for activating the application from a Windows notification
Network traffic¶
The application establishes all connections outbound itself. ZEDAL Forms accepts no incoming connections from the network; a firewall rule for inbound traffic is not required.
| Destination | Purpose | Protocol | Required |
|---|---|---|---|
https://api.live.zedal.de |
Sign-in, master data, sending and receiving documents | gRPC over HTTP/2, TLS (443) | yes |
https://files.live.zedal.de |
Installation and automatic updates | HTTPS (443) | yes |
https://itsigner.live.zedal.de |
Signing jobs sent to a signature device that is not attached to the same machine (remote and cloud signing) | gRPC over HTTP/2, TLS (443) | only for remote or cloud signing |
https://telemetry.live.infotech.de |
anonymised error reports | HTTPS (443) | optional |
Interaction with ITSigner¶
For local signing — card reader attached to the same machine — ZEDAL Forms addresses the ITSigner app via the loopback adapter, either as an HTTP call to http://localhost:8056/ or through a named pipe. This traffic never leaves the machine and needs no firewall rule.
If ITSigner uses the A-Trust online signature, its network requirements apply in addition; ZEDAL Forms itself does not contact the A-Trust endpoints. The complete list is documented under ITSigner → Prerequisites.
Proxy environments¶
The connection to the ZEDAL server is gRPC over HTTP/2. Where HTTP/2 is not passed through — for example by an intercepting proxy or TLS inspection — the application can be switched to an explicitly configured proxy or to gRPC-Web. Please contact ZEDAL support for this.
Local data storage¶
Within the user profile, the application stores its settings, log files and working files for opened documents and their attachments — inside the MSIX application directory of the signed-in user. The log files can be opened from within the application via the settings; they are the first place to look when ZEDAL support needs to reproduce a problem.
ZEDAL Forms does not maintain a local document database: the document inventory resides on the ZEDAL server, and offline operation is not provided for.