2026.22 Infrastructure Changes — Unique AI Documentation
2026.22 Infrastructure Changes
Changes on Application environment Copy link to this section
| Change | Environment Variable Name | Application Default Value (if env variable unset) |
Example | Required | Applications | Short Description |
|---|---|---|---|---|---|---|
| Added | FEATURE_FLAG_ENABLE_AGENTIC_INGESTION_PAGE_BATCH_FIGURE_EXTRACTION_UN_19457 |
false |
true |
false | - backend-service-configuration |
Enables page-batch figure extraction for Image Content Extraction. When enabled and Image Content Extraction is active for the document, the ingestion worker sends the full page image and all detected figure regions to agentic-ingestion in one batched call instead of sending one cropped image per figure. |
| Added | FEATURE_FLAG_ENABLE_ATOMIC_FIGURE_CHUNKING_UN_19136 |
false |
true |
false | - backend-service-configuration |
Keeps extracted <figure> blocks atomic during markdown chunking, so figure captions and extracted image text are kept together. |
| Added | FEATURE_FLAG_ENABLE_MDI_PDF_HYPERLINK_EXTRACTION_UN_19716 |
false |
true |
false | - backend-service-configuration |
Enable the extraction of hyperlinks in chunks. |
| Added | FEATURE_FLAG_AGENTIC_TABLE_COMMENTS_UN_17606 |
false |
true |
false | - backend-service-configuration |
Enable inline comments on cells in the Agentic Table with threaded replies, @mentions, resolve/re-open and a dedicated side panel for triage. |
| Removed | FEATURE_FLAG_AGENTIC_TABLE_REFERENCE_SIDEBAR_COMPONENTS_UN_16483 |
- | - | - | - web-app-chat- backend-service-configuration |
Removed since it is GA. |
| Removed | FEATURE_FLAG_AGENTIC_TABLE_NEW_FILES_DROPDOWN_UN_12713 |
- | - | - | - web-app-chat- backend-service-configuration |
Removed since it is GA. |
| Removed | FEATURE_FLAG_AGENTIC_TABLE_INSERT_ROW_UN_17649 |
- | - | - | - web-app-chat- backend-service-configuration |
Removed since it is GA. |
Migration Hook Command Update Copy link to this section
The Prisma migration step in the migration hook now runs from the service root instead of the prisma/ subdirectory, and the --config path is no longer relative to prisma/. The migration command in the migration hook in the default values of the affected services needs to be adjusted.
Affected services:
- backend-service-app-repository
- backend-service-chat
- backend-service-configuration
- backend-service-ingestion
- backend-service-scope-management
For each service, in your override values:
# search for
cd /home/node/app/services/<service>/prisma; pnpm exec prisma migrate deploy --config ../prisma.config.ts;
# replace with
cd /home/node/app/services/<service> && pnpm exec prisma migrate deploy --config prisma.config.ts;
Replace
with the actual service directory name (e.g. node-ingestion, node-chat, gatekeeper, configuration-backend, node-app-repository, node-scope-management).
Example final result for backend-service-ingestion:
hooks:
migration:
enabled: true
command: |
cd /home/node/app/services/node-ingestion && pnpm exec prisma migrate deploy --config prisma.config.ts; cd /home/node/app/services/node-ingestion/dist;