Supported Versions and Compatibility
Maintenance periods, security-fix commitments, and end-of-support dates are defined by your FormKiQ support agreement. These docs do not promise a fixed number of maintained release branches or a universal support window.
Documentation baseline
The current API/backend documentation is pinned to v1.19.2. The Web Guide describes Web v4.3.8. These are independent version streams: a new Web release does not imply a new backend, and a backend release does not update a separately hosted console automatically.
| Component | Compatibility check |
|---|---|
| Backend and CloudFormation | Pin the release tag/template version, region, edition, and installed modules. |
| FormKiQ Web | Read the Web release's required backend capabilities and migration notes before updating its package. |
| Business Solutions | Confirm the solution package, workspace definitions, configuration migration, and backend dependencies. |
| SDK | Check the SDK's published API coverage against the deployment's OpenAPI version. SDK version numbers need not equal backend versions. |
| MCP server | Pin its release and bundled OpenAPI snapshot; enable only supported API groups/modules. |
Use the changelog and upgrade guide together. A new endpoint in a client or schema does not install that capability on an older or differently licensed backend.
Plan an upgrade
- Record current backend, Web, module, SDK, and solution package versions and deployment parameters.
- Review intervening release notes, schema/configuration changes, and any version-specific limitations.
- Back up configuration and data and rehearse the update and recovery plan in a separate environment.
- Test authentication, access denial, uploads, search, processing, reviews, signing, retention, and integration contracts used by your deployment.
- Agree the production window and any support requirements before applying the release.
Keep dependencies and AWS runtime changes in the operating plan. Do not assume that an older release remains secure or supported indefinitely merely because its template can still be downloaded. Contact FormKiQ with exact component versions to confirm your maintenance and migration options.